Messages in this thread | | | Date | Fri, 24 May 2002 07:56:34 +0200 | From | Vojtech Pavlik <> | Subject | Re: [reiserfs-dev] Re: IDE problem: linux-2.5.17 |
| |
On Fri, May 24, 2002 at 02:23:51AM +0200, Lionel Bouton wrote: > On Fri, May 24, 2002 at 12:55:25AM +0200, Vojtech Pavlik wrote: > > > > If you rewrite the whole drive with zeros (or the original data) sector > > by sector, the uncorrectable errors will go away. I've done this to my > > 307030 and it works fine again. (Fortunately for me the errors were only > > in my swap partition). > > > > Don't know for the whole drive yet (currently running) but when I did a mkraid > on a raid5 array using 4 partitions on the same drive the sync thread ended > and left the array in degraded mode after a bunch of : > May 24 02:05:06 twins kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } > May 24 02:05:06 twins kernel: hdd: dma_intr: error=0x40 { UncorrectableError }, LBA sect=2097375, sector=2097298 > May 24 02:05:06 twins kernel: end_request: I/O error, dev 16:41 (hdd), sector 2097298 > > Then I tried to zero the offending sectors with a slight margin : > [root@twins root]# dd if=/dev/zero of=/dev/hdd1 count=200 bs=512 seek=2097200 > dd: writing /dev/hdd1': Erreur d'entrée/sortie > 113+0 enregistrements lus. > 112+0 enregistrements écrits. > > Same error each time, seems sector 2097312 is not my friend. > > dd if=/dev/zero of=/dev/hdd bs=<cylinder_size> running. > > Too bad lsof doesn't show offsets... > I can't tell if dd passed the offending sector :-|
Well, if writing failed, it means the drive has ran out of relocatable sectors. That's too bad ... best to send it in for replacement.
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |