NVME SSD not recognized in Linux

[dunila28]

Hello!

 

I have an Acer Predator Helios 300 (Model name: Predator PH315-52). When I purchased the machine it had a single NVME M.2 SSD (256 GB) in it which had windows 10 installed on it. I quickly bought a SATA SSHD (2 TB) for my Steam Games etc. That was about a year ago, and even then I was messing around with dual-booting windows 10 with Linux. However I could only install Linux on my SATA drive and the NVME drive wouldn't even show up. Back then I was quite happy about this because it meant that I couldn't accidentally delete Windows while messing around.

 

But it was slow so I recently bought another NVME SSD (1 TB) that I wanted to dedicate to Linux (So now I had 3 drives installed). I installed Linux on it and it worked for about a week but then I realized my BIOS was no longer accessible meaning that when I went to smash F2 on startup I would just get a black screen and a DOS like cursor that wasn't even blinking in the top left corner of my screen (the F12 Boot menu was still working), I updated my BIOS (with official software from Acers website) which resolved this issue.

 

After that I tried booting my old Linux install and nothing happened so I tried to reinstall it but now my secondary SSD is also completely gone (Only from the secondary OS, Windows and my BIOS sees it just fine and I can write to it in windows as well). From what I have gathered on the Internet this issue has something to do with Intel's RST (Rapid Storage Technology) however I have no Idea how to circumvent this issue. 

 

Any help appreciated, Cheers!

[Nayr438]

Boot into a live Environment from a Linux Install Media.

In a terminal what does lsblk and fdisk -l output.

[dunila28]

3 minutes ago, Nayr438 said:

Boot into a live Environment from a Linux Install Media.

In a terminal what does lsblk and fdisk -l output.

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)

 

[Nayr438]

Do you have anything that mentions Raid in the Bios? If so Disable it or set it to AHCI. Also make sure Secure boot is disabled, it causes other issues sometimes.

If you don't or changing it doesn't work try switching from UEFI Boot to Legacy Boot. Should disable some features that might allow it to pass through.

 

 

[dunila28]

Just now, Nayr438 said:

Do you have anything that mentions Raid in the Bios? If so Disable it or set it to AHCI. Also make sure Secure boot is disabled, it causes other issues sometimes.

If you don't or changing it doesn't work try switching from UEFI Boot to Legacy Boot. Should disable some features that might allow it to pass through.

 

 

Thanks for the info. Unfortunately I can't change it to AHCI because windows crashes and I get a bluescreen. Secure boot is disabled and I am pretty sure That I am locked in UEFI mode since the option is greyed out and I cannot find any settings to enable it.

[Nayr438]

24 minutes ago, dunila28 said:

Thanks for the info. Unfortunately I can't change it to AHCI because windows crashes and I get a bluescreen. Secure boot is disabled and I am pretty sure That I am locked in UEFI mode since the option is greyed out and I cannot find any settings to enable it.

But does Linux show the drive when it is set to AHCI? If so its the raid controller.

It will probably break your current windows install as you break the array.

 

If it does show up under Linux after changing it. You could backup anything in your current Windows Install, switch it to AHCI and reinstall Windows.

[dunila28]

3 minutes ago, Nayr438 said:

But does Linux show the drive when it is set to AHCI? If so its the raid controller.

It will probably break your current windows install as you break the array.

 

If it does show up under Linux after changing it. You could backup anything in your current Windows Install, switch it to AHCI and reinstall Windows.

Alright will try this tomorrow thanks a bunch!!

[dunila28]

I have solved the issue!

 

1. Enable Safe Boot(minimal) in Win10

2. Enable AHCI in BIOS.

3. Disable Safe Boot and restart.

 

Thank you so much for your help!