I want my Fedora back [Intel NUC, dual boot, SSD and HDD]

someuser123 · February 12, 2023, 2:30pm

Have been happily using Fedora 36 on a single SSD for quite some time till adding a HDD with Ubuntu. Can’t remember an exact point where it turned south, there were a bunch of errors I tried to google with little success (should have tried chatgpt perhaps )
Gave up finally and tried to stay with Ubuntu 20. Well, after a few weeks I’d very much love to get my Fedora back but can’t find a way to boot it again.
Unfortunately my knowledge level of mounting points, grub and stuff is at “rm -rf /” level. Please help me get back and avoid making any more mess I already did. Thanks!

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 116,7M 1 loop /snap/core/14447
loop1 7:1 0 49,8M 1 loop /snap/snapd/17950
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 512M 0 part
└─sda2 8:2 0 465,3G 0 part /
nvme0n1 259:0 0 223,6G 0 disk
├─nvme0n1p1 259:1 0 600M 0 part /boot/efi
├─nvme0n1p2 259:2 0 1G 0 part
└─nvme0n1p3 259:3 0 222G 0 part

efibootmgr
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,0002,0003,0000,0001,0004
Boot0000* Windows Boot Manager
Boot0001* Fedora
Boot0002* UEFI : LAN : PXE IP4 Intel(R) Ethernet Connection (6) I219-V
Boot0003* UEFI : LAN : PXE IP6 Intel(R) Ethernet Connection (6) I219-V
Boot0004* Windows Boot Manager
Boot0007* ubuntu

fdisk -l
Disk /dev/loop0: 116,71 MiB, 122363904 bytes, 238992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 49,85 MiB, 52248576 bytes, 102048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme0n1: 223,58 GiB, 240057409536 bytes, 468862128 sectors
Disk model: Force MP510
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6B9AEACF-6BDE-4C61-86C2-90366522191B

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1230847 1228800 600M EFI System
/dev/nvme0n1p2 1230848 3327999 2097152 1G Linux filesystem
/dev/nvme0n1p3 3328000 468860927 465532928 222G Linux filesystem

Disk /dev/sda: 465,78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000BPKT-7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: E7AB9463-4088-4BBF-A237-29CF8AD0C522

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 976771071 975720448 465,3G Linux filesystem

semiconductor · February 12, 2023, 2:40pm

It looks like we’re having the same issue loading Fedora, except I’m running a Fedora/Windows11 dualboot (boots Windows11 all the time). Could not find a solution for this throuble, installed Manjaro instead of Fedora. Manjaro has no problem with GRUB.

computersavvy · February 12, 2023, 2:41pm

Please post the output of lsblk -f so we can see exactly what file systems are on your devices.

someuser123 · February 12, 2023, 2:53pm

lsblk -f
NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0
     squash                                                  0   100% /snap/core
loop1
     squash                                                  0   100% /snap/snap
sda                                                                   
├─sda1
│    vfat         6B14-552A                                           
└─sda2
     ext4         f1f7d5d1-1eca-4c9a-84ce-c3491d2a89ad  307,7G    28% /
nvme0n1
│                                                                     
├─nvme0n1p1
│    vfat         4357-B9DA                             576,4M     4% /boot/efi
├─nvme0n1p2
│    ext4         ce440cca-bd0e-4f0b-b480-2b5f2e4818a8                
└─nvme0n1p3
     btrfs  fedora_localhost-live
                  31760f0f-4928-425d-ac15-b28423054106

computersavvy · February 12, 2023, 3:44pm

Note that I edited your post above to add the Preformatted text tags </> to make it look as it did on your screen. Please post command outputs using those tags from the indicated button above.

From what you have posted, it appears you are currently booting ubuntu, and that you have two efi partitions (both /dev/nvme01p1 and /dev/sda1).

I suspect that ubuntu cannot boot fedora since fedora uses btrfs on /dev/nvme0n1p3.

This may be very simple.
Try using this command to select fedora for the next boot.
efibootmgr -n 0001 followed by a reboot.
If that works then change the boot order (which currently shows ubuntu [Boot0007] as first) to the following.
efibootmgr -o 0001,0007,0000 which should set the boot order to fedora, ubuntu, windows (in that order).

Then check the fedora grub boot menu to verify that all 3 OSes are listed and can be selected from the grub menu.

