Re: Marking sectors on IDE drives as bad

2001-01-26 Thread Andrzej Krzysztofowicz
"Wahlman, Petter wrote:" > The problem still persist, even after marking the respective block with: > badblocks -n -o /var/log/badblocks, > and e2fsck -l /var/log/badblocks > fsck is forced at boot, with the previously mentioned error: > > Jan 26 10:32:37 evil kernel: hda: read_intr: error=0x01

RE: Marking sectors on IDE drives as bad

2001-01-26 Thread Wahlman, Petter
The problem still persist, even after marking the respective block with: badblocks -n -o /var/log/badblocks, and e2fsck -l /var/log/badblocks the corrupted block is: dumpe2fs -b /dev/hda5 dumpe2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 655573 fsck is forced at boot, with the previously men

Re: Marking sectors on IDE drives as bad

2001-01-23 Thread Andreas Dilger
You write: > I'm experiencing some fscking problems due to a defective IDE drive. > > exerpt from /var/log/messages: > Jan 22 09:31:29 evil kernel: hda: read_intr: status=0x59 { DriveReady > SeekComplete DataRequest Error } > Jan 22 09:31:29 evil kernel: hda: read_intr: error=0x01 { AddrMarkNotFo