ata errors -> read-only root partition. Hardware issue?
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 11 lines · jerome lacoste
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
SCSI error : <2 0 0 0> return code =0x8000002
sda: Current: sense key: Medium Error
Additional sense: Unrecovered read error - auto reallocate failedend_request: I/O error, dev sda, sector 67801511
That sounds an awful lot like a failing hard drive.
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/
Quoted 13 lines · Robert Hancock
Quoted 11 lines · jerome lacoste
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
SCSI error : <2 0 0 0> return code =0x8000002
sda: Current: sense key: Medium Error
Additional sense: Unrecovered read error - auto reallocate failedend_request: I/O error, dev sda, sector 67801511
Quoted 1 line
That sounds an awful lot like a failing hard drive.
Thanks Robert,
So what is the procedure in Linux to test for these problems? I was thinking:
- scan for bad blocks
- maybe check the SMART results if they are available
- memory check: memtest86 & memtest86+ tests (just in case)
Anything I missed?
Does someone know a diagnostics utilities CD (a la Dell diagnostics) that you can boot on your PC, let run for x hours and get feedback?
Cheers,
Jerome
Quoted 1 line · jerome lacoste
- scan for bad blocks
Read the entire disk (write will hide and clean up errors by reallocating)
Quoted 1 line
- maybe check the SMART results if they are available
Definitely - failures are in the smart log
Quoted 1 line
- memory check: memtest86 & memtest86+ tests (just in case)
memory failures generally show a different pattern, you get corruption not errors off disks.
Alan
Quoted 5 lines · Alan Cox
Quoted 1 line · jerome lacoste
- scan for bad blocks
Read the entire disk (write will hide and clean up errors by reallocating)
something like should be sufficient right?
cat /dev/sdax > /dev/null
Thanks a lot.
Jerome
Quoted 10 lines · jerome lacoste
Quoted 5 lines · Alan Cox
Quoted 1 line · jerome lacoste
- scan for bad blocks
Read the entire disk (write will hide and clean up errors by reallocating)
something like should be sufficient right?
cat
/dev/sdax>/dev/null
I did something slightly different:
root@manies:~# cat /dev/sda > /dev/null cat: /dev/sda: Input/output error
and in dmesg, problems show again:
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
SCSI error : <2 0 0 0> return code = 0x8000002
sda: Current: sense key: Medium Error
Additional sense: Unrecovered read error - auto reallocate failedend_request: I/O error, dev sda, sector 39088832
Buffer I/O error on device sda, logical block 4886104
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
....
smartmontools is unfortunately not installed but I probably don't need it.
Could something else (bad cable or disk controller ) trigger these issues?
It would be great if we users had a quick way to decipher these messages.
E.g.
"Buffer I/O error on device xxxx, logical block yyyyyyy"
Usualy a disk failure, may also be caused by....
Etc...
Noone has made an "Identifying Hardware failures HowTo"?
Jerome
Quoted 40 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of jerome lacoste
Sent: Wednesday, January 11, 2006 9:26 AM
To: Alan Cox
Cc: Robert Hancock; linux-kernel
Subject: Re: ata errors -> read-only root partition. Hardware issue?Quoted 10 lines · jerome lacoste
Quoted 5 lines · Alan Cox
Quoted 1 line · jerome lacoste
- scan for bad blocks
Read the entire disk (write will hide and clean up errors by reallocating)
something like should be sufficient right?
cat
/dev/sdax>/dev/nullI did something slightly different:
root@manies:~# cat /dev/sda > /dev/null cat: /dev/sda: Input/output errorand in dmesg, problems show again:
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
Quoted 8 lines
SCSI error : <2 0 0 0> return code =
0x8000002
sda: Current: sense key: Medium Error
Additional sense: Unrecovered read error - auto reallocate failedend_request: I/O error, dev sda, sector 39088832 Buffer I/O error on device sda, logical block 4886104
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
....
If it is repeatable on the exact same block(s)/sector(s) every time, and it reads lots of other blocks/sectors just fine, it is very unlikely to be anything but a disk error.
Roger
Quoted 11 lines · jerome lacoste
Could something else (bad cable or disk controller ) trigger these issues?
It would be great if we users had a quick way to decipher these messages.
E.g.
"Buffer I/O error on device xxxx, logical block yyyyyyy"
Usualy a disk failure, may also be caused by....
This is not a bad idea, "status=0x51 { DriveReady SeekComplete Error }" in my experience always indicates a failing hard drive. Maybe a "Possible drive or media failure" could be added?
Lee
Quoted 10 lines · Lee Revell
Quoted 8 lines · jerome lacoste
Could something else (bad cable or disk controller ) trigger these issues?
It would be great if we users had a quick way to decipher these messages.
E.g.
Quoted 8 lines
Quoted 3 lines
"Buffer I/O error on device xxxx, logical block yyyyyyy"
Usualy a disk failure, may also be caused by....
This is not a bad idea, "status=0x51 { DriveReady SeekComplete Error }" in my experience always indicates a failing hard drive. Maybe a "Possible drive or media failure" could be added?
I posted this in another thread, but reposting here. This is an Asus P5GDC-V MB with WD740GD harddisk.
The machine was locking hard (no KBD, video, network) after a few hours of uptime with kenrels 2.6.12 ... 2.6.14.4, now running 2.6.15 with patched sk98lin. After some random time (up to 2d), the dmesg output is full of these:
[snip, see below as it is identical]
the fs is mounted ro, and most I/O is dead (like trying to use /sbin/shutdown resulting in I/O error). I checked the disk with WD Data LifeGuardTools and no errors were reported. smartctl says this:
ooops, the machine is again borked and not here, will post smartctl tomorrow, but basicaly no errors are reported after extended tests.
Now dmesg says:
[17225533.452000] ata1: port reset, p_is 40000001 is 1 pis 0 cmd c017 tf 471
ss 113 se 0
[17225533.452000] ata1: translated ATA stat/err 0x71/04 to SCSI SK/ASC/ASCQ
0xb/00/00
[17225533.452000] ata1: status=0x71 { DriveReady DeviceFault SeekComplete
Error }
[17225533.452000] ata1: error=0x04 { DriveStatusError }
[17225533.452000] ata1: port reset, p_is 40000001 is 1 pis 0 cmd c017 tf 471
ss 113 se 0
[17225533.452000] ata1: translated ATA stat/err 0x71/04 to SCSI SK/ASC/ASCQ
0xb/00/00
[17225533.452000] ata1: status=0x71 { DriveReady DeviceFault SeekComplete
Error }
[17225533.452000] ata1: error=0x04 { DriveStatusError }
[17225533.452000] ata1: port reset, p_is 40000001 is 1 pis 0 cmd c017 tf 471
ss 113 se 0
[17225533.452000] ata1: translated ATA stat/err 0x71/04 to SCSI SK/ASC/ASCQ
0xb/00/00
[17225533.452000] ata1: status=0x71 { DriveReady DeviceFault SeekComplete
Error }
[17225533.452000] ata1: error=0x04 { DriveStatusError }
[17225533.452000] ata1: port reset, p_is 40000001 is 1 pis 0 cmd c017 tf 471
ss 113 se 0
[17225533.452000] ata1: translated ATA stat/err 0x71/04 to SCSI SK/ASC/ASCQ
0xb/00/00
[17225533.452000] ata1: status=0x71 { DriveReady DeviceFault SeekComplete
Error }
[17225533.452000] ata1: error=0x04 { DriveStatusError }
[17225533.452000] ata1: port reset, p_is 40000001 is 1 pis 0 cmd c017 tf 471
ss 113 se 0
[17225533.452000] ata1: translated ATA stat/err 0x71/04 to SCSI SK/ASC/ASCQ
0xb/00/00
[17225533.452000] ata1: status=0x71 { DriveReady DeviceFault SeekComplete
Error }
[17225533.452000] ata1: error=0x04 { DriveStatusError }
[17225533.452000] sd 0:0:0:0: SCSI error: return code = 0x8000002
[17225533.452000] sda: Current: sense key=0xb
[17225533.452000] ASC=0x0 ASCQ=0x0
[17225533.452000] end_request: I/O error, dev sda, sector 17632540
[17225533.452000] Buffer I/O error on device sda3, logical block 1216070
[17225533.452000] lost page write due to I/O error on sda3
[17225677.824000] ReiserFS: sda3: warning: clm-6006: writing inode 10055 on
readonly FS
[17225677.824000] ReiserFS: sda3: warning: clm-6006: writing inode 10055 onreadonly FS
At least the good thing is that I can ssh now.
After soft reboot (for i in s u s b; do echo $i >/proc/sysrq-trigger; sleep 1;done ) form a borked state (like now) the bios fails to detect the harddisk and hangs indefinately...
Kalin.
P.S. Will try sky2 tomorrow instead of sk98lin.P.P.S. Also askid in "2.6.15 and CONFIG_PRINTK_TIME" thread, but any idea why is this strange time printed since boot?
Signature · 3 lines
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]| +-> http://ThinRope.net/ <-+ |[ ______________________ ]|