Re: Boot issues after latest kernel update

Man2Dev <Man2Dev@xxxxxxxxx> · Sun, 07 Jul 2024 19:43:02 +0000

Hello
It seems to me one of the drives that is name by the UUID of `696850c4-f73d-47b5-9a9f-c2bbb003dc0b` in the `/etc/fstab` file is not being found. As such, it's failing to boot. It's fairly easy to fix, just comment it out for now and get into the system

-------- Original Message --------
On 7/7/24 20:52, Sbob  wrote:

    All;
    after the latest update (KDE - Fedora 40) I got dropped into
      emergency mode 3 times trying to boot, journalctl didnt really
      help
    I finally got the laptop to boot and my boot.log has these
      entries:

    [  OK  ] Finished modprobe@dm_mod.service - Load Kernel
          Module dm_mod.

        [  OK  ] Stopped systemd-vconsole-setup.service - Virtual
          Console Setup.

                Stopping systemd-vconsole-setup.service - Virtual
          Console Setup...

                Starting systemd-vconsole-setup.service - Virtual
          Console Setup...

        [ TIME ] Timed out
          waiting for device dev-disk-by\x2duuid-696850c4\x2df73d\x2d47b5\x2d9a9f\x2dc2bbb003dc0b.device - /

        dev/disk/by-uuid/696850c4-f73d-47b5-9a9f-c2bbb003dc0b.

        [DEPEND] Dependency
          failed for data.mount - /data.

        [DEPEND] Dependency
          failed for local-fs.target - Local File
          Systems.

        [DEPEND] Dependency
          failed for selinux-autorelabel-mark.service - Mark the
          need to relabel after reboot.

        [DEPEND] Dependency
          failed for systemd-fsck@dev-disk-by\x2duuid-696850c4\x2df73d\x2d47b5\x2d9a9f\x2dc2bbb003dc0b.serv

        ice - File
          System Check on
          /dev/disk/by-uuid/696850c4-f73d-47b5-9a9f-c2bbb003dc0b.

        [  OK  ] Stopped systemd-ask-password-wall.path - Forward
          Password Requests to Wall Directory Watch.

    [  OK  ] Finished systemd-user-sessions.service - Permit User
          Sessions.

        [  OK  ] Started atd.service - Deferred
          execution scheduler.

        [  OK  ] Started crond.service - Command
          Scheduler.

                Starting plymouth-quit-wait.service - Hold until
          boot process finishes up...

                Starting plymouth-quit.service - Terminate
          Plymouth Boot Screen...

        [  OK  ] Started virtvboxd.service - libvirt
          VirtualBox daemon.

        [  OK  ] Started virtlxcd.service - libvirt LXC
          daemon.

        [  OK  ] Started virtqemud.service - libvirt
          QEMU daemon.

        [FAILED] Failed to
          start plymouth-quit.service - Terminate
          Plymouth Boot Screen.

        See 'systemctl status plymouth-quit.service' for details.

    Should I be concerned?

    Thanks in advance

-- 
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue