Re: [Hampshire] Laptop Hardrive

Top Page

Reply to this message
Author: Vic
Date:  
To: Hampshire LUG Discussion List
Subject: Re: [Hampshire] Laptop Hardrive


> Example of a syslog entry for one of the above:
> Apr 27 11:26:42 quad kernel: [ 3821.830237] sd 2:0:0:0: [sde]
> Unhandled sense code


"Unhandled sense code". That's a good start. Do you think this is a
reallocation?

> Apr 27 11:26:42 quad kernel: [ 3821.830239] sd 2:0:0:0: [sde] Result:
> hostbyte=DID_OK driverbyte=DRIVER_SENSE
> Apr 27 11:26:42 quad kernel: [ 3821.830243] sd 2:0:0:0: [sde] Sense
> Key : Medium Error [current] [descriptor]


"Medium Error". The disk has failed.

> Apr 27 11:26:42 quad kernel: [ 3821.830261] sd 2:0:0:0: [sde] Add.
> Sense: Unrecovered read error - auto reallocate failed


"Unrecovered read error". The data is already unreadable.

> Apr 27 11:26:42 quad kernel: [ 3821.830274] end_request: I/O error,
> dev sde, sector 256711459


And the failure is reported[1] to the kernel.

> So, here it is trying to reallocate the sector due to a read fault,
> but failed to do so.
> In smartctl, the drive only had 2 reallocated sectors so the
> reallocate should have succeeded as there were spare sectors left for
> reallocation.


OK, now think through things a little.

You're not getting assorted prefail warnings, you're getting a medium
error. By the time this log excert was started, the data had already left
the drive. It was not available for copying.

So of course the reallocation would have failed. You can't copy something
if you don't have the thing to copy in the first place.

> I suspect a firmware bug.


I would say your logic is entirely flawed. This log does not show a
firmware bug.

> The drive was replaced with a different model.


That's up to you. It's your money.

Vic.

[1] "reported" might be the wrong word for the operation, but it shows the
overall effect :-)