@337harvey, i had a issue 4-5 weeks ago that zorin didnt want to use my second m2 drive to install zorin on. What i did was removing both samsung drives. Booted back in the live and now zorin can be installed on the WD drive
Samsung 980 1tb m.2. nvme
Western Digital blue 1tb m.2. sata
Samsung 870 2tb sata 3
I dont know why because when all drives where attached and selected to manually partition a drive it just saw my second m2 drive. But when i selected install next to windows 10 i only saw both samsung drives and the WD was not listed.
The funny thing is when i installed zorin on the WD drive and reattached samsung everything worked fine. I did a clean install 1 week later, booted live and selected the option install next to windows 10 and now the live session saw the WD drive...i didnt had to remove the samsung drives like before.
Michel, while your gathering info to post so that Mr. Harvey can help you, would you also please update your profile to reflect which version of Zorin OS you are using?
Thanks!
Now in regards to PCIE NVME M.2 drives, they don't connect exactly the same as SATA drives do. M.2's use the PCIE gen 3 and gen 4 lanes on the motherboard, and they are usually configured in RAID.
I am still learning about these new drives myself, but what little I know, I understand like on my notebook for example, they have to be enabeld for RAID for both drives to be seen and used on the same motherboard.
The western digital is also visible because zorin os in installed on it. I try to explain it more detailed today with screenshots. The topic title is not correct either.
@337harvey, here i made a nice video of it today. It happend again but now it did not see my Samsung 980 1TB NVMe m2 and also didn't see the Western Digital 1 1tb m2 SATA m2. The first time it happend (4-5 weeks ago) the Samsung 980 drive was visible as well (Windows 10 drive) the Western Digital (sandisk drive) was EMPTY back then and formatted in NTFS (i used it and made it empty). That was the first time i wanted to install linux and my WD drive was not visible in that part.
Good thing that you posted this video. Unless I am wrong, this looks like a clear bug with the installer software. And if other people come across this, we might be able to start seeing a pattern to confirm it. But for all we know, it may only happen with certain hardware.
I didn't get any errors during setup, only drives missing as shown in the video. Anyway Zorin is installed already 4-5 weeks ago on the WD drive. I manually formatted it with Gparted installed zorin manually only i messed things up (home root whatever i did, im a noob lol) so i did a reinstall back then, this time i could select the wd drive to install besides the windows 10 install (where it first didn't show up).
If i delete irst application ??? as i understand there is no raid table configured. In status it says "create a volume by combining available drives to expand your storage system"
If you intend to install Ubuntu on a computer that supports RST functionality, you may need to make operational adjustments to your setup before you can proceed.
By default, the Ubuntu installer can detect certain RAID configurations, but it may not necessarily be able to access and use the hard disks grouped in them.
If the Ubuntu installer cannot detect the hard disks you need, then before you can install Ubuntu, you will need to turn RST in the computer’s BIOS. The exact terminology and steps required to access and manage RST in BIOS often depend on the specific implementation by the platform vendor. For instance, Dell computers may have different settings from Lenovo or HP computers.
Furthermore, you may already have Windows installed on the computer that uses RST. If you disable RST in the BIOS or change the RST configuration, Windows may become unbootable, as it may no longer be able to find and use the hard disks.
I remember once I was trying to get Windows 7 to boot up from a high capacity hard drive connected to early Sata 1 interface, on an old AMD single core 64-bit machine.
Nothing I did could make it work, until I set the drive up in the bio's for RAID. Once RAID was enabled, even though it wasn't a real RAID having only 1-drive in the system, suddenly, the hard drive could be booted from.
I always assumed this was due to the fact that the Asus A8V Deluxe motherboard bio's were just too ancient to properly detect and boot from the drive unless RAID was engaged, which maybe still indeed the case. Still have that old desktop machine BTW. lol
But it is indeed possible, that weird oddities like that, are still present in modern systems, when in regards to the newest and and greatest NVME SSD drives. Anyways, thought I'd share my experience.
