On Thursday, 24 July 2025 16:46:10 British Summer Time Nuno Silva wrote: > On 2025-07-24, Michael wrote: > > On Thursday, 24 July 2025 15:17:02 British Summer Time Dennis Clarke wrote: > >> Dear gentoo folks : > >> I am making very very slow progress with the SiFive P550 RISC-V > >> > >> board wherein I needed to get a GRUB bootloader from the Sifive Ubuntu > >> flash image. I have no idea why the GRUB bootloader built inside the > >> chroot stage 3 is a failure. That is a whole other problem for some > >> other day. I am able to get the grub.cfg from /boot/grub/ directory on > >> the root filesystem. I put it there manually. > >> > >> Once I get the GRUB menu and simply hit enter on the Gentoo linux > >> > >> menu item I get what looks like a bootable system .. until it is *not*. > > > >> Thus : > > [snip ...] > > > >> [ 229.478914] dracut Warning: Could not boot. > >> > >> > >> dracut Warning: Could not boot. > >> > >> [ 229.517264] dracut Warning: /dev/disk/by-uuid/0AC0-79CF does not exist > >> dracut Warning: [ 229.525221] dracut Warning: > >> /dev/disk/by-uuid/d2821a3b-7ad0-44dc-989b-8b5b0c80b947 does not exist > >> /dev/disk/by-uuid/0AC0-79CF does not exist > >> dracut Warning: /dev/disk/by-uuid/d2821a3b-7ad0-44dc-989b-8b5b0c80b947 > >> does not exist > >> > >> Generating "/run/initramfs/rdsosreport.txt" > >> You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick > >> or /boot > >> after mounting them and attach it to a bug report. > >> > >> To get more debug information in the report, > >> reboot with "rd.debug" added to the kernel command line. > >> > >> Dropping to debug shell. > >> > >> dracut:/# > >> > >> I have no idea where these strange UUID numbers are coming from. I was > >> very careful to ensure the grub.cfg and the /etc/fstab were correct. > >> > >> Is there a trivial file somewhere that can be edited? > > > > The UUID 0AC0-79CF is from a DOS filesystem, most likely your ESP. > > > > The UUID d2821a3b-7ad0-44dc-989b-8b5b0c80b947 is from a linux fs. Most > > likely from your / partition. > > > > Run 'blkid' to find out which is which on your drive, or: > > > > ls -alF /dev/disk/by-uuid > > > > Grub will need this to know where it can pick up the initramfs.img. > > That specifically shouldn't be the problem, given that the output shows > the bootloader loading that ramdisk as well as output from what ought to > be the in-ramdisk system itself (notably "Dropping to debug shell." > above)?
Yes, you are quite right. I was thinking if Dennis is going to check through his installation he might as well check GRUB borrowed from Ubuntu too.
signature.asc
Description: This is a digitally signed message part.
