From: Vojtech Pavlik <vojtech@suse.cz>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [reiserfs-dev] Re: IDE problem: linux-2.5.17
Date: Fri, 24 May 2002 07:56:34 +0200 [thread overview]
Message-ID: <20020524075634.A28157@ucw.cz> (raw)
In-Reply-To: <3CECF59B.D471F505@namesys.botik.ru> <3CECFC5B.3030701@evision-ventures.com> <20020523193959.A2613@namesys.com> <3CED004A.6000109@evision-ventures.com> <20020523234720.A7495@bouton.inet6-interne.fr> <20020524005525.H27005@ucw.cz> <20020524022351.A8230@bouton.inet6-interne.fr>
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
next prev parent reply other threads:[~2002-05-24 5:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 13:58 IDE problem: linux-2.5.17 Gryaznova E.
2002-05-23 14:17 ` Martin Dalecki
2002-05-23 17:48 ` Gryaznova E.
2002-05-23 18:03 ` Tomas Szepe
2002-05-23 18:44 ` Andre Hedrick
2002-05-23 17:49 ` Martin Dalecki
2002-05-23 19:11 ` Andre Hedrick
2002-05-23 19:13 ` Andre Hedrick
2002-05-24 15:05 ` Alan Cox
2002-05-23 22:40 ` Vojtech Pavlik
2002-05-23 18:07 ` Martin Dalecki
2002-05-23 22:42 ` Vojtech Pavlik
2002-05-23 22:37 ` Vojtech Pavlik
2002-05-23 14:27 ` Martin Dalecki
2002-05-23 15:39 ` [reiserfs-dev] " Oleg Drokin
2002-05-23 14:44 ` Martin Dalecki
2002-05-23 16:00 ` Oleg Drokin
2002-05-23 22:52 ` Vojtech Pavlik
2002-05-23 21:47 ` Lionel Bouton
2002-05-23 22:55 ` Vojtech Pavlik
2002-05-24 0:23 ` Lionel Bouton
2002-05-24 1:04 ` Andre Hedrick
2002-05-24 5:56 ` Vojtech Pavlik [this message]
2002-05-24 8:53 ` Lionel Bouton
2002-05-24 4:53 ` Oleg Drokin
2002-05-23 22:50 ` Vojtech Pavlik
2002-05-24 11:03 ` Martin Dalecki
2002-05-24 13:15 ` Vojtech Pavlik
2002-05-24 12:15 ` Martin Dalecki
2002-05-24 13:20 ` Vojtech Pavlik
2002-05-24 13:40 ` Martin Dalecki
2002-05-24 14:54 ` Vojtech Pavlik
2002-05-23 15:52 ` Tomas Szepe
2002-05-23 16:02 ` Oleg Drokin
2002-05-23 22:45 ` Vojtech Pavlik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020524075634.A28157@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox