- Windows Boot Manager (Samsung SSD 970 EVO 250GB)
- NVME: Samsung SSD 970 EVO 250GB
Now what happens if you select option 2 from that menu?
Also, what happens if you boot to the live media then run efibootmgr -v? Please show us that output.
1 Like
The following shows up:
Reboot and Select proper Boot device
or Insert Boot Media in selected Boot device and press a key
$ efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0001,0004,0000,0002,0003
Boot0000* Windows Boot Manager HD(1,GPT,af1d05a1-1ecc-4513-8889-0ca03b5de212,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...d................
Boot0001* Hard Drive BBS(HD,,0x0)..GO..NO........q.S.a.m.s.u.n.g. .S.S.D. .9.7.0. .E.V.O. .2.5.0.G.B....................A...........................%8V..7......4..Gd-.;.A..MQ..L.S.4.6.5.N.X.0.M.6.1.2.0.3.7.W........BO
Boot0002* UEFI: USB PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(1,0)/CDROM(1,0xac,0x13df0)..BO
Boot0003* UEFI: USB, Partition 2 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(1,0)/HD(2,MBR,0x3caf6577,0xac,0x4f7c)..BO
Boot0004* USB BBS(USB,,0x0)..GO..NO........i.U.S.B....................A.............................6..Gd-.;.A..MQ..L.A.C.2.5.B.9.5.D.1.2.4.5.4.0.9.8........BO
Well, that is disappointing. Both the bios boot menu and efibootmgr fail to see grub as bootable.
if you once again boot to the live media, and following my steps above to mount the system drives and chroot into that environment, after mounting all the other partitions with “mount -a”, what can you see if you run the mount command at this point.
I am particularly interested in comparing the mounted devices with the output of lsblk -o PATH,UUID,FSTYPE /dev/nvme0n1 and with the result of cat /etc/fstab. So please post the output of all three of those commands now. Add the result of sudo lvscan as well please.
1 Like
I am showing the entire thing in case I did something wrong.
$ sudo vgchange -a y nobaraVG
2 logical volume(s) in volume group "nobaraVG" now active
[liveuser@localhost-live ~]$ su
[root@localhost-live liveuser]# mount -t ext4 /dev/mapper/nobaraVG-root /mnt
[root@localhost-live liveuser]# for PART in /sys /proc /run /dev ; do
mount -o bind $PART /mnt/$PART
done
[root@localhost-live liveuser]# chroot /mnt
[root@localhost-live /]# mount -a
[root@localhost-live /]# mount
/dev/mapper/nobaraVG-root on / type ext4 (rw,relatime,seclabel)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,size=3258616k,nr_inodes=819200,mode=755,inode64)
devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=4096k,nr_inodes=1048576,mode=755,inode64)
/dev/nvme0n1p5 on /boot type ext4 (rw,relatime,seclabel)
/dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
/dev/mapper/nobaraVG-home on /home type ext4 (rw,relatime,seclabel)
# lsblk -o PATH,UUID,FSTYPE /dev/nvme0n1 PATH UUID FSTYPE /dev/mapper/nobaraVG-home 7151af90-b8ab-418c-a607-82896371bf5b ext4 /dev/mapper/nobaraVG-root c58834a5-ed98-4e58-a262-c905384f6c1a ext4 /dev/nvme0n1 /dev/nvme0n1p1 9839-34AF vfat /dev/nvme0n1p2 /dev/nvme0n1p3 1E1C3A571C3A2A63 ntfs /dev/nvme0n1p4 DE96364096361A0B ntfs /dev/nvme0n1p5 ae022667-835d-4df9-8e5e-8028d1e40488 ext4 /dev/nvme0n1p6 SAX4bc-2pXh-qcTf-Pplt-igbp-4xZU-f6N6tN LVM2_member
# cat /etc/fstab # # /etc/fstab # Created by anaconda on Tue Aug 9 22:53:06 2022 # # Accessible filesystems, by reference, are maintained under '/dev/disk/'. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info. # # After editing this file, run 'systemctl daemon-reload' to update systemd # units generated from this file. # /dev/mapper/nobaraVG-root / ext4 defaults 1 1 UUID=ae022667-835d-4df9-8e5e-8028d1e40488 /boot ext4 defaults 1 2 UUID=9839-34AF /boot/efi vfat umask=0077,shortname=winnt 0 2 /dev/mapper/nobaraVG-home /home ext4 defaults 1 2
# sudo lvscan ACTIVE '/dev/nobaraVG/home' [45.88 GiB] inherit ACTIVE '/dev/nobaraVG/root' [70.00 GiB] inherit
Now lets see the output of ls /boot ls /boot/grub2 ls /boot/efi ls /boot/efi/EFI
1 Like
ls /boot config-5.18.17-201.fsync.fc36.x86_64 lost+found config-5.18.18-201.fsync.fc36.x86_64 memtest86+-5.31 config-5.19.4-201.fsync.fc36.x86_64 symvers-5.18.17-201.fsync.fc36.x86_64.gz efi symvers-5.18.18-201.fsync.fc36.x86_64.gz elf-memtest86+-5.31 symvers-5.19.4-201.fsync.fc36.x86_64.gz extlinux System.map-5.18.17-201.fsync.fc36.x86_64 grub2 System.map-5.18.18-201.fsync.fc36.x86_64 initramfs-0-rescue-8ae5229828014ea2a89e0a795b4b9270.img System.map-5.19.4-201.fsync.fc36.x86_64 initramfs-5.18.17-201.fsync.fc36.x86_64.img vmlinuz-0-rescue-8ae5229828014ea2a89e0a795b4b9270 initramfs-5.18.18-201.fsync.fc36.x86_64.img vmlinuz-5.18.17-201.fsync.fc36.x86_64 initramfs-5.19.4-201.fsync.fc36.x86_64.img vmlinuz-5.18.18-201.fsync.fc36.x86_64 loader vmlinuz-5.19.4-201.fsync.fc36.x86_64
# ls /boot/grub2 fonts grub.cfg grubenv
# ls /boot/efi EFI
ls /boot/efi/EFI Boot Microsoft
Were those LVs available before you ran the “vgchange” command to activate the VG?
1 Like
i am not sure, I didn’t try it before activating the VG
Here seems to be the issue. At that location should be another directory named “fedora” which does not seem to have been created.
I must ask how you booted the USB device. Was it in UEFI mode or not?
If not booted to uefi mode then some things that rely on efi to function do not get configured in grub.
please post the output of ls /sys/firmware/efi
1 Like
it was in UEFI mode yes. The other option which I didnt choose,is supposed to be used USB thats supposed to be BIOS mode if I am not wrong.
# ls /sys/firmware/efi config_table efivars esrt fw_platform_size fw_vendor mok-variables runtime runtime-map systab
Ok, that definitely indicates booted in uefi mode.
Now please show dnf list installed grub2*
1 Like
# dnf list installed grub2* Installed Packages grub2-common.noarch 1:2.06-47.fc36 @updates grub2-efi-ia32.x86_64 1:2.06-47.fc36 @updates grub2-efi-ia32-cdboot.x86_64 1:2.06-47.fc36 @updates grub2-efi-x64.x86_64 1:2.06-47.fc36 @updates grub2-efi-x64-cdboot.x86_64 1:2.06-47.fc36 @updates grub2-pc.x86_64 1:2.06-47.fc36 @updates grub2-pc-modules.noarch 1:2.06-47.fc36 @updates grub2-tools.x86_64 1:2.06-47.fc36 @updates grub2-tools-efi.x86_64 1:2.06-47.fc36 @updates grub2-tools-extra.x86_64 1:2.06-47.fc36 @updates grub2-tools-minimal.x86_64 1:2.06-47.fc36 @updates
Now dnf list installed shim*
1 Like
dnf list installed shim* Installed Packages shim-ia32.x86_64 15.6-2 @fedora-updates shim-x64.x86_64 15.6-2 @fedora-updates
It would appear that you have all the correct packages, but we need to recreate that directory and its content.
Please run rm /boot/grub2/grub.cfg
followed by dnf reinstall grub2* shim*
If not already as root you may need to use sudo with those commands.
Post the results of what it proposes before you tell it yes for the reinstall.
1 Like
# rm /boot/grub2/grub.cfg rm: remove regular file '/boot/grub2/grub.cfg'? y [root@localhost-live /]# dnf reinstall grub2* shim* determining the fastest mirror (19 hosts).. done. [=== ] --- B/s | 0 B --:-- ETA Fedora 36 - x86_64 - Updates 14 kB/s | 32 kB 00:02 nobara-nvidia 6.4 kB/s | 5.7 kB 00:00 Installed package grub2-common-1:2.06-47.fc36.noarch (from updates) not available. Installed package grub2-efi-ia32-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package grub2-efi-ia32-cdboot-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package grub2-efi-x64-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package grub2-efi-x64-cdboot-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package grub2-pc-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package grub2-pc-modules-1:2.06-47.fc36.noarch (from updates) not available. Installed package grub2-tools-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package grub2-tools-efi-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package grub2-tools-extra-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package grub2-tools-minimal-1:2.06-47.fc36.x86_64 (from updates) not available. Installed package shim-ia32-15.6-2.x86_64 (from fedora-updates) not available. Installed package shim-x64-15.6-2.x86_64 (from fedora-updates) not available. Error: No packages marked for reinstall.
also I want to appreciate you for taking your time and helping me out, truly grateful!
1 Like
Repeat the reinstall command and add --refresh to it. Sometimes the mirrors do not respond well
1 Like
its still not responding sadly