Am Dienstag, 15. Oktober 2002 09:51 schrieb Klaus Imgrund:
> On Tue, 15 Oct 2002 12:49:19 +0800
>
> Crispin Wellington <[EMAIL PROTECTED]> wrote:
> > On Tue, 2002-10-15 at 04:47, Bruce wrote:
> > > I figured this is a hardware/bad block problem. I rebooted
> > > with a rescue disk, and ran reiserfsck --check /dev/hda2, and
> > > received the following error:
> > >
> > > hda: read_intr: error-0x40 { UncorrectableError },
> > > LBAsect=148574, sector=148511 end_request: I/O errore, dev
> > > 03:02 (hda), sector 148511
>
> Don't give up on that drive yet.I had the same error message on
> one hdd after a power failure. Since it was under warranty but
> not broken enough I ran a test on it for 48 hrs. and that didn't
> do anything to it. Seems like some parts of the kernel got
> screwed up from the power failure. After I reinstalled the OS the
> drive works fine without any hickups or error messages.
>
> Prost,
>
> Klaus
Hello,
I made similar experiences with my seagate. After compiling a new
kernel I had those messages. Do you use a via 686 chipset? Mabe you
have to choose an special option in your config to avoid such
messages in /var/log/messages.
I found this discussion on that issue:
http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&oe=UTF-8&threadm=slrn9vnna0.859.efflandt%40typhoon.xnet.com&rnum=2&prev=/groups%3Fq%3Dvia%2Bkernel%2B%2522read_intr:%2Berror-0x40%2B%257B%2BUncorrectableError%2B%257D%2522%26hl%3Dde%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3Dslrn9vnna0.859.efflandt%2540typhoon.xnet.com%26rnum%3D2
http://groups.google.de/groups?q=via+kernel+%22hda:+read_intr:+error-0x40+%7B+UncorrectableError+%7D%22&hl=de&lr=&ie=UTF-8&oe=UTF-8&selm=handler.9383.D9383.90920670422716.ackdone%40bugs.debian.org&rnum=3
http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&oe=UTF-8&threadm=3C3DABBC.4090302%40flock.org&rnum=6&prev=/groups%3Fq%3Dvia%2Bkernel%2B%2522hda:%2Bread_intr:%2Berror-0x40%2B%257B%2BUncorrectableError%2B%257D%2522%26hl%3Dde%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3D3C3DABBC.4090302%2540flock.org%26rnum%3D6
With this search I found something about powermanagement used by
the bios but not build into the kernel:
http://groups.google.de/groups?q=via++status%3D0x59+vt82c686a&btnG=Google-Suche&hl=de&lr=&ie=UTF-8&oe=UTF-8
|Von:Brian McGroarty ([EMAIL PROTECTED])
|Betrifft:Re: DriveStatusError BadCRC on hda
|
|View this article only
|Newsgroups:linux.debian.user
|Datum:2001-08-18 18:20:08 PST
|
|On Sun, Aug 19, 2001 at 03:05:42AM +0100, Christian Jaeger wrote:
|> Hello
|>
|> I've seen some messages in the system log and am wondering what
|to do
|> with them:
|>
|> Aug 14 06:25:53 pflanze kernel: hda: timeout waiting for DMA
|> Aug 14 06:25:53 pflanze kernel: ide_dmaproc: chipset supported
|> ide_dma_timeout func only: 14
|> Aug 14 06:25:53 pflanze kernel: hda: irq timeout: status=0x59 {
|> DriveReady SeekComplete DataRequest Error }
|> Aug 14 06:25:53 pflanze kernel: hda: irq timeout: error=0x84 {
|> DriveStatusError BadCRC }
|
|With a previous machine, I recall seeing the above when a hard
|drive
|was configured by the BIOS to power down after some period of
|non-use,
|but power management wasn't built into the kernel. There was never
|any
|data loss, only the disturbing messages.
|
|Building a kernel with power support fixed it.
|
|I use that disk now for several month without any problems.
|
I found these options in my .config:
CONFIG_BLK_DEV_VIA82CXXX=y
CONFIG_VIA_RHINE=m
Unfortunateley I don't remember exactly the circumstances and the
solving of my harddiskproblem. It was on a mandrake system. Maybe
It was helpful to you.
regards
gerhard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
