SSD No longer recognized - 0 bytes

[t13]

Running Manjaro, My Samsung 840 pro SSD seems unrecognized by BIOS or Ubuntu live USB on different machine

It was working fine prior to changing/ppdating Nvidea drivers - this caused grub to break but BIOS still recognized a drive during boot.

Plugging the SSD into a USB to SATA in a Live Ubuntu USB env

sudo dmesg
usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
usb 2-1: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
usb 2-1: Product: ASM1351
usb 2-1: Manufacturer: SABRENT
scsi host1: uas
scsi 1:0:0:0: Direct-Access SABRENT ASM1351 0 PQ: 0 ANSI: 6
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] Spinning up disk...
..................................................................................................not responding...
sd 1:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] Sense Key : Not Ready [current]
sd 1:0:0:0: [sdb] Add. Sense: Logical unit is in process of becoming ready
sd 1:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] Sense Key : Not Ready [current]
sd 1:0:0:0: [sdb] Add. Sense: Logical unit is in process of becoming ready
sd 1:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
sd 1:0:0:0: [sdb] 0-byte physical blocks
sd 1:0:0:0: [sdb] Test WP failed, assume Write Enabled
sd 1:0:0:0: [sdb] Asking for cache data failed
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] Preferred minimum I/O size 512 bytes not a multiple of physical block size (0 bytes)
sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
sd 1:0:0:0: [sdb] Attached SCSI disk


sudo fdisk -l
/dev/sdb 0 bytes


Any suggestions where to go from here, I hope all data is not lost.

 

[AlphaObeisance]

Sounds to me like the NVMe is in a frozen/protective state; possibly due to the change of power state?

You can try hdparm for more details.

sudo pacman -S hdparm
sudo hdparm -I /dev/sdb

 

[APTI]

If BIOS does not see the drive then no OS will either. 9 out of 10 times this is a shot drive. You may have to get a new one. But sometimes utilities from the manufacturer can rescue the drive but don't hold your breath.

 

[t13]

Thanks for the reply @AlphaObeisance

I will test out your commands and write back

For the mean time, I found this post which looks to exactly describe my problem, It also matches the SSD Model precisely

Samsung SSD 840 Pro - Microcode failure - Cheadle DATA Recovery Ltd

Case study showing recovery of a failed Samsung SSD 840 Pro. Failure of the microcode / firmware is common in this series. Use of PC3000 is required.

www.cheadledatarecovery.co.uk

Thanks @APTI Hopefully a utility or solution exists, I don't think just because the BIOS doesn't recognize it implies immediate death of the SSD... quite a negative way to think

 

[APTI]

Thanks for the reply @AlphaObeisance

I will test out your commands and write back

For the mean time, I found this post which looks to exactly describe my problem, It also matches the SSD Model precisely

Samsung SSD 840 Pro - Microcode failure - Cheadle DATA Recovery Ltd

Case study showing recovery of a failed Samsung SSD 840 Pro. Failure of the microcode / firmware is common in this series. Use of PC3000 is required.

www.cheadledatarecovery.co.uk

Thanks @APTI Hopefully a utility or solution exists, I don't think just because the BIOS doesn't recognize it implies immediate death of the SSD... quite a negative way to think

not a negative way to think, It is just factual and realistic. It is unrealistic to think you can bypass a problem like that.
What I said was that 9 out of 10 times it means just that. that leaves a 10% chance you might succeed. but that is what it is. 1 out of 10. So realistically you should expect to replace the drive and be thrilled and happy if you don't have to. I do this for a professional living. so my expectations come from actual real world use.
Going forward...

1. see if samsung can give you a utility to fix it but do not be surprised if it does not.
2. If the drive is not showing in BIOS it will not be found by any OS.
3. If it is not found in BIOS then you must replace it.
4. If you must replace it, go to samsung and see if it is under warranty, if it is create an RMA and get it replaced by them. If you use this option be prepared for a convoluted return process that may take several weeks before you have a replacement in hand. Often samsung will not replace it but just offer you market value replacement cost of the drive back. Forcing you to purchase again.

Good luck and let me know how it goes.

 

[AlphaObeisance]

Thanks for the reply @AlphaObeisance

I will test out your commands and write back

