I think I have a duff hd. is the output below definately caused by a
broken disk?
It does the same in two sepperate boxes, one with 2.2.5 and the other
2.2.10. I tryed disabling dma, but no difference.
Script started on Sat Sep 25 21:57:39 1999
linux:~#fsck /dev/hdc3
Parallelizing fsck version 1.15 (18-Jul-1999)
e2fsck 1.15, 18-Jul-1999 for EXT2 FS 0.5b, 95/08/09
/dev/hdc3 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 1826848 (Attempt to read block from filesystem resulted in short read) while doing inode scan. Ignore error<y>? yes
Error reading block 1826979 (Attempt to read block from filesystem resulted in short read) while doing inode scan. Ignore error<y>? no
Error while scanning inodes (457856): Can't read next inode
linux:~#
linux:~#dmesg -c
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=5838536, sector=3653696
end_request: I/O error, dev 16:03 (hdc), sector 3653696
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=5838536, sector=3653696
end_request: I/O error, dev 16:03 (hdc), sector 3653696
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=5838799, sector=3653959
end_request: I/O error, dev 16:03 (hdc), sector 3653959
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=5838799, sector=3653959
end_request: I/O error, dev 16:03 (hdc), sector 3653959
linux:~#exit
Script done on Sat Sep 25 21:58:39 1999
Thanks
Regards
-- Rob Murray- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/