Jeff Abrahamson on 30 Aug 2005 02:37:13 -0000 |
A crash caused me to have to fsck a ext3 partition. At least, I think that's what happened. This is a pretty new disk, about a month old. But the boot errors when running fsck look like this: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=174587984, high=10, low=6815824, sector=174587983 end_request: I/O error, dev hdb, sector 174587983 Buffer I/O error on device hdb1, logical block 87293960 hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=174587984, high=10, low=6815824, sector=174587983 end_request: I/O error, dev hdb, sector 174587983 Buffer I/O error on device hdb1, logical block 87293960 hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=174587984, high=10, low=6815824, sector=174587983 end_request: I/O error, dev hdb, sector 174587983 Buffer I/O error on device hdb1, logical block 87293960 The boot log also shows the following: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended EXT3 FS on hdb1, internal journal But then mount was willing to mount the partition anyway. Weird. I'm thinking I'm going to copy off what I can before doing more. But I'd really like to know what's going on. Any thoughts? I've had three disks in the past year "fail" with this sort of error. The last two I was willing to believe the disks had died, but this one is too new and the pattern too established. -- Jeff Jeff Abrahamson <http://www.purple.com/jeff/> +1 215/837-2287 GPG fingerprint: 1A1A BA95 D082 A558 A276 63C6 16BF 8C4C 0D1D AE4B Attachment:
signature.asc ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|