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: faile
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
> defaults
gt; > > [ 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
&g
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
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 mo
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
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
: 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
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
t;
> 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" mea
not 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-
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:
>
w 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
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
> defaults
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
15 matches
Mail list logo
