Should I just run e2fsck with the -c option so it will map the bad blocks that it finds? If so, what's the proper way to fsck the root filesystem since it's mounted?
Or should I use the diagnostic boot floppy that came with the Western Digital drive to do the mapping within the drive?
Also, is there an easy way to determine what files are affected?
You'll notice that the sectors are all consecutive multiples of eight. Is that expected due to interleaving or something, and thus indicates that one physical area of the disk is bad, or do I have multiple bad spots?
Thanks,
Larry
-----
Mar 17 07:56:17 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 17 07:56:17 localhost kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=46213637, sector=22806800
Mar 17 07:56:17 localhost kernel: end_request: I/O error, dev 03:07 (hda), sector 22806800
Mar 17 07:56:20 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 17 07:56:20 localhost kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=46213637, sector=22806808
Mar 17 07:56:20 localhost kernel: end_request: I/O error, dev 03:07 (hda), sector 22806808
Mar 17 07:56:22 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 17 07:56:22 localhost kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=46213637, sector=22806816
Mar 17 07:56:22 localhost kernel: end_request: I/O error, dev 03:07 (hda), sector 22806816
Mar 17 07:56:25 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 17 07:56:25 localhost kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=46213637, sector=22806824
Mar 17 07:56:25 localhost kernel: end_request: I/O error, dev 03:07 (hda), sector 22806824
-----
_______________________________________________ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
