Re: [blfs-support] Issues with GRUB2 (with UEFI) -- Only Boots Initrd.img and NOT an Updated Kernel Version

Thu, 19 Sep 2019 10:13:14 -0700

 
 
Sent: Friday, September 20, 2019 at 4:42 AM
From: "Christopher Gregory via blfs-support" <blfs-support@lists.linuxfromscratch.org>
To: blfs-support@lists.linuxfromscratch.org
Cc: "Christopher Gregory" <christopher.greg...@mail.com>
Subject: Re: [blfs-support] Issues with GRUB2 (with UEFI) -- Only Boots Initrd.img and NOT an Updated Kernel Version
 
 
Sent: Friday, September 20, 2019 at 4:14 AM
From: "Jared Stevens via blfs-support" <blfs-support@lists.linuxfromscratch.org>
To: "BLFS Support List" <blfs-support@lists.linuxfromscratch.org>
Cc: "Jared Stevens" <jared.stevens1...@gmail.com>
Subject: Re: [blfs-support] Issues with GRUB2 (with UEFI) -- Only Boots Initrd.img and NOT an Updated Kernel Version
 
 
On Thu, Sep 19, 2019 at 10:33 AM Bruce Dubbs via blfs-support <blfs-support@lists.linuxfromscratch.org> wrote:
 
> Did you actually use the uuid for the / partition?  Are you using a
> MSDOS or GPT partition table?  PARTUUID only works for GPT partition tables.
 
Yes the disk is using a GPT partition table that I configured initially in Linux before the build.
 
The result of the 'blkid' command (in chroot) for the disk is as follows:
 
/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"
 
My current /etc/fstab file:
 
# Begin /etc/fstab

# file system                            mount-pt     type         options     dump     fsck

#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-c17db827f78e   /  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

proc                                    /proc      proc   nosuid,noexec,nodev     0      0
sysfs                                   /sys       sysfs  nosuid,noexec,nodev     0      0
devpts                                  /dev/pts   devpts   gid=5,mode=620        0      0
tmpfs                                   /run       tmpfs     defaults             0      0
devtmpfs                                /dev       devtmpfs  mode=0755,nosuid     0      0

efivarfs                        /sys/firmware/efi/efivars  efivarfs  defaults     0      1
 
Finally, here is what my grub.cfg looks like as of now (Note that I went ahead and tried updating the kernel to 5.2.14 from 5.2.11 while still retaining my initial 5.2.8 kernel image as that is the only one that will boot -- on the initrd.img ONLY though. The config is the exact same however):
 
# 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.14 (LFS-JWS-9.0-Sept19)"  {
    linux   /vmlinuz-5.2.14-lfs-9.0-systemd; root=PARTUUID=2273falc-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.14 (LFS-JWS-9.0-Sept19)" {
    linux  /vmlinuz-5.2.14-lfs-9.0-systemd; root=UUID=aa72e154-0f87-47ea-bf33-c17db827f78e ro rootdelay=10 pci=noaer
    # initrd .img for Intel & initramfs
    initrd /boot/microcode.img /boot/initrd.img-5.2.14
  }
     
  menuentry "GNU/Linux, Linux 5.2.8 (LFS-JWS-9.0-Aug19)"  {
    linux   /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
  }
 
I have tried a wide variety of different setups and adjustments to get this thing working with no luck. I am starting to wonder if it's simply something wrong with my build and should I just give up on it and start over again from scratch.
 
I would hate to throw away the last two months of effort I put forth in it, but I haven't been making any headway on it for the last two weeks or more because of this issue (and two others as well).
 
Regardless, thank you guys for the suggestions!
 
-- Jared
 
 
Hello Jared,
 
I have just had a thought.  With my own configuration I too could not get my system to boot, because I found that I was entering the menu items into the wrong grub.cfg file.  As you have an internal drive as well as the external drive, I would suggest that you check both drives and duplicate the grub.cfg on both drives.
 
From what you have already done, this makes the most sense to me.
 
Regards,
 
Christopher.
 
Hello Jared,
 
Sorry but I forgot to also mention that you will also need to copy the kernel image, system map etc to the other drive as well.
 
Regards,
 
Christopher.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to