Need some help analysing why my Fedora 36 won’t boot anymore. I restored the partitions from a backup but no matter what I try, I can’t fix the issue. I need to analyze the cause.
Anyone willing to guide me through to get it working.
Thanks in advance
Tony
The Grub2 boot entry will need to be updated to the new partition id’s in order for it to boot it properly. You should try to boot up the system with a Fedora installation USB image, it does have a rescue mode in the troubleshooting sub-menu that may be able to rescue your system. But it would also be a way to mount your new drive to determine the partition ID’s required, such as the subvolume ID of your root file system.
Stephen
I restored the partitions to the same partitions they were backed up from. Shouldn’t partition ID be valid. There is no new drive in this case.
I don’t know what the cause of the problem is. Even after looking into log files, I don’t know what I’m looking for.
Sure should!
Does it even try to load the Grub2 boot menu?
The Grub2 menu loads and choose a kernel. Then it goes into emergency mode terminal.
If you can, try to get a F36 installation media (usb) and boot from it, then pick troubleshoot, then repair existing fedora system to see if it can recover your install. If it finds corrupted files, which I am thinking there are, it should re-install them.
The important UUID is the file system UUID. You will se these when running
lsblk -fp
The UUID for the root file system should match the one found in /boot/grub2/grub.cfg in the line reading root=UUID=. Then the UUID found in /etc/fstab should also match.
Seems ok to me
At this point you type in the root password, and then you can analyze the journal. The journalctl command takes a -p err ir -p warning to dispaly only the errors or the errors plus warnings respectively.
This will need you to set the root passwd which is not the default thing to do.
Here are the journal errors
Aug 26 81:42:37 localhost.localdomain kernel --Boot 5d99e2b88c1d4e2b8d165c819231d652 –
: kauditd_printk_skb: 79 callbacks suppressed
Aug 26 81:43:14 localhost.localdomain kernel: #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23
Aug 26 81:43:14 localhost.localdomain kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log. Aug 26 81:43:14 localhost.localdomain kernel: ata9.88: NCQ Send/Recv Log not supported Aug 26 01:43:14 localhost.localdomain kernel: ata6.88: NCQ Send/Recv Log not supported
Aug 26 81:43:14 localhost.localdomain kernel: ata18.88: NCQ Send/Recv Log not supported
Aug 26 81:43:14 localhost.localdomain kernel: ata9.88: NCQ Send/Recv Log not supported Aug 26 81:43:14 localhost.localdomain kernel: ata6.88: NCQ Send/Recv Log not supported
Aug 26 81:43:14 localhost.localdomain kernel: ata18.88: NCQ Send/Recv Log not supported Aug 26 81:43:14 localhost.localdomain systemd[1]: Failed to load BPF object: No such process
Aug 26 81:43:14 localhost.localdomain kernel: nume numel: missing or invalid SUBNON field.
not a multiple of preferred minimum block size (4096 bytes)
Aug 26 01:43:16 localhost.localdomain kernel: sd 13:0:0:0: [sdf] Optimal transfer size 33553928 bytes Aug 26 81:43:16 localhost.localdomain kernel: amdgpu 8880:04:00.0: amdgpu: PSP runtime database doesn’t exist
Aug 26 81:43:16 localhost.localdomain kernel: amdgpu 8888:8d:88.8: amdgpu: PSP runtime database doesn’t exist Aug 26 81:43:16 localhost.localdomain kernel: amdgpu: SRAT table not found Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to load BPF object: No such process
Aug 26 81:43:18 localhost.localdomain systemd-sysv-generator [9151: Sys service /etc/rc.d/init.d/livesys’ lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a
Aug 26 81:43:18 localhost.localdomain systemd-sysv-generator [9151: SysU service /etc/rc.d/init.d/livesys-late’ lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to incl Aug 26 81:43:18 localhost.localdomain zram generator::generator [917]: modprobe “zram” failed, ignoring: code exit status: 1
Aug 26 81:43:18 localhost.localdomain systemd[887]: /usr/lib/systemd/system-generators/zram-generator failed with exit status 1. Aug 26 81:43:18 localhost.localdomain kernel: kauditd_printk_skb: 88 callbacks suppressed
Aug 26 81:43:18 localhost.localdomain systemd[1]: systemd-modules-load.service: Failed with result ‘exit-code’. Aug 26 01:43:18 localhost.localdomain systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules.
Aug 26 81:43:18 localhost.localdomain systemd-modules-load [932]: Failed to look up module alias ‘msr’: Function not implemented
Aug 26 81:43:18 localhost.localdomain systemd-modules-load [932]: Failed to look up module alias ‘fuse’: Function not implemented
Aug 26 81:43:18 localhost.localdomain systemd-udevd1992]: sr8: Process ‘/usr/sbin/pktsetup -i -d 11:8’ failed with exit code 1. Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-atani-168.mount: Failed with result ‘exit-code’. Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-atani-168.mount Mount unit for atani, revision 168.
Aug 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-atani-169.mount: Failed with result ‘exit-code’. Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-atani-169.mount Mount unit for atani, revision 169. Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-bare-5.mount: Failed with result ‘exit-code’. Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-bare-5.mount - Mount unit for bare, revision 5.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-boxyx2dsvg-178.mount: Failed with result ‘exit-code’ Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-boxy\x2dsvg-178.mount - Mount unit for boxy-svg, revision 178. Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-core18-2667.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-core18-2667.mount Mount unit for core18, revision 2667.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-core18-2679.mount: Failed with result ‘exit-code’. Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-core18-2679.mount Mount unit for core18, revision 2679. Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-core28-1778.mount: Failed with result ‘exit-code’
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-core28-1778.mount Mount unit for core28, revision 1778. Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-core28-1822.mount: Failed with result ‘exit-code’. Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-core28-1822.mount - Mount unit for core28, revision 1822.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-core22-469.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-core22-469. mount Mount unit for core22, revision 469. Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-core22-584.mount: Failed with result ‘exit-code’. Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-core22-584.mount Mount unit for core22, revision 584.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-gnome\x2d3x2d28\x2d1884-145.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-gnome2d3\x2d28\x2d1884-145.mount Mount unit for gnome-3-28-1884, revision 145. Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-gnome2d3\x2d28\x2d1884-161.mount: Failed with result 'exit-code" Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1884-161.mount - Mount unit for gnome-3-28-1884, revision 161.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-gnome\x2d32d38x2d2884-119.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-gnome\x2d3\x2d38x2d2884-119.mount - Mount unit for gnome-3-38-2884, revision 119. Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-gtk2dcommon\x2dthemes-1519.mount: Failed with result ‘exit-code’. Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-gtk2dcommon\x2dthemes-1519.mount - Mount unit for gtk-common-themes, revision 1519.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-gtk2dcommon\x24themes-1535.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-gtkx2dcommon\x2dthemes-1535.mount Mount unit for gtk-common-themes, revision 1535.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-kdex2dframeworks2d5\x2dcore18-32.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-kde\x2dframeworks x2d5\x2dcore18-32.mount - Mount unit for kde-frameworks-5-core18, revision 32.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-kde2dframeworks\x2d5\x2dqtx2d5\x2d15\x2d3\x2dcore28-8.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-kdex2dframeworks\x2d5\x2dqtx2d5\x2d15\x2d3\x2dcore28-8.mount - Mount unit for kde-frameworks-5-qt-5-15-3-core28, revision 8.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-kdex2dframeworks\x2d5\x2dqtx2d5\x2d15\x2dcore28-14.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-kde2dframeworks\x2d5\x2dqtx2d5\x2d15\x2dcore28-14.mount - Mount unit for kde-frameworks-5-qt-5-15-core28, revision 14.
Aug 26 81:43:18 localhost.localdomain systemd[1]: var-lib-snapd-snap-nmap-2864.mount: Failed with result ‘exit-code’.
Aug 26 81:43:18 localhost.localdomain systemd[1]: Failed to mount var-lib-snapd-snap-nmap-2864.mount Mount unit for nmap, revision 2864.
Anyone
Hello @tlc-at-home ,
It almost seems like a hard drive failing to me.
Hi Stephen
No, all ssd are working well. It is a multi boot system so other OSs wouldn’t work if the ssd was broken. What else can I investigate?
Okay, so have you tried to boot using an installation media and then mount your device in a temporary directory to do some filesystem work?
[Edit] I am meaning a Fedora installation media, where you select troubleshoot then go to a terminal and create a temp dir and mount your fedora partition there, you could even chroot into it I think.
