Possibly too early, as grub2 is not stable yet, but I found out: the gentoo handbook stated to mount /proc and to bind-mount /dev before chrooting. I just started a new install, and tried to use grub2-mkconfig, which failed. The reason is that function prepare_grub_to_access_device within grub-mkconfiglib tries to read data from /sys to find data about the boot device. (try fs_hint="`"${grub_probe}" --device "${device}" --target=compatibility_hint`") Reproducible: Always Steps to Reproduce: 1. Follow the handbook to chroot 2. emerge grub2 3. grub2-mkconfig Actual Results: 00_header is executed 10_linux is partly executed and then silently fails Expected Results: the handbook should advise to mount -bind /sys ${chroot-dir}/sys in order to allow grub2-mkconfig to finish correctly
it's still hardmasked. we don't document grub2 anywhere, so we can't put this in our documentation until it's marked stable. however, you're welcome to update the gentoo wiki. it should already have a grub2 page.
*** Bug 420159 has been marked as a duplicate of this bug. ***