Note that doing an update to ubuntu may cause it to take priority in the boot order again, and these steps may need to be repeated to keep fedora first in the boot order.
Note also that once you have fedora booted you probably should run sudo dnf upgrade to ensure that the latest updates are installed, including the newest kernel. Installing the newest kernel should update grub for fedora so it sees and can manage booting to all 3 OSes.

someuser123 · February 12, 2023, 4:22pm

@computersavvy Thank you Good Sir. Unfortunately efibootmgr -n 0001 made no difference.
Moreover, the “Boot Menu”, accessible by F10 at the very early step of power on, displays only “ubuntu” choice in the list of UEFI devices. There must be something else: have you mentioned “btrfs”? What if we change this one to be … well, no idea.

semiconductor · February 12, 2023, 4:54pm

Probably, bug in distro?

vekruse · February 12, 2023, 8:44pm

Can we get some more info about the uefi entries? Run these commands.

lsblk -o PATH,PARTUUID
efibootmgr -v

someuser123 · February 13, 2023, 8:57am

I totally messed up the system by executing efibootmgr -o 0001,0007,0000 yesterday.
This smart move led to ubuntu loader total disappearance and Fedora boot options appeared back on the boot screen. And this is where I realised why I switched to Ubuntu, it was because of these:

failed to listen on dbus.s D-bud System Message Bus Socket
Dependency failed … Power Profiles daemon

Of course the rescue mode mode came with “the root account is locked”.
So, I am from live Fedora 37 USB now and here is my current lsblk and efibootmgr

[liveuser@localhost-live ~]$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0   1.8G  1 loop 
loop1         7:1    0   7.6G  1 loop 
├─live-rw   253:0    0   7.6G  0 dm   /
└─live-base 253:1    0   7.6G  1 dm   
loop2         7:2    0    32G  0 loop 
└─live-rw   253:0    0   7.6G  0 dm   /
sda           8:0    0 465.8G  0 disk 
├─sda1        8:1    0   512M  0 part 
└─sda2        8:2    0 465.3G  0 part 
sdb           8:16   1  14.5G  0 disk 
├─sdb1        8:17   1   1.9G  0 part /run/initramfs/live
├─sdb2        8:18   1   9.9M  0 part 
└─sdb3        8:19   1   300K  0 part 
zram0       252:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 223.6G  0 disk 
├─nvme0n1p1 259:1    0   600M  0 part 
├─nvme0n1p2 259:2    0     1G  0 part 
└─nvme0n1p3 259:3    0   222G  0 part

[liveuser@localhost-live ~]$ lsblk -o PATH,PARTUUID
PATH                  PARTUUID
/dev/loop0            
/dev/loop1            
/dev/loop2            
/dev/sda              
/dev/sda1             8b47f155-9050-4259-b31c-a2c3b6f30aef
/dev/sda2             5175c780-fc64-41f6-9380-d87841078eb9
/dev/sdb              
/dev/sdb1             ac25d109-653f-46d5-99c2-9890086ba449
/dev/sdb2             ac25d109-653f-46d5-99c1-9890086ba449
/dev/sdb3             ac25d109-653f-46d5-99c0-9890086ba449
/dev/zram0            
/dev/mapper/live-rw   
/dev/mapper/live-rw   
/dev/mapper/live-base 
/dev/nvme0n1          
/dev/nvme0n1p1        c1e3fdd4-5851-4fbc-aa7a-f0c4256af0d8
/dev/nvme0n1p2        4ce695e1-df5b-4ff8-a55d-4ec393c0c63f
/dev/nvme0n1p3        699217ac-4195-4806-a6cc-b15c791dacc8
[liveuser@localhost-live ~]$ efibootmgr -v
BootCurrent: 000A
Timeout: 1 seconds
BootOrder: 000A,0001,0008,0009,0007,0000,0004
Boot0000* Windows Boot Manager	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000096000100000010000000040000007fff0400
      dp: 01 04 14 00 e7 75 e2 99 a0 75 37 4b a2 e6 c5 38 5e 6c 00 cb / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 96 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* Fedora	HD(1,GPT,c1e3fdd4-5851-4fbc-aa7a-f0c4256af0d8,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 c0 12 00 00 00 00 00 d4 fd e3 c1 51 58 bc 4f aa 7a f0 c4 25 6a f0 d8 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0004* Windows Boot Manager	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000016070100000010000000040000007fff0400
      dp: 01 04 14 00 e7 75 e2 99 a0 75 37 4b a2 e6 c5 38 5e 6c 00 cb / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 16 07 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0007* ubuntu	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
      dp: 01 04 14 00 e7 75 e2 99 a0 75 37 4b a2 e6 c5 38 5e 6c 00 cb / 7f ff 04 00
Boot0008* UEFI : LAN : PXE IP4 Intel(R) Ethernet Connection (6) I219-V	PciRoot(0x0)/Pci(0x1f,0x6)/MAC(1c697a66308a,0)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 06 1f / 03 0b 25 00 1c 69 7a 66 30 8a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0c 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
Boot0009* UEFI : LAN : PXE IP6 Intel(R) Ethernet Connection (6) I219-V	PciRoot(0x0)/Pci(0x1f,0x6)/MAC(1c697a66308a,0)/IPv6([::]:<->[::]:,0,0)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 06 1f / 03 0b 25 00 1c 69 7a 66 30 8a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0d 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
Boot000A* UEFI : USB :  USB DISK 2.0 PMAP : PART 1 : OS Bootloader	PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,GPT,ac25d109-653f-46d5-99c1-9890086ba449,0x3c65d8,0x4f7c)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 01 00 / 04 01 2a 00 02 00 00 00 d8 65 3c 00 00 00 00 00 7c 4f 00 00 00 00 00 00 09 d1 25 ac 3f 65 d5 46 99 c1 98 90 08 6b a4 49 02 02 / 7f ff 04 00
    data: 00 00 42 4f

