Re: failed to mount /boot/efi
Sorry Jonathan, But, I did not see your message! Anyway, thanks to your help. I understood that I did not boot by using the correct kernel. There was 5 options, and I did not try the right one! The issue is fixed. > To: "Community support for Fedora users" > Subject: Re: failed to mount /boot/efi > > On Jul 17, 2021, at 04:29, Patrick Dupre wrote: > > > > Then, > > mount /boot/efi > > mount: /boot/efi: unknown filesystem type 'vfat'. > > > > I also noted during the load: > > FAILED: failed to start load kernel modules > > You appear to be booting into a kernel that doesn’t have any kernel modules > available. Can you share with us the output of “uname -r” and “rpm -q kernel > kernel-modules”? > > I expect you’ve either managed to not have them installed or you are booting > a kernel from another version of Fedora (possibly due to your dual-boot > setup?) and there’s no kernel modules at all. > > I see a missing sound driver in your output too, which would also point at > kernel/modules mismatch. > — > Jonathan Billings > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: failed to mount /boot/efi Help!
On Jul 18, 2021, at 03:24, Patrick Dupre wrote: > > 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 > defaults1 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 ? You never answered my question. Can you share with us the output of “uname -r” and “rpm -q kernel kernel-modules”? — Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: failed to mount /boot/efi Help!
Thanks for the feedback,
However, I do not understand.
Do you mean in the grub configuration
/boot/efi/EFI/fedora/grub.cfg
I have
menuentry 'Fedora 34 (Workstation Edition) (on /dev/sda6)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-5.12.14-300.fc34.x86_64--a5b809ae-61c2-4d67-b0f3-109e99faad39'
{
insmod part_gpt
insmod ext2
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6
--hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6
a5b809ae-61c2-4d67-b0f3-109e99faad39
else
search --no-floppy --fs-uuid --set=root
a5b809ae-61c2-4d67-b0f3-109e99faad39
fi
linux /boot/vmlinuz-5.12.14-300.fc34.x86_64 root=/dev/sda6
initrd /boot/initramfs-5.12.14-300.fc34.x86_64.img
}
which seems correct to me.
> 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 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
> > defaults1 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
Re: failed to mount /boot/efi Help!
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 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 > defaults1 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 &g
Re: failed to mount /boot/efi Help!
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
defaults1 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 0x7f9df19959a0 _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
Re: failed to mount /boot/efi
If he ran a grub-mkconfig to regenerate the grub I am pretty sure it will make all kernels use the same options. I will mean that all boots have the same root= On Sat, Jul 17, 2021 at 4:29 PM Jonathan Billings wrote: > > On Jul 17, 2021, at 04:29, Patrick Dupre wrote: > > > > Then, > > mount /boot/efi > > mount: /boot/efi: unknown filesystem type 'vfat'. > > > > I also noted during the load: > > FAILED: failed to start load kernel modules > > You appear to be booting into a kernel that doesn’t have any kernel modules > available. Can you share with us the output of “uname -r” and “rpm -q kernel > kernel-modules”? > > I expect you’ve either managed to not have them installed or you are booting > a kernel from another version of Fedora (possibly due to your dual-boot > setup?) and there’s no kernel modules at all. > > I see a missing sound driver in your output too, which would also point at > kernel/modules mismatch. > — > Jonathan Billings > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: failed to mount /boot/efi
On Jul 17, 2021, at 04:29, Patrick Dupre wrote: > > Then, > mount /boot/efi > mount: /boot/efi: unknown filesystem type 'vfat'. > > I also noted during the load: > FAILED: failed to start load kernel modules You appear to be booting into a kernel that doesn’t have any kernel modules available. Can you share with us the output of “uname -r” and “rpm -q kernel kernel-modules”? I expect you’ve either managed to not have them installed or you are booting a kernel from another version of Fedora (possibly due to your dual-boot setup?) and there’s no kernel modules at all. I see a missing sound driver in your output too, which would also point at kernel/modules mismatch. — Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: failed to mount /boot/efi
Thanks,
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 0x7f9df19959a0 _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 wrote:
> >
> > I collected the maximum information that I could
> >
> > Failed Mounting /boot/efi
> > See "systemctl boot-efi" for details
> > Dependency failed for local file sys
Re: failed to mount /boot/efi
On Fri, Jul 16, 2021 at 1:20 PM Patrick Dupre 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@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: failed to mount /boot/efi
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 ? > > Hello, > > Running fc32 and fc34 is temporary > Actually, it is to be sure that I will not have issues when updating the fc32 > to fc34 > which really matters. > The fc32 is the primary system, but again, as soon that I have been able to > run properly the fc42, I will upgrade it. > > I did the same procedure on another machine and it was absolutely fine. > I am a bit stuck for now. > Obviously, there are some interference between the 2 systems. > Is it only under the control of grub2? > > The incomplete booting says: > failed to mount /boot:efi > check journalctl -xb > .etc.. > Cannot open access to console the root account is locked > > see man sulogin. > > Press Enter to continue > > > Than, I did press Enter, I just get a couple of messages and and again get > Press Enter to continue > > > When I check journalctl (when I can boot on the fc30 rescue version), I do > not see any think in red which could point the issue. > The output of journalctl is very long. > > How can I provide more information? > > Thanks > > > > > > > Hello, > > > > > > On a dual boot machine (one fc32, and one fc34). > > > after I upgraded the fc32 to fc34, I cannot boot on the new fc34. > > > > What does happen? I'm not sure what "cannot boot" means because it > > doesn't tell me how it's failing. > > > > > > > I get > > > failed to mount /boot/efi > > > /boot/efi is shared by both machines > > > > > > Here is the fstab of the fc34 machine > > > > > > # > > > UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4 > > > defaults1 1 > > > UUID=B2EF-0CE4 /boot/efi vfat > > > umask=0077,shortname=winnt 0 2 > > > > > > > > > The /boot/efi seem correct (it is currently mounted by the fc32). > > > > > > blkid |grep B2EF > > > /dev/sdb1: UUID="B2EF-0CE4" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI > > > System Partition" PARTUUID="0fe1d405-6683-456c-a306-140e882e322c" > > > blkid |grep 9faad39 > > > /dev/sda6: LABEL="fedora_rescue" > > > UUID="a5b809ae-61c2-4d67-b0f3-109e99faad39" BLOCK_SIZE="4096" TYPE="ext4" > > > PARTLABEL="OS" PARTUUID="41b9d134-b477-4ef5-8602-15fdc482a51e" > > > > > > What should I do ? > > > It seems that the installer create /boot/efi/EFI/fedora/grub.cfg > > > > I'm not really certain the best way to share a single > > /boot/efi/EFI/fedora between two Fedoras. > > > > My idea would be for Fedora 34 to be primary, and exclude shim and all > > of grub2 from being updated on Fedora 32. Well, ha, as I think about > > it, that doesn't matter anymore because there are no more updates, > > it's EOL. > > > > What you really want to do though is share a single /boot because the > > single bootloader needs to see a single set of configuration files > > found in /boot/loader/entries. And the f32 snippets will point to the > > f32 kernels and f32 system root. And the f34 snippets will point to > > the f34 kernels and system root. It definitely works, except for one > > problem: > > https://bugzilla.redhat.com/show_bug.cgi?id=1874724 > > > > > > > > > with > > > search --no-floppy --fs-uuid --set=dev > > > a5b809ae-61c2-4d67-b0f3-109e99faad39 > > > set prefix=($dev)/boot/grub2 > > > export $prefix > > > configfile $prefix/grub.cfg > > > > > > (I could not boot either) > > > Then I run (from the fc32) > > > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg.new > > > > > > and used this file to boot (by renamed). > > > > OK I can't tell where the f32 /boot is, but you need all the snippets > > in one /boot/loader/entries that both f32 and
Re: failed to mount /boot/efi
Hello, Running fc32 and fc34 is temporary Actually, it is to be sure that I will not have issues when updating the fc32 to fc34 which really matters. The fc32 is the primary system, but again, as soon that I have been able to run properly the fc42, I will upgrade it. I did the same procedure on another machine and it was absolutely fine. I am a bit stuck for now. Obviously, there are some interference between the 2 systems. Is it only under the control of grub2? The incomplete booting says: failed to mount /boot:efi check journalctl -xb .etc.. Cannot open access to console the root account is locked see man sulogin. Press Enter to continue Than, I did press Enter, I just get a couple of messages and and again get Press Enter to continue When I check journalctl (when I can boot on the fc30 rescue version), I do not see any think in red which could point the issue. The output of journalctl is very long. How can I provide more information? Thanks > > > > Hello, > > > > On a dual boot machine (one fc32, and one fc34). > > after I upgraded the fc32 to fc34, I cannot boot on the new fc34. > > What does happen? I'm not sure what "cannot boot" means because it > doesn't tell me how it's failing. > > > > I get > > failed to mount /boot/efi > > /boot/efi is shared by both machines > > > > Here is the fstab of the fc34 machine > > > > # > > UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4 > > defaults1 1 > > UUID=B2EF-0CE4 /boot/efi vfat > > umask=0077,shortname=winnt 0 2 > > > > > > The /boot/efi seem correct (it is currently mounted by the fc32). > > > > blkid |grep B2EF > > /dev/sdb1: UUID="B2EF-0CE4" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI > > System Partition" PARTUUID="0fe1d405-6683-456c-a306-140e882e322c" > > blkid |grep 9faad39 > > /dev/sda6: LABEL="fedora_rescue" > > UUID="a5b809ae-61c2-4d67-b0f3-109e99faad39" BLOCK_SIZE="4096" TYPE="ext4" > > PARTLABEL="OS" PARTUUID="41b9d134-b477-4ef5-8602-15fdc482a51e" > > > > What should I do ? > > It seems that the installer create /boot/efi/EFI/fedora/grub.cfg > > I'm not really certain the best way to share a single > /boot/efi/EFI/fedora between two Fedoras. > > My idea would be for Fedora 34 to be primary, and exclude shim and all > of grub2 from being updated on Fedora 32. Well, ha, as I think about > it, that doesn't matter anymore because there are no more updates, > it's EOL. > > What you really want to do though is share a single /boot because the > single bootloader needs to see a single set of configuration files > found in /boot/loader/entries. And the f32 snippets will point to the > f32 kernels and f32 system root. And the f34 snippets will point to > the f34 kernels and system root. It definitely works, except for one > problem: > https://bugzilla.redhat.com/show_bug.cgi?id=1874724 > > > > > with > > search --no-floppy --fs-uuid --set=dev a5b809ae-61c2-4d67-b0f3-109e99faad39 > > set prefix=($dev)/boot/grub2 > > export $prefix > > configfile $prefix/grub.cfg > > > > (I could not boot either) > > Then I run (from the fc32) > > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg.new > > > > and used this file to boot (by renamed). > > OK I can't tell where the f32 /boot is, but you need all the snippets > in one /boot/loader/entries that both f32 and f34 share. > > 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. > > The gist of what you need is one f34 bootloader in > /boot/efi/EFI/fedora/ and its grub.cfg points to the real grub.cfg at > /boot/grub2 which in turn loads blscfg.mod which finds and reads > /boot/loader/entries and then creates a GRUB menu from all the > snippets found there. > > > > > -- > Chris Murphy > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: failed to mount /boot/efi
On Thu, Jul 15, 2021 at 12:31 PM Patrick Dupre wrote: > > I have been able to boot on a rescue kernel! > Linux localhost.localdomain 5.6.13-100.fc30.x86_64 #1 SMP Fri May 15 00:36:06 > UTC 2020 x86_64 x86_64 x86_64 GNU/Linux > > bootctl > systemd-boot not installed in ESP. > System: > Firmware: n/a (n/a) > Secure Boot: disabled >Setup Mode: user > TPM2 Support: yes > Boot into FW: supported > > Current Boot Loader: > Product: n/a > Features: ✗ Boot counting >✗ Menu timeout control >✗ One-shot menu timeout control >✗ Default entry control >✗ One-shot entry control >✗ Support for XBOOTLDR partition >✗ Support for passing random seed to OS >✗ Boot loader sets ESP partition information > ESP: n/a > File: └─n/a > > > Is this normal ? Yes, bootctl is for the systemd-boot bootloader, which Fedora doesn't use right now. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: failed to mount /boot/efi
On Thu, Jul 15, 2021 at 12:01 PM Patrick Dupre wrote: > > Hello, > > On a dual boot machine (one fc32, and one fc34). > after I upgraded the fc32 to fc34, I cannot boot on the new fc34. What does happen? I'm not sure what "cannot boot" means because it doesn't tell me how it's failing. > I get > failed to mount /boot/efi > /boot/efi is shared by both machines > > Here is the fstab of the fc34 machine > > # > UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4 > defaults1 1 > UUID=B2EF-0CE4 /boot/efi vfat > umask=0077,shortname=winnt 0 2 > > > The /boot/efi seem correct (it is currently mounted by the fc32). > > blkid |grep B2EF > /dev/sdb1: UUID="B2EF-0CE4" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI > System Partition" PARTUUID="0fe1d405-6683-456c-a306-140e882e322c" > blkid |grep 9faad39 > /dev/sda6: LABEL="fedora_rescue" UUID="a5b809ae-61c2-4d67-b0f3-109e99faad39" > BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="OS" > PARTUUID="41b9d134-b477-4ef5-8602-15fdc482a51e" > > What should I do ? > It seems that the installer create /boot/efi/EFI/fedora/grub.cfg I'm not really certain the best way to share a single /boot/efi/EFI/fedora between two Fedoras. My idea would be for Fedora 34 to be primary, and exclude shim and all of grub2 from being updated on Fedora 32. Well, ha, as I think about it, that doesn't matter anymore because there are no more updates, it's EOL. What you really want to do though is share a single /boot because the single bootloader needs to see a single set of configuration files found in /boot/loader/entries. And the f32 snippets will point to the f32 kernels and f32 system root. And the f34 snippets will point to the f34 kernels and system root. It definitely works, except for one problem: https://bugzilla.redhat.com/show_bug.cgi?id=1874724 > with > search --no-floppy --fs-uuid --set=dev a5b809ae-61c2-4d67-b0f3-109e99faad39 > set prefix=($dev)/boot/grub2 > export $prefix > configfile $prefix/grub.cfg > > (I could not boot either) > Then I run (from the fc32) > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg.new > > and used this file to boot (by renamed). OK I can't tell where the f32 /boot is, but you need all the snippets in one /boot/loader/entries that both f32 and f34 share. 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. The gist of what you need is one f34 bootloader in /boot/efi/EFI/fedora/ and its grub.cfg points to the real grub.cfg at /boot/grub2 which in turn loads blscfg.mod which finds and reads /boot/loader/entries and then creates a GRUB menu from all the snippets found there. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: failed to mount /boot/efi
I have been able to boot on a rescue kernel! Linux localhost.localdomain 5.6.13-100.fc30.x86_64 #1 SMP Fri May 15 00:36:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux bootctl systemd-boot not installed in ESP. System: Firmware: n/a (n/a) Secure Boot: disabled Setup Mode: user TPM2 Support: yes Boot into FW: supported Current Boot Loader: Product: n/a Features: ✗ Boot counting ✗ Menu timeout control ✗ One-shot menu timeout control ✗ Default entry control ✗ One-shot entry control ✗ Support for XBOOTLDR partition ✗ Support for passing random seed to OS ✗ Boot loader sets ESP partition information ESP: n/a File: └─n/a Is this normal ? > > Hello, > > On a dual boot machine (one fc32, and one fc34). > after I upgraded the fc32 to fc34, I cannot boot on the new fc34. > I get > failed to mount /boot/efi > /boot/efi is shared by both machines > > Here is the fstab of the fc34 machine > > # > UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4 > defaults1 1 > UUID=B2EF-0CE4 /boot/efi vfat > umask=0077,shortname=winnt 0 2 > > > The /boot/efi seem correct (it is currently mounted by the fc32). > > blkid |grep B2EF > /dev/sdb1: UUID="B2EF-0CE4" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI > System Partition" PARTUUID="0fe1d405-6683-456c-a306-140e882e322c" > blkid |grep 9faad39 > /dev/sda6: LABEL="fedora_rescue" UUID="a5b809ae-61c2-4d67-b0f3-109e99faad39" > BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="OS" > PARTUUID="41b9d134-b477-4ef5-8602-15fdc482a51e" > > What should I do ? > It seems that the installer create /boot/efi/EFI/fedora/grub.cfg > with > search --no-floppy --fs-uuid --set=dev a5b809ae-61c2-4d67-b0f3-109e99faad39 > set prefix=($dev)/boot/grub2 > export $prefix > configfile $prefix/grub.cfg > > (I could not boot either) > Then I run (from the fc32) > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg.new > > and used this file to boot (by renamed). > > But I still have the same issue. > > What to do? > It seems that there is a similar issue inb > https://unix.stackexchange.com/questions/646150/problem-with-double-fedora-installation-mount-boot-efi-unknown-filesystem-ty > > Thanks. > > === > Patrick DUPRÉ | | email: pdu...@gmx.com > Laboratoire interdisciplinaire Carnot de Bourgogne > 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE > Tel: +33 (0)380395988| | Room# D114A > === > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
failed to mount /boot/efi
Hello, On a dual boot machine (one fc32, and one fc34). after I upgraded the fc32 to fc34, I cannot boot on the new fc34. I get failed to mount /boot/efi /boot/efi is shared by both machines Here is the fstab of the fc34 machine # UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4 defaults1 1 UUID=B2EF-0CE4 /boot/efi vfat umask=0077,shortname=winnt 0 2 The /boot/efi seem correct (it is currently mounted by the fc32). blkid |grep B2EF /dev/sdb1: UUID="B2EF-0CE4" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="0fe1d405-6683-456c-a306-140e882e322c" blkid |grep 9faad39 /dev/sda6: LABEL="fedora_rescue" UUID="a5b809ae-61c2-4d67-b0f3-109e99faad39" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="OS" PARTUUID="41b9d134-b477-4ef5-8602-15fdc482a51e" What should I do ? It seems that the installer create /boot/efi/EFI/fedora/grub.cfg with search --no-floppy --fs-uuid --set=dev a5b809ae-61c2-4d67-b0f3-109e99faad39 set prefix=($dev)/boot/grub2 export $prefix configfile $prefix/grub.cfg (I could not boot either) Then I run (from the fc32) grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg.new and used this file to boot (by renamed). But I still have the same issue. What to do? It seems that there is a similar issue inb https://unix.stackexchange.com/questions/646150/problem-with-double-fedora-installation-mount-boot-efi-unknown-filesystem-ty Thanks. === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988| | Room# D114A === ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
