I want to install Zorin to a RAID Drive which is currently set up in BIOS as RAID. I know I have to change that to AHCI, but I need to know if there is anything I need to add or download/install during the live session to ensure Zorin recognizes the drives as an Array/single drive.
Also, this is going to be a clean insall with just Zorin - no dual booting.
Welcome to the Forum!
Maybe this Video could help You:
The used mdadm Program, You can install with the Command sudo apt install mdadm
If you're using hardware raid like you're talking about and setting it up in your bios, however you set it up there should just show up that way in the installer (I've done this a few times, and that's generally how it goes). Unless you're wanting to use a Software raid setup which you could use something like @Ponce-De-Leon is showing above.
The video is being done either in a VM or an already installed linux system on Rasperry Pi. Does this work the same from the live usb?
It should be makeable in the Live Mode. But the Question is, if it stays when You install it. So, it isn't an Option to install Zorin and make that after the Installation?
I solved the problem - kind of. I installed a VM. I can't lose my RAID. It took a lot of work doing it the "easy" way through the BIOS and I just don't have the time to figure out the Linux way, and I don't understand why open source has to be such a narrow minded religion that it can't get along with at least some of these other things that are proprietary. We pay for that proprietary BIOS whether we use all the features or not.
Here is a link to a helpful site for raid1:
I don't think you understand what "propietary" means in the context of software.
For instance, let's use the example of a pretty famous graphics card manufacturer. This is a privately-owned company that wants to protect their intellectual property, in order to remain competitive and have the technological advantage when they release a new product.
As a profit-seeking entity, they'll first reach out to the largest OS makers, and other hardware vendors, to make deals with them to ensure their shiny new product is well supported on those platforms.
Then, here comes an independent developer (let's call him Jerry) that wants to use this new product on a Linux desktop computer. But Jerry doesn't know how this new product works; there simply aren't enough technical details released to make it work, and the company is very careful about sharing this information.
Jerry tries to make it work somehow, through a painful and time consuming process of trial and error, but without success.
Meanwhile, the company keeps making record profit year after year, and some random user online calls the entire open source community "narrow minded" because of Jerry's incompetence.
Thanks a lot, Jerry.
1 Like