#Otherwise healthy NVME drive not working in Mint.

6 messages · Page 1 of 1 (latest)

tame compass
#

I have a 1TB XPG nvme drive that up until recently was running my Windows install with no issues. This device, if it appears in Mint's disk manager at all, cannot be mounted when it does, complaining that it can't read the superblock. Windows can access and read/write this device just fine, and when I took it out of the computer and put it into a USB enclosure, Mint had no trouble either and reported no issues.

I tried to mount it manually and found this error in dmesg:

               nvme0n1: rw=4096, sector=2, nr_sectors = 2 limit=0
[ 1268.176714] EXT4-fs (nvme0n1): unable to read superblock

Investigating further in dmesg I found this:

[   74.337602] nvme nvme0: Does your device have a faulty power saving mode enabled?
[   74.337603] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
[   74.364595] nvme 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
[   74.364708] nvme nvme0: Disabling device after reset failure: -19
[   74.384715] nvme nvme0: Identify namespace failed (-5)

Any ideas or help interpreting these messages would be appreciated. I'm still fairly new to the ecosystem.

Attached is a screenshot of lsblk and the disk manager, in case that helps.

feral moon
#

click in nvme p1 in Disks app. lsblk shows its size. click the gear icon then repair

#

probably windows fast startup on. disable

tame compass
#

p1 wasn't accessible, but I did a reboot to check fast startup (it was off). After the reboot p1 was visible in the manager again, but this was the result of attempting a repair:

feral moon
#

i/o error hm

#

shutdown. use diferent port, also run chkdsk from windpws on it