fsck <=> disk problem
Randal Abler
randy at gtuplab.UUCP
Thu May 26 07:20:26 AEST 1988
I have a VAXstation II running Ultrix, and am having trouble
dealing with Bad Blocks on a third party drive. My question
for the net is:
When fsck reports a bad block, say BLK 243125 for example,
how does that map into the logical block numbers for the drive?
Do I just add the partition table offset for that partition on the
drive? Given the correct logical block number, I should be able
to map out that block.
Vital Statistics:
Drive Controller Dilog DQ686 (ESDI controller)
Disk Drive Maxtor 4380E (320MB, 5.25" ESDI Disk)
Randy Abler
EE-CERL
Georgia Tech
gtuplab!randy
More information about the Comp.unix.ultrix
mailing list