Re: failed to mount /boot/efi Help!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The modules issue is your root= line is pointing to the wrong root device.

I am going to guess that all of your boot's have root= that are the
same when the f32 ones should be pointing at the f32 root and the f34
ones should be pointing at f34.

On the ones that don't boot it will need to be changed to the other
root device (ie /).

On Sun, Jul 18, 2021 at 2:24 AM Patrick Dupre <pdupre@xxxxxxx> wrote:
>
> Hello,
>
> It is now 2 days that I am stuck with this issue.
> I search on internet, but I did not find clear solutions which I could trust.
>
> Here is the fstab
> UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 /                       ext4    defaults        1 1
> UUID=B2EF-0CE4          /boot/efi               vfat    umask=0077,shortname=winnt,nofail 0 2
>
> /boot/efi is mounted properly with fc32.
>
> Is it an issue with the modules ?
>
>
> > nofail let me run the initialization.
> >
> > Then,
> > mount /boot/efi
> > mount: /boot/efi: unknown filesystem type 'vfat'.
> >
> > I also noted during the load:
> > FAILED: failed to start load kernel modules
> >
> >
> > Now
> > journalctl -b -o short-monotonic --no-hostname
> >
> > It is long, I noted (in red):
> > [    4.338041] audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=42949672>
> > [    4.338061] audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=429496729>
> > [    4.338076] iscsid[838]: iSCSI daemon with pid=840 started!
> > [    4.338202] iscsid[838]: can't open InitiatorName configuration file /etc/is>
> > [    4.338216] iscsid[838]: Warning: InitiatorName file /etc/iscsi/initiatornam>
> > [    4.338229] iscsid[838]: can't open InitiatorAlias configuration file /etc/i>
> > [    4.338240] iscsid[838]: iscsid shutting down.
> > [    4.341185] systemd[1]: iscsid.service: Succeeded.
> >
> >
> > [    9.904952] zram_generator::generator[946]: modprobe "zram" failed, ignoring>
> > [   10.439405] systemd[926]: /usr/lib/systemd/system-generators/zram-generator >
> > [   11.940971] systemd[1]: Unknown serialization item 'show-status=yes', ignori>
> > [   11.968280] systemd[1]: initrd-switch-root.service: Current command vanished>
> > [   12.033261] kernel: audit: type=1131 audit(1626509496.013:47): pid=1 uid=0 a>
> >
> > [   12.462543] systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FA>
> > [   12.462635] systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
> > [   12.462951] systemd[1]: Failed to start Load Kernel Modules.
> > [   12.468566] systemd[1]: Condition check resulted in OSTree Remount OS/ Bind Mounts being skipped.
> > [   12.468593] systemd[1]: Condition check resulted in First Boot Wizard being skipped.
> >
> > [   12.596729] systemd[1]: systemd-journald.service: Deactivated successfully.
> > [   12.597268] systemd-modules-load[970]: Failed to look up module alias 'msr': Function not implement>
> > [   12.597839] systemd-modules-load[970]: Failed to look up module alias 'fuse': Function not implemen>
> >
> >
> >
> > [   22.973831] systemd[1]: boot-efi.mount: Mount process exited, code=exited, status=32/n/a
> > [   23.026760] systemd[1]: boot-efi.mount: Failed with result 'exit-code'.
> > [   23.027004] systemd[1]: Failed to mount /boot/efi.
> > [   23.027246] systemd[1]: Finished Flush Journal to Persistent Storage.
> > [  102.217573] systemd[1]: dev-zram0.device: Job dev-zram0.device/start timed out.
> > [  102.218867] systemd[1]: Timed out waiting for device /dev/zram0.
> > [  102.557734] systemd[1]: Dependency failed for Compressed Swap on /dev/zram0.
> > [  102.558003] systemd[1]: Dependency failed for Create swap on /dev/zram0.
> >
> > [  128.354157] systemd[1]: Starting Authorization Manager...
> > [  128.823608] avahi-daemon[1157]: System host name is set to 'localhost'. This is not a suitable mDNS>
> > [  128.823809] avahi-daemon[1157]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
> >
> > [  140.812865] systemd[1]: firewalld.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
> > [  140.813274] systemd[1]: firewalld.service: Failed with result 'exit-code'.
> >
> > [  146.600482] libvirtd[1359]: hostname: localhost.localdomain
> > [  146.600525] libvirtd[1359]: Unable to create bridge virbr0: Package not installed
> > [  147.104845] systemd[1422]: Queued start job for default target Main User Target.
> >
> > [  157.210842] pipewire-media-session[1565]: inotify_add_watch() '/dev/snd' failed: No such file or di>
> > [  157.359563] systemd[1]: Started WPA supplicant.
> >
> > [  159.349494] systemd-coredump[1708]: [🡕] Process 1565 (pipewire-media-) of user 42 dumped core.
> >
> >                                        Stack trace of thread 1565:
> >                                        #0  0x00007f9df19959a0 _DYNAMIC (libc.so.6 + 0x1c29a0)
> >
> > [  162.702491] audit[1804]: AVC avc:  denied  { write } for  pid=1804 comm="ibus-x11" name="dbus-vi7e8>
> > [  170.062078] gdm-password][1879]: gkr-pam: unable to locate daemon control file
> > [  170.063026] audit[1879]: USER_AUTH pid=1879 uid=0 auid=4294967295 ses=4294967295 subj=system_u:syst>
> > [
> >
> > [  185.002978] systemd[1895]: Starting GNOME Terminal Server...
> > [  185.076572] abrt-notification[2652]: [🡕] Process 2143 (pipewire-media-session) crashed in svcauthsw>
> > [  185.102957] vmware-user.desktop[2497]: Error: /usr/bin/vmtoolsd must be run inside a virtual machin>
> > [
> >
> > [  193.967216] systemd[1]: dev-zram0.device: Job dev-zram0.device/start timed out.
> > [  193.967861] systemd[1]: Timed out waiting for device /dev/zram0.
> > [  193.967973] systemd[1]: Dependency failed for Compressed Swap on /dev/zram0.
> > [  193.968031] systemd[1]: Dependency failed for Create swap on /dev/zram0.
> >
> >
> > > On Fri, Jul 16, 2021 at 1:20 PM Patrick Dupre <pdupre@xxxxxxx> wrote:
> > > >
> > > > I collected the maximum information that I could
> > > >
> > > > Failed Mounting /boot/efi
> > > > See "systemctl boot-efi" for details
> > > > Dependency failed for local file system
> > > > Dependency failed for mark the ... to relabel after reboot
> > > > Stopped
> > > > You are in emergency mode. After logging in type "journalctl -xb" to view system logs
> > > > "systemctl reboot" to reboot
> > > > "systemctl default" to exit
> > > > cannot open access to console, the root account is locked
> > > > see sulogin(8) man page for more details
> > > > Press Enter to continue
> > > > Rebooting system manager confirmation
> > > > Starting default target
> > > > You are in emergency mode ....................
> > > >
> > > > What are your siggestions ?
> > >
> > >
> > > > > > I'm not sure why /boot/efi is failing to mount need to see logs for
> > > > > > that, but you can also add nofail to the fstab for it so at least boot
> > > > > > won't hang.
> > >
> > > Did you add nofail to fstab options for the /boot/efi line?
> > >
> > > Can you post 'journalctl -b -o short-monotonic --no-hostname' somewhere?
> > >
> > > --
> > > Chris Murphy
> > > _______________________________________________
> > > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> > > To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
> > > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
> > >
> > _______________________________________________
> > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
> >
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux