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