From: jerome lacoste <jerome.lacoste@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ata errors -> read-only root partition. Hardware issue?
Date: Wed, 11 Jan 2006 16:26:18 +0100 [thread overview]
Message-ID: <5a2cf1f60601110726r46805e1dl784f0a0ca20c128@mail.gmail.com> (raw)
In-Reply-To: <5a2cf1f60601110552t5e9afa0dr7785b22ae6dbd99b@mail.gmail.com>
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
next prev parent reply other threads:[~2006-01-11 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ttip-Xh-13@gated-at.bofh.it>
2006-01-10 23:54 ` ata errors -> read-only root partition. Hardware issue? Robert Hancock
2006-01-11 8:30 ` jerome lacoste
2006-01-11 13:38 ` Alan Cox
2006-01-11 13:52 ` jerome lacoste
2006-01-11 15:26 ` jerome lacoste [this message]
2006-01-11 15:55 ` Roger Heflin
2006-01-11 17:44 ` Lee Revell
2006-01-13 17:04 ` Kalin KOZHUHAROV
2006-01-10 15:06 jerome lacoste
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=5a2cf1f60601110726r46805e1dl784f0a0ca20c128@mail.gmail.com \
--to=jerome.lacoste@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockr@shaw.ca \
--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;
as well as URLs for NNTP newsgroup(s).