Yesterday's Windows 10 update resulted in a Blue Screen of Death. Since then, my NVMe disk is no longer operational. I wonder if anybody has a suggestion how to approach a data recovery.
Mainboard: Gigabyte Aorus Elite Ax V2. NVMe disk: Gigabyte GP-ASM2NE6100TTTD (1TB M.2 drive). Purchased 4 years ago. Last SMART check 7 weeks ago revealed no warning, 14.2 TB read / 7.07 TB written, 100% available spare and 10258 hours on power.
Should I have been alerted by:
Error Information (NVMe Log 0x01, 16 of 63 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 2619 0 0xd00b 0x4004 0x004 0 1 - Invalid Field in Command
1 2618 0 0x200a 0x4004 0x004 0 1 - Invalid Field in Command
2 2617 0 0x5010 0x4004 0x004 0 1 - Invalid Field in Command
3 2616 0 0x0018 0x4004 0x028 0 0 - Invalid Field in Command
Or is that acceptable?
BIOS stated that there is no NVMe drive so I removed it, put it into an external USB M.2 case and tried it with my Lenovo Thinkpad X220 running Ubuntu.
When inserting, journalctl -f showed:
kernel: usb 3-1: new high-speed USB device number 3 using xhci_hcd
kernel: usb 3-1: New USB device found, idVendor=152d, idProduct=0562, bcdDevice= 2.08
kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 3-1: Product: External
kernel: usb 3-1: Manufacturer: JMicron
kernel: usb 3-1: SerialNumber: DD56419883E43
kernel: scsi host6: uas
kernel: scsi 6:0:0:0: Direct-Access JMicron Tech 0208 PQ: 0 ANSI: 6
mtp-probe[2829]: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb3/3-1"
kernel: sd 6:0:0:0: Attached scsi generic sg1 type 0
mtp-probe[2829]: bus: 3, device: 3 was not an MTP device
mtp-probe[2830]: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb3/3-1"
mtp-probe[2830]: bus: 3, device: 3 was not an MTP device
kernel: sd 6:0:0:0: [sdb] Spinning up disk...
kernel: .not responding...
kernel: sd 6:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
kernel: sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]
kernel: sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81
kernel: sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
kernel: sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]
kernel: sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81
kernel: sd 6:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
kernel: sd 6:0:0:0: [sdb] 0-byte physical blocks
kernel: sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
kernel: sd 6:0:0:0: [sdb] Asking for cache data failed
kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
kernel: sd 6:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
kernel: sd 6:0:0:0: [sdb] Unit Not Ready
kernel: sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]
kernel: sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81
kernel: sd 6:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
kernel: sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]
kernel: sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81
kernel: sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
kernel: sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]
kernel: sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81
kernel: sd 6:0:0:0: [sdb] Attached SCSI disk
fdisk -l /dev/sdb fails to open /dev/sdb. lsblk does not show the device. lsusb reports:
ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
But no drive attached.
Is there anything left to do?
