Nick Lidakis:
>
> [ 2468.452915] sd 2:0:0:0: [sdc] Unhandled error code
> [ 2468.452919] sd 2:0:0:0: [sdc]
> [ 2468.452922] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> [ 2468.452926] sd 2:0:0:0: [sdc] CDB:
> [ 2468.452928] Read(10): 28 00 03 7e 20 00 00 00 08 00
> [ 2468.452940] end_request: I/O error, dev sdc, sector 58597376
> [ 2468.452948] Buffer I/O error on device sdc6, logical block 0
I am not an expert with the exact meaning of these messages, but to me
this looks like a hardware error. Since you tested this in a different
machine we can probably rule out issues with the controller, cable or
PSU. That doesn't leave very much but the disk itself.
One other option might be to ensure that AHCI is enabled in your
system's BIOS. Some people suggest these messages can be fixed this way.
One example: https://bugzilla.redhat.com/show_bug.cgi?id=450848. Do you
have "port is slow to respond" or "soft resetting link" messages as
well?
> I don't know if this is just corrupted data or a dead/dying SSD. I'll look
> at the man pages for the S.M.A.R.T tools.
A good start is smartctl -a /dev/sdc. If you post the output here,
please make sure not to introduce additional linebreaks. Attaching it as
a plain text file would be fine.
If you have spare space you can try ddrescue. It creates a bit-by-bit
copy of your disk (or what's left of it). You can then use photorec or
similar tools on that disk image without risking to destroy even more
data.
J.
--
I use a Playstation to block out the existence of my partner.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>
Attachment:
signature.asc
Description: Digital signature