On Fri, May 14, 2021 at 2:36 AM John Covici <covici@ccs.covici.com> wrote:

I would look in the grub.cfg and give us exactly what is in the stanza
you are using, including where it thinks the root file system is,
etc.  Also, see if there is any genkernel option to get some debugging
info out of the initrd, I know using dracut you can get breakpoints
during the process and see how its doing.

Here’s what I see when pressing “e” just before the system attempts to boot:

setparams ‘Gentoo GNU/Linux’

        load_video
        if [ “x$grub_platform” = xefi ]; then
                set gfxpayload=keep
        fi
        insmod gzio
        insmod part_gpt
        insmod fat
        set root=‘hd0,gpt2’
        if [ x$feature_platform_search_hint = xy ]; then
          search —no-floppy —fs-uuid —set=root —hint-bios=hd0,gpt2 —hint-baremetal=ahci0, got2 5C75-30A0
        else
          search —no-floppy —fs-uuid —set=root 5C75-30A0
        fi
        echo            ‘Loading Linux 5.10.27-gentoo-x86_64 ...’
        linux             /vmlinuz-5.10.27-gentoo-x86_64 root=UUID=0df096ca-4dc8-4325-9296-7b0ddb67f044 ro loglevel=4 nomodeset
        echo            ‘Loading initial ramdisk ...’
        initrd            /early_ucode.cpio /initramfs-5.10.27-gentoo-x86_64.img

I have checked the uuid and filenames - they are correct.  (hd0,gpt2) makes sense.  There’s only 1 disk connected, it uses gpt, and the second partition is a fat boot partition with the above uuid.  The named files exist on that partition.

I don’t see anything in ‘man genkernel’ that looks like a way to get debug info out of an initrd/initramfs.  Looks like there’s a way to turn it off, so perhaps it’s on by default?

John