On Saturday, 2 September 2017 13:28:44 BST Jacques Montier wrote:
> I once encountered the problem with my Crucial SSD.
> I found a procedure to make the SSD detected which worked for me.
> http://forums.crucial.com/t5/Crucial-SSDs/Why-did-my-SSD-quot-disappear-qu
> ot-from-my-system/ta-p/65215 Hope this will help.
Mine's by Samsung:
# lspci -v -s 05:00.0
05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD
Controller SM951/PM951 (rev 01) (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM951/
PM951
Flags: bus master, fast devsel, latency 0, IRQ 35, NUMA node 0
Memory at fbd00000 (64-bit, non-prefetchable) [size=16K]
I/O ports at d000 [size=256]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable+ Count=9 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [158] Power Budgeting <?>
Capabilities: [168] #19
Capabilities: [188] Latency Tolerance Reporting
Capabilities: [190] L1 PM Substates
Kernel driver in use: nvme
It's clearly visible to the kernel, and smartd finds it too if I tell it
what to look for.
I don't want to start unplugging it unless I have to, as it's in a PCI slot
and I'd probably make things worse. And it is only 18 months old, as I said.
A week or two ago I was investigating some other weirdnesses and at one
point I zeroed out the first partition: the unformatted one containing the
UEFI data. It took longer than I expected, having only 2MB to fill. I wonder
if it strayed outside the partition...
--
Regards,
Peter.
