View topic - M2-drive fails to be read

Main » Forums home » Flash storage, SSD

All times are UTC - 5 hours [ DST ]

Switch to mobile style

M2-drive fails to be read

Page 1 of 1

[ 2 posts ]

Print view

Previous topic | Next topic

Author

Message

bos

Post subject: M2-drive fails to be read

Posted: October 23rd, 2020, 7:45

Joined: October 20th, 2014, 5:25
Posts: 138
Location: Sweden

A customer brought me this drive which I cannot figure out the root-cause on. Attaching the drive gives me this in syslog:

Code:

Oct 23 13:40:10 dr kernel: [  567.000141] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 23 13:40:10 dr kernel: [  567.000557] ata1.00: ATA-10: SAMSUNG MZNLN256HMHQ-000H1, MAV21H3Q, max UDMA/100
Oct 23 13:40:10 dr kernel: [  567.000563] ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Oct 23 13:40:10 dr kernel: [  567.000983] ata1.00: configured for UDMA/100
Oct 23 13:40:10 dr kernel: [  567.000990] ata1: EH complete
Oct 23 13:40:10 dr kernel: [  567.001135] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG MZNLN256 MAV2 PQ: 0 ANSI: 5
Oct 23 13:40:10 dr kernel: [  567.001385] sd 0:0:0:0: Attached scsi generic sg1 type 0
Oct 23 13:40:10 dr kernel: [  567.001394] sd 0:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Oct 23 13:40:10 dr kernel: [  567.001399] sd 0:0:0:0: [sdb] 4096-byte physical blocks
Oct 23 13:40:10 dr kernel: [  567.001535] sd 0:0:0:0: [sdb] Write Protect is off
Oct 23 13:40:10 dr kernel: [  567.001580] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 23 13:40:41 dr kernel: [  597.824202] ata1: hard resetting link
Oct 23 13:40:51 dr kernel: [  607.836142] ata1: hard resetting link
Oct 23 13:41:01 dr kernel: [  617.848116] ata1: hard resetting link
Oct 23 13:41:11 dr kernel: [  628.420141] ata1: link is slow to respond, please be patient (ready=0)
Oct 23 13:41:36 dr kernel: [  652.892150] ata1: limiting SATA link speed to 1.5 Gbps
Oct 23 13:41:36 dr kernel: [  652.892153] ata1: hard resetting link
Oct 23 13:41:41 dr kernel: [  658.080152] ata1.00: disabled
Oct 23 13:41:41 dr kernel: [  658.080158] ata1.00: device reported invalid CHS sector 0
Oct 23 13:41:41 dr kernel: [  658.080168] ata1: EH complete
Oct 23 13:41:41 dr kernel: [  658.080208] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080212] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080218] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080232] quiet_error: 4 callbacks suppressed
Oct 23 13:41:41 dr kernel: [  658.080274] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080277] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080281] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080350] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080353] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080357] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080409] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080411] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080415] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080449] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080452] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080455] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080493] ldm_validate_partition_table(): Disk read failed.
Oct 23 13:41:41 dr kernel: [  658.080508] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080510] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080513] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080547] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080549] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080552] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080602] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080604] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080607] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080640] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080642] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080646] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080683] Dev sdb: unable to read RDB block 0
Oct 23 13:41:41 dr kernel: [  658.080698] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080700] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080703] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080737] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080739] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080742] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080792] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080794] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080798] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 18 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080825] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080828] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080831] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 18 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080878] sd 0:0:0:0: [sdb] Unhandled error code
Oct 23 13:41:41 dr kernel: [  658.080880] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.080884] sd 0:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Oct 23 13:41:41 dr kernel: [  658.080902]  sdb: unable to read partition table
Oct 23 13:41:41 dr kernel: [  658.081051] sd 0:0:0:0: [sdb] READ CAPACITY(16) failed
Oct 23 13:41:41 dr kernel: [  658.081054] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.081057] sd 0:0:0:0: [sdb] Sense not available.
Oct 23 13:41:41 dr kernel: [  658.081110] sd 0:0:0:0: [sdb] READ CAPACITY failed
Oct 23 13:41:41 dr kernel: [  658.081112] sd 0:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 23 13:41:41 dr kernel: [  658.081115] sd 0:0:0:0: [sdb] Sense not available.
Oct 23 13:41:41 dr kernel: [  658.081236] sd 0:0:0:0: [sdb] Truncating mode parameter data from 12148 to 512 bytes
Oct 23 13:41:41 dr kernel: [  658.081260] sd 0:0:0:0: [sdb] Attached SCSI disk

I will have to tell the customer to contact Kroll because this is out of my league, but I'm still curious; is this a controller issue or a NAND-issue? Because I see that the drive can be identified correctly, which gives me the idea that the controller is working to a degree, but when trying to read CHS 0 everything goes bork, which tells me atleast one of the two NANDs are screwed.

Top

lcoughey

Post subject: Re: M2-drive fails to be read

Posted: October 23rd, 2020, 12:11

Joined: February 9th, 2009, 16:13
Posts: 2513
Location: Ontario, Canada

It is more of a translator issue, most of the time. Unfortunately, I don't believe it is a model supported by PC3000 and therefore not recoverable by most labs. I'd be surprised if Kroll can handle it, either. If I were you, I'd be looking for someone who has a way to work with the translator of this model of Samsung SSD and refer your client to them.

_________________
Luke
Recovery Force Data Recovery

Top

Page 1 of 1

[ 2 posts ]

Main » Forums home » Flash storage, SSD

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 10 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum