I've been trying to restore a BackupEdge full backup of an SCO 5.0.6 system
to an 80G SATA disk on an Intel S3000AHLX system board. This has not gone well.
Every time I boot the RE2 media the hard disk geometry comes back as
4 heads, 17 sectors, 4791 cylinders.
This is the output of defbootstr wd.debug=g:
wd_calc_geom(total_Blks = 15663014888x)
wd_calc_geom: head spin: sec = 63, heads = 16, spcyl = 1008, cyl = 155061
wd_calc_geom: head spin: sec = 63, heads = 32, spcyl = 2016, cyl = 77530
wd_calc_geom: head spin: sec = 63, heads = 64, spcyl = 4032, cyl = 38765
wd_calc_geom: head spin: sec = 63, heads = 128, spcyl = 8064, cyl = 9729
wd_calc_geom: head spin: sec = 63, heads = 255, spcyl = 16065, cyl = 9729
wd_calc_geom: returning sec = 63, heads = 255, spcyl = 16065, cyl = 155061
wd_set_geom: bootmisc.bioshds = 255, bootmisc.biossecs = 63, bootmisc.bioscyls = 9729
wd_set_geom: romTab hds = 4 romTab sec = 17 romTab Cyl = -536867492 Magic = 0x00
wd_set_geom: ValidTrans, heads = 4, sec = 17, cyl = 4791
wd_set_geom: final heads = 4, sec = 17, cyl = 4791
This makes fdisk unusable as fdisk only lists 19164 tracks (approximately
166M Byte).
I forced a restore by using UBC4Win boot CD and partition magic and defined
a UNIX partition that came out to be partition #4 as displayed by fdisk
that is about 40G. Running divvy -i and adjusting the divisions resulted
in a 4G root and 6G /dev/u file system and I was able to restore the
backup edge archive to the disk.
defbootstr with biosgeom=(9729,255,63) results with the 4hd, 17 sec, 4791
cyl disk paramaters.
dparam -w /dev/rhd00 `dparam /dev/rhd00` does no good, still 4,17,4791
dparam -w /dev/rhd00 9219 255 0 0 0 0 0 63 does not help, still 4,17,4791.
defbootstr wd.debug=i output:
%floppy 0x03F2-0x03F7 6 2 unit=0 type=135ds18
wd 0/0: IDENTIFY_DEVICE: Status 7F, Error FF (no device)
wd 0/1: IDENTIFY_DEVICE: Status 58: Error 00
wd 0/1: non-ATAPI device present
wd 1/0: IDENTIFY_DEVICE: Status 51, Error 04
wd 1/0: ATAPI_IDENTIFY: Status 58, Error 00, ATAPI = yes
wd 1/0: IDENTIFY_DEVICE: Status 00, Error 00 (no device)
%adapter 0x0170-0x0177 15 - type=IDE ctlr=secondary dvr=wd
%eeG0 0x1100-0x111F 9 - type=PRO/1000 00:15:17:01:52:aa
%cd-rom - - - type=IDE ctlr=sec cfg=mst dvr=Srom->wd
%disk 0x01F0-0x01F7 14 - type=W0 unit=0 cyls=4791 hds=4 secs=17
mem: total = 3666160k, kernel = 441348k, user = 3224812k
swapdev = 1/41, swplo = 0, nswap = 8379454, swapmem = 4189724k
rootdev = 1/42, pipedev = 1/42, dumpdev = 1/41
kernel: HZ = 100, i/o bufs = 366248k (high bufs = 359924k)
INIT: SINGLE USER MODE
Rebooting with defbootstr wd.debug=u output:
%floppy 0x03F2-0x03F7 6 2 unit=0 type=135ds18
wd: didn't find any specific known PCI IDE controller, trying by class
wd: PCI bus/dev/func 0/31/2, vend/dev 8086/27C0, prog_if 80, BMIBA 00000
wd: unknown but possibly usable PCI IDE controller; assuming UDMA 133
wd: if incorrect, add wd.udma=33 (or 66 or 100) to your bootstring.
wd: Drive max supported mode = 6, BIOS selected mode = 5
wd: Drive using BIOS selected UDMA mode 5
wd 0/1: Common UDMA Mode 6, Max MBoard mode 6, Max dev supt 6
wd: Possible UDMA timing mismatch, bootstring may be required.
wd: add wd.udma=auto for driver attempted auto sense or
wd: wd.udma=off to usse Programmed I/O (PIO) instead of UDMA.
%adapter 0x0170-0x0177 15 - type=IDE ctlr=secondary dvr=wd
%eeG0 0x1100-0x111F 9 - type=PRO/1000 00:15:17:01:52:aa
%cd-rom - - - type=IDE ctlr=sec cfg=mst dvr=Srom->wd
%disk 0x01F0-0x01F7 14 - type=W0 unit=0 cyls=4791 hds=4 secs=17
mem: total = 3666160k, kernel = 441348k, user = 3224812k
swapdev = 1/41, swplo = 0, nswap = 8379454, swapmem = 4189724k
rootdev = 1/42, pipedev = 1/42, dumpdev = 1/41
kernel: HZ = 100, i/o bufs = 366248k (high bufs = 359924k)
INIT: SINGLE USER MODE
Is there any secret switch to wd.debug=g that over rides the
wd_set_geom: romTab hds = 4 romTab sec = 17 romTab Cyl = -536867492 Magic = 0x00
wd_set_geom: ValidTrans, heads = 4, sec = 17, cyl = 4791
wd_set_geom: final heads = 4, sec = 17, cyl = 4791
"ValidTrans" that results in the wd_set_geom: final heads = 4, sec = 17,
cyl = 4791?
Attempting a fresh install from 5.0.6 media with wd506 bootload driver
was no better. Still had the problem with 4,17,4791 disk parameters.
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670