Marking sectors on IDE drives as bad

Marking sectors on IDE drives as bad

[Wahlman, Petter]

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 { AddrMarkNotFound
}, LBAsect=10262250, sector=1311147
Jan 22 09:31:29 evil kernel: ide0: reset: success
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=0x40 { UncorrectableError
}, LBAsect=10262250, sector=1311147
Jan 22 09:31:29 evil kernel: end_request: I/O error, dev 03:05 (hda), sector
1311147

Is it possible to somehow mark the above sector as bad (in ll_rw_block.c or
similar) to circumvent the problem?


please CC to me, because i'm not on this list.


thanks


Petter Wahlman

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Marking sectors on IDE drives as bad

[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 { AddrMarkNotFound
> }, LBAsect=10262250, sector=1311147
> Jan 22 09:31:29 evil kernel: ide0: reset: success
> 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=0x40 { UncorrectableError
> }, LBAsect=10262250, sector=1311147
> Jan 22 09:31:29 evil kernel: end_request: I/O error, dev 03:05 (hda), sector
> 1311147
> 
> Is it possible to somehow mark the above sector as bad (in ll_rw_block.c or
> similar) to circumvent the problem?

Chances are, you should replace the drive, because this sort of problem
usually gets worse as time goes on.

That said, it is possible for ext2 to mark the sectors bad (assuming you
use ext2 and not reiserfs), and then they will never be used.  You can
use the "badblocks" program in conjunction with e2fsck or mke2fs to mark
the blocks bad in the filesystem.

I would suggest keeping good backups after that.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

RE: Marking sectors on IDE drives as bad

[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 mentioned error: 

Jan 26 10:32:37 evil kernel: hda: read_intr: error=0x01 { AddrMarkNotFound
}, LBAsect=10262250, sector=1311147
Jan 26 10:32:37 evil kernel: ide0: reset: success
Jan 26 10:32:37 evil kernel: hda: read_intr: status=0x59 { DriveReady
SeekComplete DataRequest Error }
Jan 26 10:32:37 evil kernel: hda: read_intr: error=0x01 { AddrMarkNotFound
}, LBAsect=10262250, sector=1311147
Jan 26 10:32:37 evil kernel: end_request: I/O error, dev 03:05 (hda), sector
1311147



Petter Wahlman


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Marking sectors on IDE drives as bad

[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 { AddrMarkNotFound
> }, LBAsect=10262250, sector=1311147
> Jan 26 10:32:37 evil kernel: ide0: reset: success
> Jan 26 10:32:37 evil kernel: hda: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }

IDE layer knows nothing about ext2 marked badblocks.
Did you turn off multicount (PIO) and readahead (DMA) for this disk
using hdparm ?

However note that some ext2 structure information is not relocable.
So if bad blocks hit them you lose.

Andrzej
-- 
=======================================================================
  Andrzej M. Krzysztofowicz               ankry@mif.pg.gda.pl
  phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math.,   Technical University of Gdansk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/