After dnf update, stuck on grub prompt | F40 | Dell XPS 13

geoff1188 · June 16, 2024, 11:06pm

Hi everyone,

Thanks in advance for all you help, and at least, for complete reading of my post

Sorry for double post, I’m trying to get more help from the community, by translating my post, initially in French here:

After a dnf update in Fedora Workstation 40 on my Dell XPS 13 Laptop (L322X model, year 2013), after reboot, I got stuck on this kind of screen, described by a member of the community here:

I tried to follow this quick doc:

But no success. Except a little progress of my problem, the screen doesn’t said anymore that “the root account is locked”, but the prompt was not usable at all, was freezing, or lag a lot when typing. I tried to enter the root password that I just reset with the quick doc, but the password was not recognized and keep continue to ask for password, by infinite…

Before having this issue, I create a live USB of Fedora Workstation 40. So, with the live usb, I tried to follow this quick doc:

Not sure I did well, but doesn’t solve my problem. To precise, I’m using LVM file system.

Then, I tried this:

Now, When I boot the laptop, boot sequence stop and get stuck on grub prompt:

Then, keep searching online, on fedora discussion, and also other website, like reddit, and others like unix stack exchange.

I got lost, hours of research online, on many website

I feel lonely, so I decide to create a post here. I’m quiet a beginner on Fedora, I used to be a power user, but not anymore I hope to not create a double post, a well known issue already solved

Here is the result of the command journalctl /dev/sda on live USB:

Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601 conventional PCI endpoint
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 0 [io  0x2098-0x209f]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 1 [io  0x20bc-0x20bf]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 2 [io  0x2090-0x2097]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 3 [io  0x20b8-0x20bb]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 4 [io  0x2060-0x207f]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 5 [mem 0xd0518000-0xd05187ff]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: PME# supported from D3hot
Jun 03 01:18:05 fedora kernel: ahci 0000:00:1f.2: version 3.0
Jun 03 01:18:05 fedora kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x1 impl SATA mode
Jun 03 01:18:05 fedora kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst 
Jun 03 01:18:05 fedora kernel: scsi host0: ahci
Jun 03 01:18:05 fedora kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD PM83 3D1Q PQ: 0 ANSI: 5
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Write Protect is off
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601 conventional PCI endpoint
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 0 [io  0x2098-0x209f]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 1 [io  0x20bc-0x20bf]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 2 [io  0x2090-0x2097]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 3 [io  0x20b8-0x20bb]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 4 [io  0x2060-0x207f]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: BAR 5 [mem 0xd0518000-0xd05187ff]
Jun 03 01:18:05 fedora kernel: pci 0000:00:1f.2: PME# supported from D3hot
Jun 03 01:18:05 fedora kernel: ahci 0000:00:1f.2: version 3.0
Jun 03 01:18:05 fedora kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x1 impl SATA mode
Jun 03 01:18:05 fedora kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst 
Jun 03 01:18:05 fedora kernel: scsi host0: ahci
Jun 03 01:18:05 fedora kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD PM83 3D1Q PQ: 0 ANSI: 5
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Write Protect is off
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
Jun 03 01:18:05 fedora kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jun 03 06:18:17 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 03 06:18:17 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 03 06:59:30 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 03 06:59:30 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 03 07:47:35 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 03 07:47:35 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 03 14:20:20 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 03 14:20:20 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 03 15:24:27 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 03 15:24:27 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 03 17:43:16 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 03 17:43:16 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 04 01:44:54 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 04 01:44:54 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 04 06:25:07 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 04 06:25:07 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 04 07:14:59 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 04 07:14:59 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 04 15:13:50 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 04 15:13:50 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 04 16:41:53 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 04 16:41:53 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 05 12:58:06 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 05 12:58:06 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 06 03:44:21 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 06 03:44:21 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 06 05:59:56 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 06 05:59:56 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 06 06:33:02 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 06 06:33:02 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 06 06:33:29 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 06 06:33:29 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 06 09:52:56 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 06 09:52:56 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 07 07:12:14 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 07 07:12:14 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 07 16:45:39 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 07 16:45:39 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 08 03:49:35 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 08 03:49:35 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 08 07:49:00 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 08 07:49:00 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 09 06:58:29 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 09 06:58:29 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 09 09:18:31 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 09 09:18:31 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 09 11:03:27 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 09 11:03:27 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 09 16:38:42 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 09 16:38:42 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 09 17:15:19 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 09 17:15:19 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 10 08:11:29 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 10 08:11:29 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 10 15:40:38 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 10 15:40:38 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 10 16:00:45 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 10 16:00:45 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 11 00:46:09 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 11 00:46:09 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 11 01:36:32 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 11 01:36:32 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 11 09:54:20 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 11 09:54:20 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 11 11:31:55 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 11 11:31:55 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 11 16:08:21 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 11 16:08:21 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 12 10:14:48 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 12 10:14:48 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 12 12:18:03 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 12 12:18:03 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 12 16:53:31 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 12 16:53:31 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 13 08:02:40 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 13 08:02:40 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 13 17:29:11 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 13 17:29:11 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 14 01:36:40 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 14 01:36:40 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 14 09:56:15 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 14 09:56:15 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 14 12:26:51 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 14 12:26:51 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 14 13:39:35 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 14 13:39:35 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 14 16:56:25 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 14 16:56:25 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 15 08:31:30 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 15 08:31:30 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 16 05:34:01 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 16 05:34:01 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 16 15:39:11 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 16 15:39:11 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk
Jun 16 19:08:09 localhost-live kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 16 19:08:09 localhost-live kernel: sd 0:0:0:0: [sda] Starting disk

