On 6/22/07, Carlos E. R. <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Friday 2007-06-22 at 16:52 -0400, Greg Freemyer wrote:
> Also, SATA drives do not reallocate on read only on write.
Same as PATA. It is done by the disk hardware, no cpu intervention.
> Since the OP has the sector #, he should use dd to read in the sector
> from the good drive to a temp file. Then use dd to write it back out
> to the failed drive. In theory the bad drive will see that someone is
> writing to a bad sector and re-map it to one of the spare sectors.
That's not possible; it seems you haven't read previous posts:
| 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. 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.
FYI: I don't think the SATA error code interpretation by the SCSI
layer is 100% accurate, so I would not trust anything SATA related
that is being reported by the SCSI layer that libata is currently
kludged underneath. Hopefully someday libata will become its own full
fledged subsystem without any of the scsi core code causing confusion.
Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
