Device NVME SSD not detected on Linux system
Device NVME SSD not detected on Linux system
Hello! Your Acer Predator Helios 300 had a single NVME M.2 SSD with Windows 10 installed when you bought it. You switched to a SATA SSHD for gaming and other needs, but Linux only worked on the SATA drive. The NVME drive disappeared over time, making dual-booting tricky. Recently, you added another 1 TB NVME SSD for Linux, which initially worked briefly before your BIOS stopped responding. After updating the BIOS, the problem persisted when trying to boot the old Linux setup. It seems the issue might relate to Intel's RST technology. I don’t know how to fix it, but any advice would be greatly appreciated. Cheers!
Start in a running system from an install disc. In the command line, display available block devices with lsblk and show disk information using fdisk -l.
OS: Manjaro Xfce lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 69.7M 1 loop /run/miso/sfs/livefs loop1 7:1 0 363.5M 1 loop /run/miso/sfs/mhwdfs loop2 7:2 0 830.4M 1 loop /run/miso/sfs/desktopfs loop3 7:3 0 584.9M 1 loop /run/miso/sfs/rootfs sda 8:0 0 1.8T 0 disk └─sda1 8:1 0 1.8T 0 part sdb 8:16 1 7.5G 0 disk ├─sdb1 8:17 1 1.9G 0 part /run/miso/bootmnt └─sdb2 8:18 1 4M 0 part fdisk -l Disk /dev/sda: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000LX001-1RG1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 63030B75-F5BC-11E9-B609-806E6F6E6963 Device Start End Sectors Size Type /dev/sda1 32768 3907026943 3906994176 1.8T Microsoft basic data Disk /dev/loop0: 69.67 MiB, 73035776 bytes, 142648 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop1: 363.55 MiB, 381194240 bytes, 744520 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop2: 830.38 MiB, 870703104 bytes, 1700592 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop3: 584.9 MiB, 613285888 bytes, 1197824 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb: 7.5 GiB, 8039432192 bytes, 15702016 sectors Disk model: USB DISK Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 64 3915431 3915368 1.9G 0 Empty /dev/sdb2 3915432 3923623 8192 4M ef EFI (FAT-12/16/32)
Are there any entries in the Bios that reference Raid? If yes, turn it off or set it to AHCI. Also, ensure Secure boot is turned off as it sometimes leads to problems. If that doesn't resolve the issue or isn't working, consider switching from UEFI Boot to Legacy Boot. You might need to disable certain features to allow passage.
But does Linux display the drive when configured for AHCI? Yes, it usually points to the RAID controller. This might disrupt your existing Windows setup because array structures are altered. If it appears in Linux after you adjust settings, you could save important files from your current Windows installation, revert to AHCI, and reinstall Windows.
I resolved the problem! 1. Turn on Safe Boot (basic) in Windows 10
2. Activate AHCI in BIOS settings
3. Turn off Safe Boot and restart.
Thanks a lot for your assistance!