On 2020-01-14 16:08 -0700,Alan Feuerbacher wrote: > On 1/14/2020 7:39 AM, Xi Ruoyao wrote: > > On 2020-01-13 13:41 -0700, Alan Feuerbacher wrote: > > > I'm building the LFS systemd development version, and having some > > > difficulty deciding how to configure some UEFI things. > > > > > > I'm using GPT partitions and LVM (Logical Volume Management). > > Using LVM for root FS would require an initramfs: > > > > http://svn.linuxfromscratch.org/hints/trunk/Root_FS_on_RAID+encryption+LVM.txt > > > > /* snip */ > > Building an initramfs was the key: I can now boot up using rEFInd. > > I still can't boot with grub, though, even though I used some concepts > from the rEFInd configure file to modify grub.cfg.
/* snip */ > 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" /* snip */ > When I try to boot with grub, the grub command interpreter puts out this error > message: > > error: disk '08122b74-5c84...' not found. "set root=(some uuid)" is wrong. Grub doesn't support this thing. It should be something like search --no-floppy --fs-uuid --set=root 08122b74-5c84... > 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. I don't think LVM devices are "hard drive" in Grub. You can get into the grub command line interface and try to find the correct partition. From "info grub": > This means that, for example, you only need to type > > set root=( > > followed by a <TAB>, and GRUB will display the list of drives, > partitions, or file names. So it should be quite easy to determine the > name of your target partition, even with minimal knowledge of the > syntax. /* snip */ > Yes, as I said above, that worked with rEFInd, but not grub. Any ideas? They are different softwares, and there is no "ISO/IEC 99999:2020 - Information Technology -- Bootloader" forcing their behavior. > I noticed something very strange. I have separate partitions for /boot > and /boot/efi. In the Fedora 31 host system, /boot is populated as expected: > > (lfs chroot) root:/boot# ll > total 39092 > -rw-r--r-- 1 root root 5293922 Jan 14 12:16 System.map-5.4.8 > -rw-r--r-- 1 root root 132145 Jan 14 12:17 config-5.4.8 > drwxr-xr-x 3 root root 4096 Dec 31 1969 efi > drwxr-xr-x 4 root root 4096 Jan 14 14:13 grub > drwxr-xr-x 2 root root 4096 Jan 14 14:39 grubexp > -rw-r--r-- 1 root root 22604288 Jan 14 11:29 initrd.img-5.4.8 > drwx------ 2 root root 16384 Jan 2 14:26 lost+found > -rw-r--r-- 1 root root 511 Jan 10 20:38 refind_linux.conf > -rw-r--r-- 1 root root 11957120 Jan 14 12:16 vmlinuz-5.4.8-lfs-20200109- > systemd > > But in my newly booted LFS system, nothing but the efi entry is there. What's > going on? I don't know. You can just run "mount" in both systems to see. -- Xi Ruoyao <xry...@mengyan1223.wang> School of Aerospace Science and Technology, Xidian University -- 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