Viewed 21k times. Improve this question. Siler Siler 1 1 gold badge 7 7 silver badges 14 14 bronze badges. I am loathe to answer because I don't use Ubuntu-based distributions and have little familiarity. Grub isn't actually using it as RAID-1 when booting i. Grub is just treating it as a non-RAID volume. RAID-1 is easy to boot from. I probably do it out of superstition more than anything else. In the "olden days" BIOS had trouble accessing large partitions and you ran the risk that, if after a kernel upgrade your new kernel ended up sitting beyond the limits of BIOS-accessible space you might not be able to boot.
I don't know that this is even a factor today, but old habits die hard. I had almost the same problem but i had two partitions - one boot and another for root.
Both in RAID1. See if that works. I think it's just the problem of grub-install really. How it determines the drive with root partition, etc. Without saying what the error was, we can't help. Installing to sda and possibly sdb and sdc as well is the correct thing to do.
To access the raid from the livecd you need to install the mdadm package: sudo apt-get install --no-install-recommends mdadm — psusi. Sorry about that, I've edited my post to include the error message. That is for fakeraid, not software raid. I managed to get it working by creating three partitions on each drive, RAIDing two sets together for the filesystem and swap and leaving the last two unRAIDed.
This seems to work. My only concern is that GRUB isn't installed on the other drive, so if I have a drive failure, I may not be able to boot.
Show 1 more comment. Active Oldest Votes. Improve this answer. Eliah Kagan k 51 51 gold badges silver badges bronze badges. Add a comment. That's why the GRUB install fails. Jeff Atwood Jeff Atwood 1 1 gold badge 10 10 silver badges 21 21 bronze badges.
I'm not sure. I complete the partitioning and installation as per usual, and the installation then fails at GRUB installation. Is this still valid for I can't activate the boot flag in This will be helpful when one HDD fails there's still a working grub. LayerCake LayerCake 1, 9 9 silver badges 23 23 bronze badges. Certainly lilo shows no interest above 1. Then you can install on the RAID array and use your favourite bootloader.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Learn more. Ask Question. Asked 10 years ago. Active 8 years, 11 months ago. Viewed 21k times. Is this a limitation of Grub2, or of the OS installers? Improve this question. Privacy Terms. Quick links. But I'm always getting a bit nervous when it comes to booting. So far I've found the following ways: 1. I can live with having to do something, whenever there is a kernel update, but of course I'd rather be free How do you normally handle software RAID and booting? Re: Recommended way to setup boot robust RAID1 in CentOS7 Post by TrevorH » Wed Jul 30, am I believe that option 1 in your list is the preferred method but whatever way you choose still has the drawback that the computer's BIOS doesn't know about software RAID so when it boots, it will always attempt to boot from the boot records on the first physical disk or whichever one it has been configured to choose.
If you have just replaced the first disk because of failure then it will be blank and the boot will fail. Use the FAQ Luke. The more "out of the box" you make your OS, the simpler it is to maintain down the road with far few problems then when you wedge it onto something that requires a special setup just to boot.
For the 2.
0コメント