kernel: read_intr error

kernel: read_intr error

Post by Sysa » Thu, 27 Nov 1997 04:00:00



I seem to have a bad sector on my HD.  I've been getting a lot of
these messages in my log the past few days:

Nov 26 10:37:58 cardinal kernel: hda: read_intr: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Nov 26 10:37:58 cardinal kernel: hda: read_intr: error=0x40 {
UncorrectableError }, LBAsect=57086, sector=57023
Nov 26 10:37:58 cardinal kernel: end_request: I/O error, dev 03:01,
sector 57023
Nov 26 10:37:59 cardinal kernel: hda: read_intr: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Nov 26 10:37:59 cardinal kernel: hda: read_intr: error=0x40 {
UncorrectableError }, LBAsect=57086, sector=57023
Nov 26 10:37:59 cardinal kernel: end_request: I/O error, dev 03:01,
sector 57023
Nov 26 10:38:00 cardinal kernel: hda: read_intr: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Nov 26 10:38:00 cardinal kernel: hda: read_intr: error=0x40 {
UncorrectableError }, LBAsect=57086, sector=57023
Nov 26 10:38:00 cardinal kernel: end_request: I/O error, dev 03:01,
sector 57023
Nov 26 10:38:01 cardinal kernel: hda: read_intr: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Nov 26 10:38:01 cardinal kernel: hda: read_intr: error=0x40 {
UncorrectableError }, LBAsect=57086, sector=57023
Nov 26 10:38:01 cardinal kernel: end_request: I/O error, dev 03:01,
sector 57023

Anyone knows how to solve this?

Thanks!

 
 
 

kernel: read_intr error

Post by Anyone for thermonuclear tenni » Thu, 27 Nov 1997 04:00:00


On Wed, 26 Nov 1997 16:00:09 GMT, a small green fish snuck into
Sysadm's internet account in order to express the following:

Quote:> I seem to have a bad sector on my HD.  I've been getting a lot of
> these messages in my log the past few days:
> Nov 26 10:37:58 cardinal kernel: hda: read_intr: status=0x59 {
> DriveReady SeekComplete DataRequest Error }
> Nov 26 10:37:58 cardinal kernel: hda: read_intr: error=0x40 {
> UncorrectableError }, LBAsect=57086, sector=57023
> Nov 26 10:37:58 cardinal kernel: end_request: I/O error, dev 03:01,
> sector 57023

Yep.  You have entered the Oh Shit Zone, named for kernel behaviour
when encountering unreadable blocks.

Quote:> Anyone knows how to solve this?

If you have a relatively recent e2fsck, you can map that problem child
out by unmounting the volume (shutdown and boot from a rescue floppy
or bring the sys down to single user if need be) and running

 e2fsck -c /dev/hda?

(replace the ? with the appropriate number - 03:01 suggests to me hda1).

If your e2fsck doesn't support the -c option, beg borrow or steal one
that does or you'll be stuck with doing the backup-mkfs-restore dance.
(mke2fs -c also checks for bad blocks while making a new filesystem)

Find out your e2fsck version by doing

 e2fsck -V

If it's 1.0 or later I think it should support the check option.
If it's 0.5, it won't.  Check the man page if it's before 1.10,
as that's what I use and thus the only one I can guarantee as
having the option.

 
 
 

1. Kernel message: hda: read_intr: error 0x40 {UncorrectableError} LBAsect=2572558 etc

So I was trying to get a man page this morning, while logged in as root for
maintenance, and up pops a Kernel Panic message and no prompt.  I was able to
switch to another console and shutdown -r, but after the usual shutdown
messages the machine DID NOT reboot.  Only hard reset would work, and upon
restart, I got nasty messages as follows:

hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=2572558, sector
524302
.
.
<repeats a few times>
.
ide0: do_ide_reset: success
.
.
<repeat first message again>
.
end_request: I/O error, dev 0303, sector 524302
.

then a big message to run fsck manually and a dump to single user mode.

Running fsck found a bunch of errors, and eventually I could reboot, but
still not coming up right.

This happened several tries, at least once system did come up, BUT seems like
something is very wrong.  Running badblocks on the partition goes VERRRRY
slowly and starts to find the same bad blocks each time - I haven't let it run
through since it appears it may take HOURS!  

So, is it something I did, and recoverable at least by re-formatting with
mke2fs -c to find the bad blocks, or has something actually gone wrong with
the disk?  (This 1.6 GB disk was new about 3 weeks ago).

Opinions sought - thanks.

Geoff


2. Motif development for Linux

3. lod kernel: hda: read_intr: error = 0x04 ?

4. 3c503 network config (x86)

5. WHY - kernel: hda: read_intr: error = 0x04

6. IP Masq/Forwarding just stops after a bit

7. read_intr errors, but badblocks doesn't help... kernel panics...

8. df incorrectly reports remaining space (Solaris 2.4)

9. WHY - kernel: hda: read_intr: error = 0x04

10. HD read_intr error: KERNEL PANIC?

11. kernel error: hda: read_intr: status=0x59 { DriveReady SeekComp

12. hda: read_intr error=0x59 DriveReady SeekComplete DataRequest Error

13. HD: read_intr: error