Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have 2 SSD drives setup with MD RAID0, this computer has no UEFI so I am having to use GRUB2, now at first I tried having a separate partition outside of raid for /boot, if I do it this way and set the root and all that to /dev/sda1 (/boot partition with grub) it will load and drop into emergency shell, from which I could manually mount /dev/md0p3 (raid partition which is real root), and chroot to it, then I thought well what if I try to just keep /boot in the same root partition, and let mbr be in the /dev/sda1, but when I try to do that grub-install fails saying it can't find a device for /boot/grub. Someone please help me figure this out .
I have the raid partition working fine, its getting GRUB to load it! As I said at first when it goes to boots, it drops into emergency shell, from which I can mount the /dev/md0p3 raid partition, and chroot to it, but its getting to to do that properly on its own without dropping to e shell that I am trying to figure out.
So some sort of a process, I figured out that the UUID's in grub config for the /boot partition need to point to that partition, and set ROOT= should be the UUID that is the actual root of the OS, I got as far now as it shows a Mint logo for about, 5 seconds, then exists to emergency shell with no real indication of exactly what is going on or why its failing. I can manually run ./init in inetramfs and get it to show the logo again for a few seconds, but it just exits out complains about mounting sysfs proc and udev being resource busy (I iamgine cause it mounted them the first time around). Also complains about /dev/pts already existing when it tries to mkdir, but that is before the logo comes up so I don't think that is what is causing it to fail.
Well I feel like I gave up doing it this way, but I just made a 16GB standard partition on each SSD drive, OSA and OSB, so they can be 2 diferent OS backup images, and the rest of the SSD's are software raid 0, and that works fine, swap is on that, as well as scratch space and it works right out the box that way.
I am, only UEFI can boot from a software raid as it required gpt support, BIOS boot only supports MBR, which means grub must be installed on a drive with msdos partition table. Anyway I gave up doing it how I really wanted to and put the entire OS on a single non-SW raid partitition, then afterwards I just moved the critical stuff like /usr and /var to a different partitition bind mounted to a folder. Working well. I will work on getting it running off RAMDISK once I get all the RAM I ordered in, only have 32GB installed right now, I have 128GB coming.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.