So I took your advice below:
*> What you need to skip initrd is to use root=PARTUUID=<value> or the >
traditional root=/dev/sda2. Since you are using an external usb drive, >
sda may be something else like sdb.*
And updated my grub.cfg to now say:
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod gzio
insmod part_gpt
insmod ext2
set root=(hd0,gpt2)
# hd[x] is the drive of the LFS partion and gpt[y] is the partition
insmod efi_gop
insmod efi_uga
insmod font
if loadfont /grub/unicode.pf2; then
loadfont /grub/unicode.pf2
set gfxmode=auto
insmod gfxterm
set gfxpayload=keep
terminal_output gfxterm
fi
menuentry "GNU/Linux, Linux 5.2.11 (LFS-JWS-9.0-Sept19)" {
linux /boot/vmlinuz-5.2.11-lfs-9.0-systemd;
root=*PARTUUID=2273fa1c-2403-4350-850a-e7bfa3859bae
*ro rootdelay=10 pci=noaer
# initrd .img for Intel microcode
initrd /boot/microcode.img
}
# Generic initramfs identified by UUID (w/ Intel microcode initrd .img)
menuentry "GNU/Linux, Initrd.img 5.2.11 (LFS-JWS-9.0-Sept19)" {
linux /boot/vmlinuz-5.2.11-lfs-9.0-systemd;
root=UUID=aa72e154-0f87-47ea-bf33-c17db827f78e ro rootdelay=10 pci=noaer
# initrd .img for Intel microcode + initramfs .img
initrd /boot/microcode.img /boot/initrd.img-5.2.11
}
menuentry "GNU/Linux, Linux 5.2.8 (LFS-JWS-9.0-Aug19)" {
linux /boot/vmlinuz-5.2.8-lfs-9.0-rc1-systemd; root=
*PARTUUID=2273fa1c-2403-4350-850a-e7bfa3859bae* ro rootdelay=10
# initrd .img for Intel microcode
initrd /boot/microcode.img
}
# Generic initramfs identified by UUID (w/ Intel microcode initrd .img)
menuentry "GNU/Linux, Initrd.img 5.2.8 (LFS-JWS-9.0-Aug19)" {
linux /boot/vmlinuz-5.2.8-lfs-9.0-rc1-systemd
root=UUID=aa72e154-0f87-47ea-bf33-c17db827f78e ro rootdelay=10 pci=noaer
initrd /boot/microcode.img /boot/initrd.img-5.2.8
}
However, attempts to boot the system without the initrd.img OR either of
the 5.2.11 kernel options yielded the exact same error message:
*grub: error: disk 'PARTUUID=2273fa1c-2403-4350-850a-e7bfa3859bae' not
found*
*Press any key to continue...*
For the initrd.img-5.2.11 entry, the error reads:
*grub: error: disk 'UUID=aa72e154-0f87-47ea-bf33-c17db827f78e' not found*
*Press any key to continue...*
Pressing a key will, for some reason, start the boot process anyway until
it reaches the VFS panic error and stops.
I also tried changing it to "root=/dev/sdb2" with the same error (replace
"PARTUUID=..." with "/dev/sdb2"). What confuses me the most is how the
Initrd.img for 5.2.8 will boot the OS no problem, yet the 5.2.11 option
configured the exact same way cannot find the root partition.
Just for the heck of it, I even tried changing my /etc/fstab file to find
the UUID instead of PARTUUID for the partitions:
#PARTUUID=34f54da4-22c7-4037-a514-00139bac5672 /boot/efi vfat
defaults 0 1
*UUID=6542-5441 * /boot/efi vfat
defaults 0 1
*UUID=aa72e154-0f87-47ea-bf33-c*17db827f78e / ext4
noatime,errors=remount-ro 0 0
#PARTUUID=2273fa1c-2403-4350-850a-e7bfa3859bae / ext4
noatime,errors=remount-ro 0 0
#PARTUUID=23ecb3ba-2855-44b4-9411-cfa2ef31feeb swap swap
pri=1 0 0
*UUID=dd31c8ab-5fb8-461d-a10f-a5d2de720646 * swap swap
pri=1 0 0
No change whatsoever. I am utterly perplexed as to what the problem is
here. Just for reference, here is the output for the 'blkid' command in LFS
(note that I was in chroot so the drive name was assigned as 'sdc' in this
instance due to a microSD card being connected to the laptop as well:
*/dev/sdc1: UUID="6542-5441" TYPE="vfat" PARTLABEL="boot"
PARTUUID="34f54da4-22c7-4037-a514-00139bac5672"/dev/sdc2:
UUID="aa72e154-0f87-47ea-bf33-c17db827f78e" TYPE="ext4"
PARTUUID="2273fa1c-2403-4350-850a-e7bfa3859bae"/dev/sdc3:
UUID="dd31c8ab-5fb8-461d-a10f-a5d2de720646" TYPE="swap" PARTLABEL="swap"
PARTUUID="23ecb3ba-2855-44b4-9411-cfa2ef31feeb"*
Jared Stevens
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
