If that is the case, it would be better to recommend another distr which comes with the latest kernel.
Thanks to the openness of this forum we have no hesitation to talk about other Linux distros here 
Sometime I feel like I am sending more people to MX, my husband's distro of choice 
I'm writing from windows, then nothing, nvme disks cannot be disabled, on the contrary, sata can be disabled. I would have to physically remove them, which I don't feel like doing, even if the motherboard is mounted on a test stand, I'm a geek. Having said that, I have prepared a key with Mx I did the boot, it is the latest version 19 ... dedicated to amd, but not to the amd raid in fact not even this one sees the raid disks, among other things you can not change even the language is useless to add another OS at boot, in my opinion they are the same, but I have to recognize one thing, I first installed the "core" version with which the printer worked, I also did the print test, with the "pro" see the printer online but does not print ... mysteries of technology.
I checked at distrowatch.com
Even the latest beta version, they are using 5.10.46 kernel.
I think if you want to try the bleeding edge kernel, you need something like
Fedora rawhide (5.15.0)
OpenSuse tumbleweed (5.14.2)
Manjaro 21.1.3 (5.13.15)
Ubuntu snapshot impish (5.13.0)
Yes, this is a good suggestion.
A higher kernel may help, but certainly is no guarantee. What may make the difference between OS's is not the kernel, but the installer. Zorin OS uses the Ubuntu Ubiquity Installer. MX uses its own installer.
As does Fedora.
1 Like
Ah, 3rd thing I've learnt today. I did not know that.
Fedora rawhide (5.15.0)
OpenSuse tumbleweed (5.14.2)
Ubuntu snapshot impish (5.13.0)
Actually when I looked at the names of those distro versions, they look a bit threatening.
Not that i am aware of. I have 3 different storage drives installed. From what i know (or think) raid only works with identical drives.
I used to run RAID 1 (mirroring) on my NAS and what I know is that I could mix HDDs with different capacities but the smaller disk would be the limiting factor.
That is 2GB+2GB gives the same capacity as 2GB+4GB.
1 Like
IRST is intel's solution for quicker access which creates a fake raid pointing to storage locations to improve access speed. It treats individual directories as raid partitions without duplication, as i understand it. Those raid tables are what is causing the issue in both systems, i guess because they weren't created in the os. If a fix is implemented in Ubuntu it will be passed to zorin by inherentance, but until then the only solution/work around offered has been to delete the irst table. I'm guessing that adding the uuid of the raid array to fstab will provide access and recognition, seems logical, but i have no way to test this. I'm hopeful it will provide recognition of the disks, and this may also work for Michel, but until someone can confirm initial recognition and no loss over time i couldn't call it a solution.
2 Likes
Holy molly guacamole, thats a lot of chat since I last was here. So, as I understand it, there is still no solution after all this time? Especially since one of the last comments refers to suggestion of a different distro?
Dear oh dear, how far we have fallen. Linux kernel, what are you doing to us! Ugg 
1 Like
The possibility of a solution has been presented, it just needs tested to see if it's viable.
1 Like
Maybe this is significant. Was there a a kernel update between ezzy using Core and him installing Pro. What other reason if all was well in Core but not in Pro. Makes you think.
I could do it but I don't know how to do it, the uuid I don't know what it is, I think an identifying id, there will certainly be in the bios, but I wouldn't know how to create the support in "fstab", I don't know how to program, oh my if I have the exact instructions I can do it.
https://www.codeproject.com/Tips/5263343/How-to-Get-the-BIOS-UUID
UUID is Universally Unique IDentifier.
1 Like
I have read everything I have also downloaded the zip file but I do not know how to write or which shell to use, at least I know some cmd ms-dos line, for the rest nothing, I am hardware not software, you give me a software and I I test it on a system, but I'm not a programmer, I can learn, but ...
We are the same in this regard 
2 Likes
ahahah! wonderful! 
The commands to get the uuid in this walkthrough doesn't help you because Zorin doesn't see it. You may try that portion at a grub prompt prior to boot to see the bios's list of hardware. Once you write down the uuid, the rest is simple in adding it to fstab.
3 Likes
Or taking a photo with a mobile phone.
UUID is very looong to copy by hand.
1 Like
@FrenchPress Good idea. It avoids human error. At least in the capture phase. I now use my mobile to capture serial numbers, part numbers, meter readings, etc etc instead of writing them down.
(Do not reply to this post as I fear it will trigger a "deviation from subject" klaxon)
3 Likes
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.