linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jerome lacoste <jerome.lacoste@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ata errors -> read-only root partition. Hardware issue?
Date: Wed, 11 Jan 2006 09:30:07 +0100	[thread overview]
Message-ID: <5a2cf1f60601110030u358c12fcscf79067cbc3eebe0@mail.gmail.com> (raw)
In-Reply-To: <43C4493A.4010305@shaw.ca>

On 1/11/06, Robert Hancock <hancockr@shaw.ca> wrote:
> jerome lacoste wrote:
> >
> > 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 67801511
>
> 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

  reply	other threads:[~2006-01-11  8:30 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 [this message]
2006-01-11 13:38     ` Alan Cox
2006-01-11 13:52       ` jerome lacoste
2006-01-11 15:26         ` jerome lacoste
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=5a2cf1f60601110030u358c12fcscf79067cbc3eebe0@mail.gmail.com \
    --to=jerome.lacoste@gmail.com \
    --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).