someuser123 · February 13, 2023, 9:04am

I’m quite tempted to backup my two “/home” folders (Fedora & Ubuntu) and get Fedora 37 installed from scratch. However I’d like to give another try to restoration attempts if it is as easy as change something via Disks GUI. Have googled it for a bit and gave up on something like " … if you use LUKS and LVM" - which I have no idea what is about.

vekruse · February 13, 2023, 9:37am

Boot000A is referring to ESP locates in /dev/sdb2. That is the USB live boot device. You see that the UUID matches and

/dev/sdb2             ac25d109-653f-46d5-99c1-9890086ba449
Boot000A* UEFI : USB :  USB DISK 2.0 PMAP : PART 1 : OS Bootloader	PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,GPT,ac25d109-653f-46d5-99c1-9890086ba449,0x3c65d8,0x4f7c)0000424f

Boot0001 Is the fedora boot and you see the UUID matches. It will try to boot the file EFI\fedora\shimx64.efi, and that would normally be known as /boot/efi/EFI/fedora/shimx64.efi. You can check if that file exists.

/dev/nvme0n1p1        c1e3fdd4-5851-4fbc-aa7a-f0c4256af0d8
Boot0001* Fedora	HD(1,GPT,c1e3fdd4-5851-4fbc-aa7a-f0c4256af0d8,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)

The following entries refers to a disk unit which are not found on the system. You probably should delete those. The Windows entry is a duplicate.

Boot0000* Windows Boot Manager	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000096000100000010000000040000007fff0400
Boot0004* Windows Boot Manager	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000016070100000010000000040000007fff0400
Boot0007* ubuntu	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)

What happened to /dev/sda1, which looked like it could be another ESP file system?

Some UEFI implementations can do some weird things, and most of them are not very well documented. Mine, for example, seems to treat a USB connected device as CDROM, which is fine until you connect a real disk via USB and try to make it bootable. That doesn’t work in this case. It probably would work on most other systems.

someuser123 · February 13, 2023, 12:12pm

Thank you! /dev/sda1 holds Ubuntu 20 and I have a few hours while data is backing up to an old spare HDD to find a tool which would detect both systems installed (Fedora 36 & Ubuntu 20) and fix grub/uefi for me. Wish I knew about Boot-Repair-Disk while having operational Ubuntu. Whatever, Fedora 37 fresh install looks like the fastest option here.

vekruse · February 13, 2023, 3:25pm

If you go for a fresh install, I would suggest that you consider installing one of them in a virtual disk. One of the problems is that Ubuntu grub2 is not compatible with Fedora grub2. It can be done, but then it requires that you really know what you are doing and why. In some cases you can also use the systemd-nspawn facility. You can actually run an Ubuntu system using the Fedora kernel, but everything else is Ubuntu. See the man pages for systemd-nspawn for examples man systemd-nspawn.