Messages in this thread | | | Date | Wed, 11 Jan 2006 16:26:18 +0100 | From | jerome lacoste <> | Subject | Re: ata errors -> read-only root partition. Hardware issue? |
| |
On 1/11/06, jerome lacoste <jerome.lacoste@gmail.com> wrote: > On 1/11/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote: > > On Mer, 2006-01-11 at 09:30 +0100, jerome lacoste wrote: > > > - 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 failed end_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 - 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/
| |