Here is the result of lsblk -f -p

NAME                    FSTYPE          FSVER            LABEL                  UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
/dev/loop0              squashfs        4.0                                                                                           
/dev/loop1              ext4            1.0              Anaconda               57b2da08-9667-4695-9f1f-13d099a97592                  
├─/dev/mapper/live-rw   ext4            1.0              Anaconda               57b2da08-9667-4695-9f1f-13d099a97592      1.1G    86% /
└─/dev/mapper/live-base ext4            1.0              Anaconda               57b2da08-9667-4695-9f1f-13d099a97592                  
/dev/loop2              DM_snapshot_cow                                                                                               
└─/dev/mapper/live-rw   ext4            1.0              Anaconda               57b2da08-9667-4695-9f1f-13d099a97592      1.1G    86% /
/dev/sda                                                                                                                              
├─/dev/sda1             ext4            1.0                                     e0e0d1f2-36c9-49ee-9bac-1b375c690d25                  
└─/dev/sda2             LVM2_member     LVM2 001                                RXQbh7-kAtP-lkc4-DCzS-I1Iz-4ziM-ZKQF9f                
/dev/sdb                iso9660         Joliet Extension Fedora-WS-Live-40-1-14 2024-04-14-23-09-56-00                                
├─/dev/sdb1             iso9660         Joliet Extension Fedora-WS-Live-40-1-14 2024-04-14-23-09-56-00                       0   100% /run/initramfs/live
├─/dev/sdb2             vfat            FAT16            ANACONDA               23EA-7494                                             
└─/dev/sdb3                                                                                                                           
/dev/sdc                                                                                                                              
└─/dev/sdc1             vfat            FAT32            CLEUSB16GO             7A49-EA70                               355.8M    98% /run/media/liveuser/CLEUSB16GO
/dev/zram0                                                                                                                            [SWAP]

mpphill2 · June 17, 2024, 2:59am

There must be something going on, I got some sort of shim error and came here to see if anyone else experienced anything. Aside from going from 6.8.11 to the 6.9.4 kernel it isn’t a massive upgrade, dav1d and some other package. I’m assuming it is something about the new kernel, I’ll try to get the picture of my error.

mpphill2 · June 17, 2024, 3:11am

barryascott · June 17, 2024, 2:03pm

From the error in the image it looks like you have a issue with secure boot and keys.

You could turn off secure boot in the BIOS and see if you can then boot up.

I wonder if the shim in /boot is not the correct version?

robtheanimoo · June 17, 2024, 4:10pm

I can confirm that latest update on Silverblue also borks up the grub booting. Previous kernel version 6.8.11-300.fc40.x86_64 boots completely fine.

PS: I can also confirm that disabling secure boot in UEFI makes latest update to kernel 6.9.4 bootable again.

