So one of my older Samsung 860 EVO 1TB SSD drive just failed, and I don’t know how “It’s dead Jim” it is. Fortunately I have backups and the data is not that critical.
lsblk: drive is listed but there is no partition or mountpoint
blkid: drive /dev/sda is not listed
If the data is not needed, Last (as in absolute last) resort might be trying hdparm and try an ata-secure erase?
I got the impression you would like to poke around, see if there is anything you an do, but I got nothing. Could try to update he firmware maybe? That might wipe it also, but maybe get the controller responding again?
Yeah I’m willing to poke a little, but I don’t trust my knowledge on storage to use this drive after.
Will research and try what you suggest @Trooper_ish.
If the controller is dead, than so be it. First Samsung drive to die on me ever, and second SSD in general after some old 64GB OCZ which happened ages ago.
If you haven’t tried reseating, swapping cables, or changing ports, that would be the first thing to do. Ports and cables can fail too, if only because it’s “free”.
Or possibly try reflashing the firmware. Have you opened up the case to look for toasted components?
For my own curiosity, what’s the firmware version? Is it declaring “ERRORMOD” or only showing something with ~1GB of space?
It could be a hardware failure, or it could be because Samsung has awful firmware quality (see the “Bugs” section in this for the old 840 evo, before they started really trying to encrypt it.)
I’ve stopped suggesting picking up their misc enterprise nvme drives off eBay because despite the flash chips having plenty of life in them, the firmware is still prone to corruption and issues. And I unlike their consumer drive division, the enterprise side deliberately doesn’t make updates available, and coupled with per OEM/model compatibility issues there is generally no possibility for reflashing back to a good state.