Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

NVMe not detected by Debian on Asus UX430 only

Need help with peripherals or devices?
Post Reply
Message
Author
dave
Posts: 2
Joined: 2019-11-17 15:18

NVMe not detected by Debian on Asus UX430 only

#1 Post by dave »

I've just bought a new Asus UX430UA laptop. I'm trying to do two things: replace the SATA SSD with a larger ADATA XPG SX8200 NVMe SSD, and install Debian 10 on it to dual-boot with the OEM version of Windows 10. Debian doesn't see the NVMe drive, even though the drive is working on this machine. It's driving me nuts, and I'd appreciate any help anyone can offer.
  • Debian 10.2 Live and Debian 10.1 netinst on USB: neither recognizes the drive. lsblk shows only the usb stick (/dev/sda) and loop0, and there are is no /dev/nvme*
  • I cloned Windows 10 from the OEM SSD to the new one on my Debian 9 desktop, it went flawlessly, meaning that Deb. 9 recognized the NVMe ssd on another system.
  • The laptop boots fine into Windows 10 on the NVMe SSD. Also, the UEFI sees the NVMe drive.
  • I checked a few things that I've read about here and elsewhere:
  • There is no option in UEFI for anything like Intel RST
  • The SATA configuration in UEFI is set to AHCI, which is the only option. There is no RAID option.
  • Fast boot and Secure Boot are disabled.
  • Compatibility Support Mode (CSM) is Disabled in UEFI, though I've also tried with it enabled and no effect.
  • UEFI is the latest version according to the Asus website. ADATA doesn't have any downloadable firmware for the SSD on their website.
In case it's helpful, this is from Debian Live 10.2, kernel 4.19.0-6-amd64:

Code: Select all

sudo dmesg | grep -i nvme

[    1.441062] nvme nvme0: pci function 0000:03:00.0
[    1.665679] nvme nvme0: missing or invalid SUBNQN field.
[    1.668135]  nvme0n1: p1 p2 p3 p4 p5
[   36.017364] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
[   36.049640] print_req_error: I/O error, dev nvme0n1, sector 1000215040
[   36.097358] nvme 0000:03:00.0: Refused to change power state, currently in D3
[   36.097634] nvme nvme0: Removing after probe failure status: -19
[   36.113518] Buffer I/O error on dev nvme0n1, logical block 125026880, async page read
[   36.115717] Buffer I/O error on dev nvme0n1p4, logical block 204784, async page read
[   36.115826] Buffer I/O error on dev nvme0n1p5, logical block 20479984, async page read
[   36.117946] Buffer I/O error on dev nvme0n1p1, logical block 66544, async page read
[   36.197378] nvme nvme0: failed to set APST feature (-19)
That suggests maybe a hardware problem, but as I mentioned, it works on my Debian 9 system, and UEFI and Windows 10 work with this SSD on this same system, so it can't be hardware.

EDIT: I was poking around in /dev and I found this, which suggests that the drive IS visible to Debian. It still doesn't show up in lsblk or as a /dev/nmve* file though.

Code: Select all

user@debian:~$ ls -l /dev/disk/by-uuid
lrwxrwxrwx 1 root root 10 Nov 17 08:14 2019-11-16-10-37-14-00 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 17 08:14 DEB0-0001 -> ../../sda2

user@debian:~$ ls -l /dev/disk/by-path
lrwxrwxrwx 1 root root  9 Nov 17 08:14 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 17 08:14 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 17 08:14 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 13 Nov 17 08:14 pci-0000:03:00.0-nvme-1 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Nov 17 08:14 pci-0000:03:00.0-nvme-1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Nov 17 08:14 pci-0000:03:00.0-nvme-1-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Nov 17 08:14 pci-0000:03:00.0-nvme-1-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Nov 17 08:14 pci-0000:03:00.0-nvme-1-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 Nov 17 08:14 pci-0000:03:00.0-nvme-1-part5 -> ../../nvme0n1p5

user@debian:~$ ls -l /dev/disk/by-id
lrwxrwxrwx 1 root root 13 Nov 17 08:14 nvme-ADATA_SX8200PNP_2J3720012352 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-ADATA_SX8200PNP_2J3720012352-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-ADATA_SX8200PNP_2J3720012352-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-ADATA_SX8200PNP_2J3720012352-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-ADATA_SX8200PNP_2J3720012352-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-ADATA_SX8200PNP_2J3720012352-part5 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 13 Nov 17 08:14 nvme-nvme.1cc1-324a33373230303132333532-414441544120535838323030504e50-00000001 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-nvme.1cc1-324a33373230303132333532-414441544120535838323030504e50-00000001-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-nvme.1cc1-324a33373230303132333532-414441544120535838323030504e50-00000001-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-nvme.1cc1-324a33373230303132333532-414441544120535838323030504e50-00000001-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-nvme.1cc1-324a33373230303132333532-414441544120535838323030504e50-00000001-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 Nov 17 08:14 nvme-nvme.1cc1-324a33373230303132333532-414441544120535838323030504e50-00000001-part5 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root  9 Nov 17 08:14 usb-Lexar_USB_Flash_Drive_7DA9899FCA546300822A-0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 17 08:14 usb-Lexar_USB_Flash_Drive_7DA9899FCA546300822A-0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 17 08:14 usb-Lexar_USB_Flash_Drive_7DA9899FCA546300822A-0:0-part2 -> ../../sda2
Those links to nvme0n1p* correctly show the number of partitions currently on the drive. But the links are broken, there is no /dev/nvme*!!!!

Any suggestions would be appreciated!

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: NVMe not detected by Debian on Asus UX430 only

#2 Post by Head_on_a_Stick »

deadbang

dave
Posts: 2
Joined: 2019-11-17 15:18

Re: NVMe not detected by Debian on Asus UX430 only

#3 Post by dave »

Thanks, that workaround got me up and running!

I guess it will be poorer power management, as I understand that disables power management on the SSD. (?)

Post Reply