I’ve attached an image below (from booting into recovery), but my Fedora 36 installation, after rebooting from Gnome Software’s “Reboot & Install” button, resulted in the system being unable to boot.
1st failure seems to be “Failed to mount boot-efi.mount - /boot/efi”
I’m interested in any potential fixes anyone could help with. Installation is encrypted.
I do not know that this is a gnome-software (packagekit) failure but I have seen several similar failures that all seem to have occurred after an update with gnome-software.
You can try booting to run level 3 by selecting your kernel on the grub menu and pressing the e key to edit the entry. Then find the line beginning with ‘linux’ and edit it, removing rhgb quiet and adding init 3. Ctrl + X should continue the boot which should get you to a login screen where you can log in as your regular user. Once logged in this way try ‘startx’ and it should bring up the desktop.
If that fails then we need more info from the text screen you should see.
I’ve chrooted via a netinstall disk and tried dracut --force after reading:
dracut-initqueue[558]: Warning: Not all disks have been found.
dracut-initqueue[558]: Warning: You might want to regenerate your initramfs.
I was now able to get to journalctl and read:
nvme nvme0: failed to set APST feature
nvme nvme1: failed to set APST feature
nvme nvme1: globally duplicate IDs for nsid 1
And then it tips into:
Warning: dracut-initqueue: starting timeout scripts
Any thoughts or advice appreciated.
Thanks, Jeff. Just seeing your comment now. I’m trying the init 3 replacement now.
Update: It looks like following your suggesting is still ending up with a repeating error at boot and dropping to dracut-emergency.service shell.
Two warnings:
Warning: /dev/disk/by-uuid/{string} does not exist
Warning: crypto LUKS UUID {different string} not found
This produced a /run/initramfs/rdsosreport.txt file and suggests saving it somehow, but with the limited sh-5.1# terminal (no scp or ssh) I’ll need to figure that out.
The first warnings in the rdosreport.txt are the following:
[ 129.358863] tower dracut-initqueue[562]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 129.359432] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/90-crypt.sh: "[ -e /dev/disk/by-id/dm-uuid-CRYPT-LUKS?-*1426dc5f84914369a1244f378fb486b8*-* ] || exit 1"
[ 129.360193] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fd0dcc266-7b68-49df-851d-4a969cfea450.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 129.360193] tower dracut-initqueue[562]: [ -e "/dev/disk/by-uuid/d0dcc266-7b68-49df-851d-4a969cfea450" ]
[ 129.360193] tower dracut-initqueue[562]: fi"
[ 129.363533] tower dracut-initqueue[562]: Warning: dracut-initqueue: starting timeout scripts
[ 129.883865] tower dracut-initqueue[562]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 129.884755] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/90-crypt.sh: "[ -e /dev/disk/by-id/dm-uuid-CRYPT-LUKS?-*1426dc5f84914369a1244f378fb486b8*-* ] || exit 1"
[ 129.885626] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fd0dcc266-7b68-49df-851d-4a969cfea450.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 129.885626] tower dracut-initqueue[562]: [ -e "/dev/disk/by-uuid/d0dcc266-7b68-49df-851d-4a969cfea450" ]
[ 129.885626] tower dracut-initqueue[562]: fi"
[ 129.888436] tower dracut-initqueue[562]: Warning: dracut-initqueue: starting timeout scripts
[ 130.406856] tower dracut-initqueue[562]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 130.407628] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/90-crypt.sh: "[ -e /dev/disk/by-id/dm-uuid-CRYPT-LUKS?-*1426dc5f84914369a1244f378fb486b8*-* ] || exit 1"
[ 130.408635] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fd0dcc266-7b68-49df-851d-4a969cfea450.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 130.408635] tower dracut-initqueue[562]: [ -e "/dev/disk/by-uuid/d0dcc266-7b68-49df-851d-4a969cfea450" ]
[ 130.408635] tower dracut-initqueue[562]: fi"
[ 130.411356] tower dracut-initqueue[562]: Warning: dracut-initqueue: starting timeout scripts
[ 130.929862] tower dracut-initqueue[562]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 130.930752] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/90-crypt.sh: "[ -e /dev/disk/by-id/dm-uuid-CRYPT-LUKS?-*1426dc5f84914369a1244f378fb486b8*-* ] || exit 1"
This repeats for like 300 lines, and eventually ends with:
[ 190.728066] tower dracut-initqueue[562]: Warning: dracut-initqueue: starting timeout scripts
[ 191.240855] tower dracut-initqueue[562]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 191.241790] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/90-crypt.sh: "[ -e /dev/disk/by-id/dm-uuid-CRYPT-LUKS?-*1426dc5f84914369a1244f378fb486b8*-* ] || exit 1"
[ 191.242968] tower dracut-initqueue[562]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fd0dcc266-7b68-49df-851d-4a969cfea450.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 191.242968] tower dracut-initqueue[562]: [ -e "/dev/disk/by-uuid/d0dcc266-7b68-49df-851d-4a969cfea450" ]
[ 191.242968] tower dracut-initqueue[562]: fi"
[ 191.246081] tower dracut-initqueue[562]: Warning: dracut-initqueue: starting timeout scripts
[ 191.246081] tower dracut-initqueue[562]: Warning: Could not boot.
[ 191.252775] tower systemd[1]: Starting dracut-emergency.service - Dracut Emergency Shell...
[ 191.265692] tower systemd[1]: Received SIGRTMIN+21 from PID 565 (plymouthd).
[ 191.275732] tower systemd[1]: Received SIGRTMIN+21 from PID 565 (plymouthd).
It’s worth noting that I’m never prompted for my disk decryption password when trying to boot normally, it just fails to the emergency shell. Using a live USB and going through troubleshooting mode (via server netboot) does find and prompt for decryption password and successfully chroot into the disk, so I’m not sure what the best steps here are at this point.
Looking for password-related things reveals the following:
[ 1.933308] tower systemd[1]: Started plymouth-start.service - Show Plymouth Boot Screen.
[ 1.933425] tower audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1.934015] tower systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of a failed condition check (ConditionPathExists=!/run/plymouth/pid).
[ 1.934080] tower systemd[1]: Started systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch.
[ 1.934111] tower systemd[1]: Reached target paths.target - Path Units.
Followed shortly by something I’d seen before:
[ 2.365281] tower kernel: nvme nvme0: failed to set APST feature (2)
[ 2.379244] tower kernel: nvme nvme1: failed to set APST feature (2)
Not sure if there’s a way to force the password ask, but maybe that would help.
That sounds like there is an issue with device id on those 2 devices.
You may want to check the disk uuid and the uuid of each partition on those 2 drives and find out if there is a conflict there.
While booted up try this command to see if there is any duplicated info shown.
$ lsblk --output MODEL,NAME,PARTTYPE,PARTUUID,SERIAL,MOUNTPOINT,TYPE,UUID,VENDOR,WWN -a
MODEL NAME PARTTYPE PARTUUID SERIAL MOUNTPOINT TYPE UUID VENDOR WWN
SanDi sda 191078 disk ATA 0x5001b448b842c616
├─sda1
│ c12a7328-f81f-11d2-ba4b-00a0c93ec93b f899df8e-0177-45ba-a145-8a342ab3f83b /boot/efi part EE19-DB5A 0x5001b448b842c616
├─sda2
│ 0fc63daf-8483-4772-8e79-3d69d8477de4 b9d9a34d-0f61-4939-ba7e-93d679b981cf /boot part bd615d70-0ff8-42b6-ab38-0a7429b9bb91 0x5001b448b842c616
└─sda3
e6d6d379-f507-44c2-a23c-238f2a3df928 65025311-1191-41d7-9de1-429990026ed4 part vpxzk7-tpzx-FEdH-wJzd-qZEQ-yEJ7-nuiPkc 0x5001b448b842c616
└─fedora-root
/ lvm 3468ef28-f391-4b94-811e-894daaa5b791