On 6/22/07, Carlos E. R. <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Friday 2007-06-22 at 18:33 -0400, Greg Freemyer wrote:
> On 6/22/07, Carlos E. R. <robin.listas@> wrote:
> > | Jun 19 03:16:57 axis kernel: sdb: Current: sense key: Medium Error
> > | Jun 19 03:16:57 axis kernel: Additional sense: Unrecovered readerror -
> > | auto reallocate failed
> > | Jun 19 03:16:57 axis kernel: end_request: I/O error, dev sdb,
> > | sector25690407
> >
> > Remapping has already failed.
>
> failed on a read the way I read it.
That is irrelevant: remapping was triggered and failed.
> I suggested to do a write. I don't know what subsystem generated the
> above. Maybe the dmraid layer tried a write after the failed read?
> Don't know, but I would still try to do a write manually via dd.
Something tried remapping and failed, and that is the important thing. If
it is the HD remapping that failed, as I think it is, then the failure is
crucial and the HD needs replacing ASAP, no toying.
In fact, trying to write to that sector will probably fail and the
remapping will fail, too. Should fail.
That's why reading the SMART log is so important in this case. If he has
10.0 and smartctl can't read it, then he should use a 10.2 rescue system
and read that log.
Or replace the disk first, investigate later.
I googled the error message.
Found it in
http://tldp.org/HOWTO/archived/SCSI-Programming-HOWTO/SCSI-Programming-HOWTO-22.html
So it appears to be coming out of the SCSI layer that sits above
libata. As I said before, I would not trust those error messages
since there is not a good mapping of ATA errors into the SCSI world.
Checking smart logs makes sense, but based on that single error I
would not be replacing hardware.
Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
