Hello, this is my first time installing Qubes OS and I own an Alienware Aurora and It has
m.2 nvme 500gb SSD (Win 11 OS)
2TB HDD
1TB 2.5 SSD
1TB 2.5 SSD
m.2 nvme connected to motherboard via M.2 NVME to PCIe 3.0 x4 Adapter.
So, after manually installing the 5th m.2 nvme via the adapter, I installed the disk and created a new simple volume as NTFS/GUI disk.
I followed the procedure to create a qubes OS installation flash drive and disabled the secure boot and booted using the qubesOS flash drive and did the test this media and install OS option and in the install destination I could see the disk number 2), 3) & 4) but not 1) & 5). I’m planning to install qubesOS in 5).
Do you guys know why 5) is it not showing up & how to successfully install it ?
Qubes uses the Fedora installer.
There was a long standing issue with fedora not recognising NVME drives.
You could check this using a live Fedora iso, and then selecting
“install to disk”. Try it.
You do not say which version of Qubes you are trying to install - 4.0 is
based off Fedora 25, which will (may?) not work. 4.1 is based off much
more recent base system.
You could try checking the boot mode - if it is set to RAID, change that
to “AHCI” - this has been reported to work with Fedora 32. I do not know
if this will affect any other OS you have installed on those other
drives.
If you are dual booting please read the documentation so you are aware
of any risks and pit falls in advance.
I’ll try the fedora live iso today and see if the nvme shows up,
I’m using Qubes release 4.1.0-rc3
how do I change the boot mode to RAID or AHCI ? all I see in Alienware BIOS is option to change to UEFI or Legacy boot, and if I’m installing Qubes in a separate internal SSD ( 512gb m.2 nvme connected to motherboard via M.2 NVME to PCIe 3.0 x4 Adapter.) will it affect my win 11 OS installed in a separate m.2 nvme SSD ?
Hello, this is my first time installing Qubes OS 4.1.0-rc3 and I own an Alienware Aurora and It has
m.2 nvme 500gb SSD (Win 11 OS)
2TB HDD
1TB 2.5 SSD
1TB 2.5 SSD
m.2 nvme connected to motherboard via M.2 NVME to PCIe 3.0 x4 Adapter.
So, after manually installing the 5th m.2 nvme via the adapter, I installed the disk and created a new simple volume as NTFS/GUI disk.
I followed the procedure to create a qubes OS installation flash drive and disabled the secure boot and booted using the qubesOS flash drive and did the test this media and install OS option and in the install destination I could see the disk number 2), 3) & 4) but not 1) & 5). I’m planning to install qubesOS in 5).
Do you guys know why 5) is it not showing up & how to successfully install it ?
@ludovic@51lieal This is what I get when I ran lsblk in qubes os 4.1.0 rc3 and I don’t see my primary m.2 nvme where win 11 is installed or the other nvme where I intend to install Qubes OS.
Sorry to pile on here, @ppc, but I think the OP’s case though may not be quite so simple (usually it’s the case of existing SATA being disabled in order for the obviously populated M2 to be used rather than the reverse - of course there could be boards with the opposite choice made by the engineers) - but it has to be considered so @Mephisto maybe you can look into it or pass along more details for us to chew over. The issue that I think @ppc maybe brings up (looking back now I’m already doubting my interpretation of their slant & it could be completely different so sorry) is a matter of design limitations & barely documented features of modern systems - namely the optional features (expansion slots, expansion headers, etc.) that auto-kill other optional features since both are not capable of being used due to scarce resources (board has two jacks but chipset/CPU can only accommodate so much use & BIOS auto turns off one if the other is populated situation - right @alzer89).
Addendum: to wit, I also recall times when certain card slots (PCI/ISA but PCIe?) would be enabled or disabled based upon a similar device - engineering choices with limited resources).
Still the SSD is not showing up.
