| 1 |
> > I've got a fresh Gentoo installation that does not boot. I just end up in |
| 2 |
> > the Grub2 shell. |
| 3 |
> > |
| 4 |
> > However when there if I do 'set root=(md/0)' and 'configfile /grub/grub.cfg' |
| 5 |
> > I do get to the Grub2 menu where Gentoo boots just fine. |
| 6 |
> > |
| 7 |
> > /boot and / are both on mdadm devices. |
| 8 |
> > |
| 9 |
> > I've tried re-running grub-mkconfig and grub-install several times without |
| 10 |
> > luck. |
| 11 |
> > |
| 12 |
> > I've added domdadm to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. |
| 13 |
> > |
| 14 |
> > Drives sda/sdb use GPT disklabels and have 20M BIOS boot partitions first. |
| 15 |
> |
| 16 |
> To which device are you installing grub? |
| 17 |
> |
| 18 |
> Check what "core.img" prefix and modules grub-install is using with |
| 19 |
> |
| 20 |
> grub-install --debug $your_device 2>&1 | grep grub-mkimage |
| 21 |
> |
| 22 |
> [I hit a similar problem with mdadm 6 or 7 years ago and had to create |
| 23 |
> a custom "core.img" to boot normally. You might have to do the same |
| 24 |
> but i would've thought that this problem's been solved. I haven't |
| 25 |
> encountered it since.] |
| 26 |
|
| 27 |
I install grub to devices sda and sdb in the hope I can boot from both/either |
| 28 |
|
| 29 |
m / # grub-install --debug /dev/sda 2>&1 | grep grub-mkimage |
| 30 |
grub-install: info: grub-mkimage --directory '/usr/lib/grub/i386-pc' |
| 31 |
--prefix '(mduuid/46488b259685a3b9c52b7449d592dc80)/grub' --output |
| 32 |
'/boot/grub/i386-pc/core.img' --format 'i386-pc' --compression 'auto' |
| 33 |
'ext2' 'part_gpt' 'part_gpt' 'diskfilter' 'mdraid1x' 'biosdisk' |
| 34 |
m / # |
Archives