I have an Asrock Z97 Extreme9 motherboard which I updated to the latest firmware (2.10). I’ve installed a Samsung 970 Evo Plus NVMe SSD. When I try to install Leap 15.3 it does not detect the SSD and only lists the hard disk drives. My current installation is Leap 15.2 on Intel RST RAID 1. I thought the situation described here https://www.suse.com/support/kb/doc/?id=000019441 may apply so I changed the BIOS setting for SATA3 mode from RAID to AHCI. It still does not detect the SSD during installation. The BIOS setup shows the SSD under NVMe configuration and in the list of boot devices. However, it does say under storage configuration that M2_1 is not detected and that’s where the SSD is plugged in.
I don’t think you went far enough given the clues in that article. Does the installer find the NVME if you disconnect all SATA drive cables from the motherboard? If yes, then likely you only need to move at least one of the cables to other ports. There are usually one or two SATA ports that cannot be used at the same time as some devices in at least one of two M.2 ports, or an only M.2 port.
If you boot 15.2, is the NVME detected by it?
Thank you mrmazda. I will try your suggestions as soon as I can. The motherboard manual states that M2_2 is shared with SATAE_1, SATA3_4 and SATA3_5. I don’t see any mention of M2_1 being shared with anything other than using four PCIe lanes. The SSD is PCIe Gen 3x4. So it uses four PCIe lanes, but no SATA channels. All the PCI expansion slots are empty. I don’t know what this SSD has to do with SATA or AHCI/RAID. I did read somewhere that Intel SATA controllers have some weird mode where PCI is remapped in some way that prevents access to NVMe devices.
To determine whether the problem is more or less likely a YaST than a kernel issue, start the installer. When you reach the license screen, key in Ctrl-Alt-F2 and run lsmod | grep nvme. If you get any non-null result, the problem is probably in YaST. When I boot NVME, I get a two line result from that command. If you get no result, run modprobe nvme, then run lsmod | grep nvme again. If you get a result this time, Alt-F1 or Alt-F7 to return to YaST to try proceeding with installation.
When I boot into Leap 15.2, gnome-disk-utility shows 500GB disk present as /dev/nvme0n1. This is with Intel RST RAID enabled as well. When I try to install Leap 15.3, and do Ctrl-Alt-F2, lsmod | grep nvme I get:
tty2:install:/ # lsmod | grep nvme
nvme 49152 0
nvme_core 135168 1 nvme
t10_pi 16384 2 sd_mod,nvme_core
tty2:install:/ #
I don’t see any way to install on the SSD when I get to the partitioning screen. It’s not listed anywhere (not in guided setup, expert partitioner: start with existing partitions nor start with current proposal). Looks like more of an installation issue than hardware issue. What now?
Thank you mrmazda.
Report a YaST/installation bug:
https://en.opensuse.org/openSUSE:Report_a_YaST_bug
https://en.opensuse.org/openSUSE:Submitting_bug_reports
https://en.opensuse.org/openSUSE:Bug_reporting_FAQ
I’m running into the same issue while trying to install MicroOS Desktop/Aeon and Tumbleweed, but not Leap. I wanted MicroOS Desktop/Aeon but YaST only recognizes my NVME drive while installing Leap. I have booted the tumbleweed live USB and I can see the drive in gparted but not in YaST. I can see it under ls /dev, lsblk, but not blkid. This happens when I drop into a tty while using the installer ISO and the live USB ISO.
Has anyone figured out anything regarding this issue?
Please, this is more then a year old. You probably have a different LEAP version (although you do not mention is). When you want to draw the attention of people to help you, better start a new thread with a good title then hang on at the end of an old thread that many people will not watch anymore.
Thanks for the direction. This was was my first post and I thought it was related in some way. I will make a new request with more info and a relevant title.