April 23rd, 2017, 11:40
April 23rd, 2017, 17:08
April 23rd, 2017, 18:56
April 24th, 2017, 2:44
April 24th, 2017, 9:36
April 24th, 2017, 13:40
April 24th, 2017, 14:12
sourcerer wrote:Please try to attach it to a Linux system and look at the output of "dmesg", whether you see anything there.
If you get messages like "COMRESET failed" after about 10-20 seconds, then the SSD hangs during initialisation.
April 24th, 2017, 15:55
April 24th, 2017, 17:29
[ 110.831727] scsi 8:0:0:0: Direct-Access Samsung SSD 850 EVO 250G B PQ: 0 ANSI: 0
[ 110.832233] sd 8:0:0:0: Attached scsi generic sg8 type 0
[ 110.832787] sd 8:0:0:0: [sdi] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[ 110.833899] sd 8:0:0:0: [sdi] Write Protect is off
[ 110.833903] sd 8:0:0:0: [sdi] Mode Sense: 3b 00 00 00
[ 110.836165] sd 8:0:0:0: [sdi] No Caching mode page found
[ 110.836171] sd 8:0:0:0: [sdi] Assuming drive cache: write through
...
[ 296.954366] sd 8:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[ 296.954373] sd 8:0:0:0: [sdi] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 296.954376] blk_update_request: I/O error, dev sdi, sector 0
[ 296.954380] Buffer I/O error on dev sdi, logical block 0, async page read
April 25th, 2017, 6:14
fzabkar wrote:ISTM that the drive IDs correctly, but does not allow read access.
- Code:
[ 110.831727] scsi 8:0:0:0: Direct-Access Samsung SSD 850 EVO 250G B PQ: 0 ANSI: 0
[ 110.832233] sd 8:0:0:0: Attached scsi generic sg8 type 0
[ 110.832787] sd 8:0:0:0: [sdi] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[ 110.833899] sd 8:0:0:0: [sdi] Write Protect is off
[ 110.833903] sd 8:0:0:0: [sdi] Mode Sense: 3b 00 00 00
[ 110.836165] sd 8:0:0:0: [sdi] No Caching mode page found
[ 110.836171] sd 8:0:0:0: [sdi] Assuming drive cache: write through
...
[ 296.954366] sd 8:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[ 296.954373] sd 8:0:0:0: [sdi] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 296.954376] blk_update_request: I/O error, dev sdi, sector 0
[ 296.954380] Buffer I/O error on dev sdi, logical block 0, async page read
Does smartctl (Linux) provide any information?
April 25th, 2017, 6:32
April 25th, 2017, 7:01
sourcerer wrote:Did you try to attach it through a USB-SATA interface? Is possible, please also try a native (PCI/...) SATA interface instead. (The USB2-SATA adapters usually hide some details due to limitations in the USB mass-storage protocol.)
Yes, it seems that the SSD starts but it has problems reading your data later on.
Has the SSD been unpowered for a longer period of time? (Months)
Does the SSD case look legitimate? The output from your logfile looks a bit strange to me, but I am not sure. I have seen a fake Samsung SSD in the wild already (which was sold by a reputable dealer). The indicators I found on that fake SSD were the following:
* A Samsung Logo was missing on a sticker on the SSD
* The serial number format was wrong
* A sticker was attached on the wrong side of the SSD, not covering the screwholes
* The firmware version it reported did not adhere to the Samsung Firmware number scheme
* Samsung Magician did not recognize it as a Samsung SSD
So I would suggest to also install Samsung Magician from the Samsung website, and have it analyze the SSD. (In addition to running hdparm -I and smartctl --all as fzabkar already suggested)
I think for Samsung Magician it might be also better to use a native SATA interface, without USB.
[ 218.239847] ata5: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
[ 218.239853] ata5: irq_stat 0x00400040, connection status changed
[ 218.239856] ata5: SError: { PHYRdyChg 10B8B DevExch }
[ 218.239863] ata5: hard resetting link
[ 218.962561] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 223.962551] ata5.00: qc timeout (cmd 0xef)
[ 223.962568] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) failed (Emask=0x4 Stat=0x50 Err=0x01)
[ 223.962575] ata5: hard resetting link
[ 229.322554] ata5: link is slow to respond, please be patient (ready=0)
[ 233.970554] ata5: COMRESET failed (errno=-16)
[ 233.970565] ata5: hard resetting link
[ 239.330549] ata5: link is slow to respond, please be patient (ready=0)
[ 243.978545] ata5: COMRESET failed (errno=-16)
[ 243.978555] ata5: hard resetting link
[ 249.338545] ata5: link is slow to respond, please be patient (ready=0)
[ 279.030535] ata5: COMRESET failed (errno=-16)
[ 279.030547] ata5: limiting SATA link speed to 1.5 Gbps
[ 279.030550] ata5: hard resetting link
[ 284.054551] ata5: COMRESET failed (errno=-16)
[ 284.054573] ata5: reset failed, giving up
[ 284.054588] ata5: EH complete
April 25th, 2017, 14:41
April 25th, 2017, 15:16
DR-Kiev wrote:The main goal not clarified. Do you need data or just repair device? In first case it is possible to do, need to run it in tech-mode, connect to terminal (Rx-Tx) and download specific microcode. So far it is possible only with expensive tools like (pc3k ssd edition).
April 25th, 2017, 17:15
April 26th, 2017, 5:23
May 2nd, 2017, 3:40
Adisa wrote:Thanks allot for your time, trying to help me out!
I will consider sending it to DR after all.
Take care!
Powered by phpBB © phpBB Group.