GentooThis forum is for the discussion of Gentoo Linux.
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.
Distribution: Gentoo, Ubuntu,and sometimes something from billy gates (when Im desperate)
Posts: 188
Rep:
gentoo grub cant resolve root using raid1
Hi Guys.
Trying to setup a new system on Raid 1.
I followed the handbook and This site and now I cant boot the system.
I get the error unable to resolve root: UUID XXX
The install works as I rsynced it onto a spare HDD with a ext4 partition, plugged it into sda slot (removed other), reconfigured grub and other configs and it boots fine.
I am using Grub2 boot loader following instructions from the handbook
Quote:
grub2-mkconfig -o /boot/grub/grub.cfg
I tried downgrading grub to grub:0 and manually setup my conf file with similar non booting results.
Distribution: Gentoo, Ubuntu,and sometimes something from billy gates (when Im desperate)
Posts: 188
Original Poster
Rep:
Thanks for the help. Happy to reply that I got it working after many many hours trial and error taking suggestions from those listed links.
In the end I think I needed grub2 emerged with -device-mapper use flag and also the auto config from grub wasn't picking the right UUID. When I manually changed it to what was in mdadm.conf, it booted fine.
Distribution: Gentoo, Ubuntu,and sometimes something from billy gates (when Im desperate)
Posts: 188
Original Poster
Rep:
Strange that the system will pick up raid devices from other disk if I put them in. Or if I boot the system from a live cd, then mount the md0, it works fine.
My brain is hurting too much now. I'll look at tomorrow after work.
May still even give up on grub2 and go back to legacy.
Distribution: Gentoo, Ubuntu,and sometimes something from billy gates (when Im desperate)
Posts: 188
Original Poster
Rep:
I have spent so many hours trying to figure this out with no luck
I went back over my kernel config and made sure all drivers for raid were in the kernel.
Still no luck so I removed grub2 and went grub legacy. Following above instructions, it boots with the same issues eg. cant find md0 but the operating system still works.
I followed thesetutorials a few years ago on another machine and it worked great. I cant figure out what I am doing different.
I'm running kernel 3.18. I may have to try downgrading to a lower version.
Distribution: Gentoo, Ubuntu,and sometimes something from billy gates (when Im desperate)
Posts: 188
Original Poster
Rep:
Bit of an update for anyone interested.
I copied a kernel from another machine I setup a few years ago to this machine (/usr/src/linux-3.3.8) including its config and recompiled it on the new machine.
This kernel boots up fine (with no initrd) and everything works fine. (using root=/dev/md0)
I tried booting one of the newer kernels (3.18.7) with no initrd and it wont boot.
My question is what has changed since 3.3.8 that makes raid behave so differently.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.