For the mean time, I found this post which looks to exactly describe my problem, It also matches the SSD Model precisely

Samsung SSD 840 Pro - Microcode failure - Cheadle DATA Recovery Ltd

Case study showing recovery of a failed Samsung SSD 840 Pro. Failure of the microcode / firmware is common in this series. Use of PC3000 is required.

www.cheadledatarecovery.co.uk

Thanks @APTI Hopefully a utility or solution exists, I don't think just because the BIOS doesn't recognize it implies immediate death of the SSD... quite a negative way to think

APTI is in fact, not wrong. My advise was based solely on a personal experience some time ago where my drive oddly refused to be recognized in the bios.

While I too would instinctively plan on replacing the drive; I'm also resourceful enough to exhaust all options before reaching for the wallet. Call me cheap, or stubborn; either works.

I'm still using the drive today, and it's in fact, quite healthy. That is not to say you would be so lucky, but that sometimes it is in fact easier to just cut your losses so to speak; than it is to try and exhaust your options.

The NVMe that powers my Hypervisors OS didn't show up intel BIOS of my power edge either; but I'm still using it 2 years later as well.

Maybe we'll just call me an optimist.

 

[t13]

not a negative way to think, It is just factual and realistic. It is unrealistic to think you can bypass a problem like that.
What I said was that 9 out of 10 times it means just that. that leaves a 10% chance you might succeed. but that is what it is. 1 out of 10. So realistically you should expect to replace the drive and be thrilled and happy if you don't have to. I do this for a professional living. so my expectations come from actual real world use.
Going forward...

1. see if samsung can give you a utility to fix it but do not be surprised if it does not.
2. If the drive is not showing in BIOS it will not be found by any OS.
3. If it is not found in BIOS then you must replace it.
4. If you must replace it, go to samsung and see if it is under warranty, if it is create an RMA and get it replaced by them. If you use this option be prepared for a convoluted return process that may take several weeks before you have a replacement in hand. Often samsung will not replace it but just offer you market value replacement cost of the drive back. Forcing you to purchase again.

Good luck and let me know how it goes.

It isnt factual at all, Your figures of 9/10 ie 90% are not accurate or factual, and cannot be.
The actual FACT is that all brands and models would have different repair/recovery rates, its not a simple 9/10 SSD are deemed dead at this point.

Some brands of SSD would have 100% dead rate, some 20%, etc.

I dont believe 9/10 Samsung 840 pro SSD are "shot" drives at this stage, your figures not mine.

Your figures are unrealistic and thats why I choose to be positive.

I have a AmScope, Hot Air rework Station, soldering iron, and £5k to throw at this to get my data back...
If it means buying the same samsung SSD model and swapping/resoldering the chips over, thats a positive approach I would be willing to try.

Moving on.

@AlphaObeisance

I have changed live iso USB to systemrescue as it has more progs readily suited.

running sudo hdparm -I /dev/sda

This hangs for around 6 seconds and just prints
/dev/sdb:

running sudo smartctl -a /dev/sda

Read Device Identity failed: scsi error device will be ready soon

If this is a USB connected device, look at the various --device=TYPE variants...

 

[APTI]

APTI is in fact, not wrong. My advise was based solely on a personal experience some time ago where my drive oddly refused to be recognized in the bios.

While I too would instinctively plan on replacing the drive; I'm also resourceful enough to exhaust all options before reaching for the wallet. Call me cheap, or stubborn; either works.

I'm still using the drive today, and it's in fact, quite healthy. That is not to say you would be so lucky, but that sometimes it is in fact easier to just cut your losses so to speak; than it is to try and exhaust your options.

The NVMe that powers my Hypervisors OS didn't show up intel BIOS of my power edge either; but I'm still using it 2 years later as well.

Maybe we'll just call me an optimist.

I completely agree to exhaust options before buying a new drive. They are expensive right now thanks to all the datacenters buying it all up and increasing demand and so on, but suffice it to say they are expensive and I do not replace blindly without trying the options for that 10% chance of resurrecting the drive.
So please do you the utilities and try. but be prepared to replace it.

I have my fingers crossed for not replacing it.

 

[MikeRocor]

I have my fingers crossed for not replacing it.

I usually find it sufficient to just cross my eyes - which isn't hard, most of the time, when dealing with tech.