I finally have X Windows up and running, so I certainly can boot up ok.
This request is to help me better understand the LFS book's booting
procedures.
I've built LFS with systemd, and used LVM and GPT partitions. After some
earlier help, I found that an initramfs was key to making things work.
But it doesn't seem to work with what I've done with GRUB.
I'm not able to boot using GRUB, but am using rEFInd from RodsBooks. My
basic question here is: Why can I not boot using GRUB?
rEFInd has a configuration file refind.conf, which in my system contains
these successful lines:
########
menuentry Linux-LFS-foooo {
icon EFI/refind/icons/os_linux.png
volume efi-boot
loader /vmlinuz-5.4.8-lfs-20200109-systemd
initrd /initrd.img-5.4.8
options "ro root=UUID=f7309704-012d-4115-884d-403c6e06a989
initrd=/initrd.img-5.4.8"
}
########
I used some concepts from the rEFInd configure file to modify grub.cfg.
The grub.cfg is now:
########
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod gzio
insmod part_gpt
insmod ext2
# set root=(hd1, gpt1)
# set root=(hd1, gpt3)
set root=UUID="08122b74-5c84-4aa5-947e-0d2952db1ecd"
# set root=(lvm/lfslvm-boot)
insmod efi_gop
insmod efi_uga
insmod font
if loadfont /boot/grub/fonts/unicode.pf2; then
loadfont /boot/grub/fonts/unicode.pf2
set gfxmode=auto
insmod gfxterm
set gfxpayload=keep
terminal_output gfxterm
fi
menuentry "GNU/Linux, Linux vmlinuz-5.4.8-lfs-20200109-systemd" {
linux /vmlinuz-5.4.8-lfs-20200109-systemd
root=UUID=f7309704-012d-4115-884d-403c6e06a989 initrd=/initrd.img-5.4.8 ro
initrd /initrd.img-5.4.8
}
########
You can see that the "root=..." lines are essentially the same in both
configuration files. However, in grub.cfg you can see some of my
attempts at getting "set root=..." to work. It appears that this is one
issue GRUB has when trying to boot.
Here are the relevant bits from blkid on the Fedora host system:
#########
[root@localhost Buildscripts-sysd9]# blkid
/dev/sdb1: LABEL_FATBOOT="efi-boot" LABEL="efi-boot" UUID="000A-CAC9"
TYPE="vfat" PARTLABEL="EFI System" PARTUUID="3ae2214c-3cf6-4324-80cf-
a01741ccbccc"
/dev/sdb3: UUID="VzWWbo-7FXe-LfrH-vMkK-ewze-y0kQ-vFV395"
TYPE="LVM2_member" PARTLABEL="Linux LVM" PARTUUID="b0ce9087-639c-4487-
97dc-5c947aec3603"
/dev/sdb4: UUID="u3BU8P-G1GU-FqWS-sm2q-5xpe-tvUb-68s3zX"
TYPE="LVM2_member" PARTLABEL="Linux LVM" PARTUUID="35e97922-0128-453a-
afbf-3f0dd75d98b2"
/dev/mapper/lfslvm-boot: UUID="08122b74-5c84-4aa5-947e-0d2952db1ecd"
TYPE="ext4"
/dev/mapper/lfslvm-root: UUID="f7309704-012d-4115-884d-403c6e06a989"
TYPE="ext4"
#########
When I try to boot with grub, the grub command interpreter puts out this error message:
error: disk '08122b74-5c84...' not found.
error: you need to load the kernel first.
I get a similar error no matter what "set root=..." line I use. For
example, when I use:
set root=(hd1, gpt3)
I get:
error: disk '(hd1, ' not found.
I have no clue what " '(hd1, ' " represents.
See grub.cfg above for my attempts.
I've been unable to find relevant information on the Net.
Alan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