mpphill2 · June 19, 2024, 2:43pm

Yep, I finally got around to testing and disabling secure boot, it got to the LUKS login. It’s probably fine but it didn’t sit right with me, so I powered off and turned secure boot back on. Will wait for the fix.

geoff1188 · June 25, 2024, 12:03am

Hi, there’s no link with secure boot for me, I’m on legacy mode, I’m using BIOS mode. When I type this command line:

$ [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS

It returns BIOS.

So, after several attempt, and understanding the use of chroot, explained in this doc:

I follow this doc to try to repair my bootloader:

My partition is not encrypted by LUKS, and I’m using LVM2 filesystem. So I follow the steps of the doc for LVM:

root@localhost-live:/home/liveuser# vgscan
  Found volume group "fedora_localhost-live" using metadata type lvm2

oot@localhost-live:/home/liveuser# vgchange -ay fedora_localhost-live
  3 logical volume(s) in volume group "fedora_localhost-live" now active
root@localhost-live:/home/liveuser# lvs
  LV   VG                    Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  home fedora_localhost-live -wi-a----- 160.00g                                                    
  root fedora_localhost-live -wi-a-----  70.00g                                                    
  swap fedora_localhost-live -wi-a-----  <7.47g

So I follow all the next steps described in the doc, until the chroot. I did the grub2-install, grub2-mkconfig, and the I finally sync && exit then reboot.

But still stucks at the grub prompt…

So I follow the next paragraph of the doc:

I load the necessary module for LVM filesystem.

“ls” command return me:

At the step 4.Probe each partition of the drive and locate your vmlinuz and initramfs files.

The outcome of the command:

ls (hd0,1)

or

ls (hd0,msdos1)

or

ls (hd0, msdos2)

does’t return any list of files.

I finally found my boot partition is (hd0,msdos1), so I follow the next steps assumed it’s that one, but no idea why. The only things that can help me to guess is the good one, when I type linux / and enter TAB, the vmlinuz_xxx appears, on the step 2 of this doc:

But at the beginning, I believe in LVM filesystems, the boot partition is the fedora_localhost–live-root logical volume.

Finally, I enter boot, the system finally run whith lot of line precede by “OK”, and after a lot of line of loading message, I arrive on a prompt that ask me the root password and explain me that I’m in emergency mode. But I can’t type anything on that prompt, it’s unusable…

Sorry if I’m not clear, but any expert help would be very nice, but I know guys did what you can, and your time is precious. Thank’s in advance for any advice.

Otherwise, I would mount my file system home, copy to an external drive, then go for a fresh install… But don’t really know what happened…

The last transaction ID of the dnf update that I found in my dnf history is 263:

root@localhost-live:/# dnf history
ID     | Command line                                                                                                                                                                            | Date and time    | Action(s)      | Altered
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   264 | -y install --nogpgcheck --disablerepo=* /tmp/akmods.D4MjKSoe/results/kmod-VirtualBox-6.8.10-300.fc40.x86_64-7.0.18-1.fc40.x86_64.rpm                                                    | 2024-05-28 14:38 | Install        |    1   
   263 | update                                                                                                                                                                                  | 2024-05-28 14:32 | C, E, I, U     |  190 EE

root@localhost-live:/# dnf history info 263
Transaction ID : 263
Begin time     : Tue 28 May 2024 02:32:01 PM CEST
Begin rpmdb    : 03bacc1fbe846e273d3ec596bcf01647600d7e7e53543242a4f27109d549d0e4
End time       : Tue 28 May 2024 02:38:42 PM CEST (6 minutes)
End rpmdb      : 06eaa12394d3045ebed1ec3b69a49233e3c97e50e11fb6070848ceb215659022
User           : Geoff <geoff>
Return-Code    : Success
Releasever     : 40
Command Line   : update
Comment        : 
Packages Altered:
    Install       dotconf-1.3-35.fc40.x86_64                                   @fedora
    Install       espeak-ng-1.51.1-8.fc40.x86_64                               @fedora
    Install       highway-1.1.0-1.fc40.i686                                    @fedora
    Install       libjxl-1:0.8.2-6.fc40.i686                                   @fedora
    Install       pcaudiolib-1.1-14.fc40.x86_64                                @fedora
    Install       kernel-6.8.10-300.fc40.x86_64                                @updates
    Install       kernel-core-6.8.10-300.fc40.x86_64                           @updates
    Install       kernel-devel-6.8.10-300.fc40.x86_64                          @updates
    Install       kernel-modules-6.8.10-300.fc40.x86_64                        @updates
    Install       kernel-modules-core-6.8.10-300.fc40.x86_64                   @updates
    Install       kernel-modules-extra-6.8.10-300.fc40.x86_64                  @updates
    Install       speech-dispatcher-0.11.5-5.fc40.x86_64                       @updates
    Install       speech-dispatcher-espeak-ng-0.11.5-5.fc40.x86_64             @updates

geoff1188 · July 11, 2024, 11:14am

Hi everyone,

After days of silence, trying to help myself searching and on website, social network and other community, I finally found out and solve part of my issue following this quick doc:

But I’m french, and I better appreciate working with this doc:
https://doc.fedora-fr.org/wiki/GRUB2_:_Les_bases_pour_Fedora#GRUB2_sur_un_système_BIOS

Now I’m facing a new issue, I can see again de GRUB2 bootloader menu, I boot the first default line, and I’m stuck here:

I tried resetting the root password, in rescue mode, following this doc:

Without success

gnwiii · July 11, 2024, 12:21pm

You can’t fix an unbootable system, and “secure boot” is mostly hype – it only blocks a few type of attacks. I assume you disabled it to attempt the grub repair. Does the grun menu offer several choices of kernels to boot?

If so, can you boot an older kernel from the grub menu? If not, can you boot a F40 Live USB system? You can use chroot from the Live USB system to repair the installation, but it is important to understand what broke.

The installer does try to preserve and existing /home, but you should make a backup of /home. If the filesystem is OK you can make a backup using the Live USB.

Start with checking the “Health” of your system disk with Gnome Disks, and also verify that the filesystem has free space.

It could be helpful to provide the output from running inxi -Fzxx (you probably need to install it with dnf install inxi) in a terminal and posting the output as pre-formatted text (using the </> button from the top line of the text entry panel).

geoff1188 · July 12, 2024, 6:54pm

Hi @gnwiii,

thanks for your reply, and for your time.

Yes, I’m currently saving all my /home on a external usb hard drive, but usually troubles never come alone , and I’m facing some input / output error while copying my data on it. It’s a Samsung M3 portable hard drive, with NTFS file system (I was windows user before, long time ago). I can’t figured out what’s going on yet.

So, as far as I found online, not sure checking NTFS file systems health with disks or other command line tools on fedora is appropriate. Most of people said go on a Windows computer and run a chkdsk on your external hard drive. But I don’t have one. So, I found a linux live distro called ALT Linux, popular in “rescue” live distribution. I still have to test it, create a bootable usb stick. There’s probably lot of tools to check my disk.
Ntfsfix and smartctl command line tools were not helpful, in my case.

I “chroot” my system, cause I’m using a fedora 40 live usb stick to boot my laptop, as explained in this quick doc:

I hope I did well. So here’s the result of the command:

root@localhost-live:/# inxi -Fzxx
12System:
  12Kernel 6.8.5-301.fc40.x86_64 12arch x86_64 12bits 64 12compiler gcc 12v 2.41-34.fc40
  12Desktop GNOME 12v 46.2 12tk GTK 12v 3.24.42 12wm gnome-shell 12dm GDM 12Distro Fedora Linux 40
    (Workstation Edition)
12Machine:
  12Type Portable 12System Dell 12product XPS L322X 12v N/A 12serial <filter> 12Chassis 12type 8 12v 0.1
    12serial <filter>
  12Mobo Dell 12model 0WW7PG 12v A00 12serial <filter> 12part-nu XPS L322X 12UEFI-[Legacy] Dell 12v A10
    12date 08/28/2013
12Battery:
  12ID-1 BAT0 12charge 23.6 Wh (100.0%) 12condition 23.6/47.3 Wh (49.8%) 12volts 8.3 12min 7.4
    12model SIMPLO Dell 12serial <filter> 12status full
12CPU:
  12Info dual core 12model Intel Core i5-3337U 12bits 64 12type MT MCP 12arch Ivy Bridge 12rev 9 12cache
    12L1 128 KiB 12L2 512 KiB 12L3 3 MiB
  12Speed (MHz) 12avg 1256 12high 1593 12min/max 800/2700 12cores 121 1348 122 800 123 1285 124 1593 12bogomips 14365
  12Flags avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
12Graphics:
  12Device-1 Intel 3rd Gen Core processor Graphics 12vendor Dell 12driver i915 12v kernel 12arch Gen-7 12ports
    12active DP-1,eDP-1 12empty HDMI-A-1,VGA-1 12bus-ID 00:02.0 12chip-ID 8086:0166
  12Device-2 Microdia 1.3 MPixel Integrated Webcam 12driver uvcvideo 12type USB 12rev 2.0 12speed 480 Mb/s
    12lanes 1 12bus-ID 4-1.5:3 12chip-ID 0c45:644d
  12Display wayland 12server X.org 12v 1.20.14 12with Xwayland 12v 23.2.6 12compositor gnome-shell 12driver
    12gpu i915 12display-ID 0
  12Monitor-1 DP-1 12model Idek Iiyama PLE2483H-DP 12res 1920x1080 12dpi 92 12diag 609mm (24")
  12Monitor-2 eDP-1 12model ChiMei InnoLux 0x1345 12res 1920x1080 12dpi 166 12diag 337mm (13.3")
  12API OpenGL 12Message GL data unavailable for root.
  12API Vulkan 12Message No Vulkan data available.
  12API EGL 12Message EGL data requires eglinfo. Check --recommends.
12Audio:
  12Device-1 Intel 7 Series/C216 Family High Definition Audio 12vendor Dell 12driver snd_hda_intel
    12v kernel 12bus-ID 00:1b.0 12chip-ID 8086:1e20
  12API ALSA 12v k6.8.5-301.fc40.x86_64 12status kernel-api
  12Server-1 PipeWire 12v 1.0.7 12status n/a (root, process) 12with 121 pipewire-pulse 12status active
    122 wireplumber 12status active 123 pipewire-alsa 12type plugin 124 pw-jack 12type plugin
12Network:
  12Device-1 Intel Centrino Advanced-N 6235 12driver iwlwifi 12v kernel 12pcie 12speed 2.5 GT/s 12lanes 1
    12bus-ID 01:00.0 12chip-ID 8086:088e
  12IF wlp1s0 12state down 12mac <filter>
  12Device-2 Realtek RTL8153 Gigabit Ethernet Adapter 12driver r8152 12type USB 12rev 3.0 12speed 5 Gb/s
    12lanes 1 12bus-ID 3-1.4:123 12chip-ID 0bda:8153
  12IF enp0s20u1u4 12state down 12mac <filter>
  12IF-ID-1 enp0s20u1u1 12state unknown 12speed -1 12duplex half 12mac <filter>
12Bluetooth:
  12Device-1 Huawei ELE-L29 12driver rndis_host 12v kernel 12type USB 12rev 2.1 12speed 480 Mb/s 12lanes 1
    12bus-ID 1-1.1:53 12chip-ID 12d1:108a
  12Device-2 Intel Centrino Bluetooth Wireless Transceiver 12driver btusb 12v 0.8 12type USB 12rev 2.0
    12speed 12 Mb/s 12lanes 1 12bus-ID 2-1.5:3 12chip-ID 8087:07da
  12Report 12ID hci0 12rfk-id 9 12state down 12bt-service N/A 12rfk-block 12hardware no 12software yes
    12address <filter> 12bt-v 4.0 12lmp-v 6
12Drives:
  12Local Storage 12total 256.65 GiB 12used 30.75 GiB (12.0%)
  12ID-1 /dev/sda 12vendor Samsung 12model SSD PM830 mSATA 256GB 12size 238.47 GiB 12speed 6.0 Gb/s
    12serial <filter>
  12ID-2 /dev/sdb 12vendor Kingston 12model DataTravelerMini 12size 3.73 GiB 12type USB 12rev 2.0
    12spd 480 Mb/s 12lanes 1 12serial <filter>
  12ID-3 /dev/sdc 12vendor Kingston 12model DataTraveler 3.0 12size 14.44 GiB 12type USB 12rev 3.1 12spd 5 Gb/s
    12lanes 1 12serial <filter>
12Partition:
  12ID-1 / 12size 68.35 GiB 12used 30.75 GiB (45.0%) 12fs ext4 12dev /dev/dm-4
    12mapped fedora_localhost--live-root
12Swap:
  12ID-1 swap-1 12type zram 12size 7.3 GiB 12used 8.3 MiB (0.1%) 12priority 100 12dev /dev/zram0
12Sensors:
  12System Temperatures 12cpu 72.0 C 12mobo 54.0 C
  12Fan Speeds (rpm) N/A
12Info:
  12Memory 12total 8 GiB 12note est. 12available 7.3 GiB 12used 5.58 GiB (76.4%) 12igpu 64 MiB
  12Processes 308 12Power 12uptime 1d 5h 14m 12wakeups 8 12Init systemd 12v 255 12default graphical
  12Packages 12pm flatpak 12pkgs 12 12Compilers 12clang 18.1.6 12gcc 14.1.1 12Client shell wrapper
    12v 5.2.26-release 12inxi 3.3.34

gnwiii · July 12, 2024, 7:24pm

You need to determine if the error is a hardware problem with the system drive or the backup drive or an incompatibility. I worked in an organization that has Windows as the “corporate standard” in a group that used mission critical software only available on linux and macOS. There were often problems transferring data to NTFS filesystems. NTFS permissions do not map cleanly to linux permissions, some systems had limits on the length of paths, and mishandling of special characters. For a backup on NTFS you should consider an archive format. Borg Backup is reported to work when saving data to NTFS and has a simpified front-end called Pika with a Fedora flatpak. Note that Pika is not intended for system recovery – you can retrieve indiviual files with a GUI tool, so you would need to use Borg tools if you end up needing to restore the backup. I would want to do a test/practice run with a throwaway user login.

You should look for details of the “input/outout” error using journalctl. Gnome Disks has some “drive health” options that may tell you if a drive is failing.

geoff1188 · July 12, 2024, 10:59pm

What you explained look similar to what that talk in that post, but I’m french, my english is not perfect, and it’s very late in France now, so maybe I misunderstood:

In Gnome Disks, I picked “Check filesystem…” option, and It return me:
Screenshot from 2024-07-12 18-56-25

The only interesting thing I found is this, with journalctl:

root@localhost-live:/# journalctl -p 0..3 -x -b -5
mai 31 19:05:18 localhost.localdomain systemd-vconsole-setup[525]: /usr/bin/setfont failed wi>
mai 31 19:05:18 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:23 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:27 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:31 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:35 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:39 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:43 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:47 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:51 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:55 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:05:59 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:03 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:07 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:10 localhost.localdomain systemd[1]: Timed out waiting for device dev-sdc1.devic>
░░ Subject: A start job for unit dev-sdc1.device has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit dev-sdc1.device has finished with a failure.
░░ 
░░ The job identifier is 174 and the job result is timeout.
mai 31 19:06:11 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:15 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:19 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:23 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:27 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:31 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:36 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:40 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:44 localhost.localdomain kernel: usb usb3-port2: Cannot enable. Maybe the USB ca>
mai 31 19:06:47 localhost.localdomain kernel: watchdog: watchdog0: watchdog did not stop!

You may said to use command line tool dmesg to troubleshoot hardware issue.
Here is the output, after plug my USB external hard drive:

[35784.626448] usb 3-1: new SuperSpeed USB device number 38 using xhci_hcd
[35784.653666] usb 3-1: New USB device found, idVendor=0bda, idProduct=0411, bcdDevice= 1.33
[35784.653680] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[35784.653686] usb 3-1: Product: 4-Port USB 3.0 Hub
[35784.653691] usb 3-1: Manufacturer: Generic
[35784.663408] hub 3-1:1.0: USB hub found
[35784.664713] hub 3-1:1.0: 4 ports detected
[35784.960717] usb 3-1.2: new SuperSpeed USB device number 39 using xhci_hcd
[35784.973696] usb 3-1.2: New USB device found, idVendor=04e8, idProduct=61b6, bcdDevice=13.01
[35784.973706] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[35784.973709] usb 3-1.2: Product: Samsung M3 Portable
[35784.973711] usb 3-1.2: Manufacturer: Samsung M3 Portable
[35784.973713] usb 3-1.2: SerialNumber: 91BC7DEC05000079
[35784.976055] usb-storage 3-1.2:1.0: USB Mass Storage device detected
[35784.976369] scsi host7: usb-storage 3-1.2:1.0
[35786.032044] scsi 7:0:0:0: Direct-Access     Samsung  M3 Portable      1301 PQ: 0 ANSI: 6
[35786.033179] sd 7:0:0:0: Attached scsi generic sg2 type 0
[35786.035867] sd 7:0:0:0: [sdc] Spinning up disk...
[35787.054644] .ready
[35789.853873] sd 7:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[35789.854394] sd 7:0:0:0: [sdc] Write Protect is off
[35789.854405] sd 7:0:0:0: [sdc] Mode Sense: 33 00 00 08
[35789.854897] sd 7:0:0:0: [sdc] No Caching mode page found
[35789.854909] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[35789.859357]  sdc: sdc1
[35789.859521] sd 7:0:0:0: [sdc] Attached SCSI disk

Here is some smartctl output:

root@localhost-live:/# smartctl -i /dev/sdc
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.5-301.fc40.x86_64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Samsung SpinPoint M8U (USB)
Device Model:     ST1000LM025 HN-M101ABB
Serial Number:    E7083G94AD730Y
LU WWN Device Id: 0 000000 000000000
Firmware Version: 2BA30003
User Capacity:    1 000 204 886 016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database 7.3/5528
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Jul 13 00:13:08 2024 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

root@localhost-live:/# smartctl -s on -o on -S on /dev/sdc
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.5-301.fc40.x86_64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
SMART Attribute Autosave Enabled.
SMART Automatic Offline Testing Enabled every four hours.

root@localhost-live:/# smartctl -H /dev/sdc
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.5-301.fc40.x86_64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

When I’m browsing in a directory of the external drive:

root@localhost-live:/home/liveuser# ls -lah /run/media/liveuser/SAMSUNG/ADMINISTRATIF/Santé
ls: cannot access '/run/media/liveuser/SAMSUNG/ADMINISTRATIF/Santé/DRUOT AMELIE A   VACCIN   FAIT A JOUR   24  10 2020.pdf': Input/output error
ls: cannot access '/run/media/liveuser/SAMSUNG/ADMINISTRATIF/Santé/DRUOT AMELIE CERTIF   VACCIN   FAIT A JOUR  2023    FEV.pdf': Input/output error

Screenshot from 2024-07-12 18-53-07

All of the test (dmesg, smartctl) have been made also on the system disk.

But I’m off-topic now. I should have to rename my post

gnwiii · July 19, 2024, 11:42am

You have posted partial lines (truncated at the >. When posting journalctl output, use journalctl --no-hostname ... | cat. We don’t need to see the hostname, and the |cat wraps long lines.

The last part should probably be Maybe the USB cable is bad. Alternatives explanations are a chip damaged by static electricity or a poor connection due to dirt or corrosion or old age.

USB connectors do wear out and become unreliable with long-term use. Sometimes a dust collects in USB ports and it can take a few plug and unplug cycles to get a reliable connection, but you are better off checking for corrosion (green scum) and carefully cleaning the ports and connectors. Not all external USB drives support S.M.A.R.T drive health. Some vendors have their own drive health software that they ask you to use before returning a potentially failed drive.

geoff1188 · July 27, 2024, 10:56pm

Hi,

Sorry for late reply, thanks a lot for your complete and detailed response. I will check that tutorial you supply me with a link, apply it on my USB port of the external drive.

But the initial issue, the message I got, on a black background, when I boot my laptop : “You are in emergengy mode, after logging in, type “journalctl -xb” to view system logs… etc.” is still unsolved…

In the past few days, I did’t get enough time to investigate on it, I was very busy with others things. I’m losing patience and tired to search… I’m using another laptop to work and treat daily emergency things. But it’s frustrating to don’t know what’s going on.

Thanks again for your time.

gnwiii · July 28, 2024, 12:08am

journalctl -b <N> allows you to view the entries of previous boots: N=-1, N=-2, etc. You can get a list of all the boots and find the number of the one that failed. All your journalctl lines have added 12 before many terms, making them hard to read.

Try connecting the drive directly without the hub. To backup /home to NTFS you should create an archive file so the linux permissions are preserved. NTFS may not allow names that are OK in Linux. Gnome disks has an option to create a disk image, so if you have space, you could try that for the whole system. If you don’t have space, you need to create an archive that preserves metadata. See: Linux tar preserving ACLS and SElinux contexts – something like:

tar --selinux --acls --xattrs --xz -cvf <target_directory>/home.tar.xz /home

geoff1188 · August 1, 2024, 4:37pm

Hi,

I found a lot of boot number which have failed, from number 8 to number 25. Cause I do not remember the exact date and time I reboot my laptop, after the dnf update, and get the error at the boot… The only things I’m sure is the boot stuck issue occured during the last days of May.

Here is a sample:

root@localhost-live:/# journalctl --no-hostname -p 0..3 -x -b -8 | cat
May 31 19:05:18 systemd-vconsole-setup[525]: /usr/bin/setfont failed with exit status 71.
May 31 19:05:18 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:23 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:27 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:31 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:35 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:39 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:43 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:47 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:51 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:55 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:05:59 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:03 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:07 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:10 systemd[1]: Timed out waiting for device dev-sdc1.device - /dev/sdc1.
░░ Subject: A start job for unit dev-sdc1.device has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit dev-sdc1.device has finished with a failure.
░░ 
░░ The job identifier is 174 and the job result is timeout.
May 31 19:06:11 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:15 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:19 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:23 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:27 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:31 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:36 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:40 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:44 kernel: usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
May 31 19:06:47 kernel: watchdog: watchdog0: watchdog did not stop!

The boot number 10 gave me lot of issue logged. The next 12 and 13 show fue errors too.
I found a very big log in the boot number 25. The result of the command gave me a huge amount of lines.

I exported it to a file. How can I send it to you? I didn’t find file attachment on the forum…

Thanks for the tips. I solved my input/output errrors on the drive running CHKDSK utility on a Windows 10 computer.

geoff1188 · August 1, 2024, 5:30pm

I finally found a service to send you the journalctl log for the boot number 25:

Please tell me if it’s useful for you or not. Many thanks.

hamrheadcorvette · August 1, 2024, 5:37pm

Fedora ships fpaste which is used specifically for this usecase.

Your command would be something like

journalctl --no-hostname -p 0..3 -x -b -8 | fpaste --raw-url

You can then paste the url here so we can see the output.

geoff1188 · August 2, 2024, 9:31pm

Hi,

thank you for the tip.

Here it is:
https://paste.centos.org/view/raw/65afffe4

Not sure it’s gonna be helpful for troubleshooting guys. I’m now pretty lost technically, I reach a limit when I read those logs…

Otherwise, I’ve got a lot others boot with issues logged by journalctl. But which one is the good one?

I would like to rename the title of my post, cause my issue change during my progress in troubleshooting. It it possible? Would be better to rename like “After dnf update on Fedora 40 WS, boot stuck in emergency mode, root account is locked”

Good luck

hamrheadcorvette · August 2, 2024, 10:07pm

I just got here to help you with the paste really. . . It looks like you have been having issues for over a month

So my questions are:

Have your issues changed over time? ( I would need to read the whole thread to understand what is actually happening )
What is the issue you are currently dealing with ?

Topic		Replies	Views
Après mise à jour dnf updates sous Fedora 40, ultrabook Dell XPS 13 démarre sur le prompt Grub Ask in Other Languages notebook , boot , grub , dell , f40 , français	0	105	June 16, 2024
Stuck at grub prompt after updates + LUKS \| Fedora 39 \| Dual Boot Ask Fedora dual-boot , windows , f39	12	251	July 3, 2024
Failure to boot after update today Ask Fedora f37 , f40	4	241	June 1, 2024
Boot Failure Ask Fedora shutdown , dnf , f40	22	372	June 24, 2024
Cant boot after update Ask Fedora f36	4	348	February 18, 2023

Related Topics