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
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.
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 chang
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 v
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 /b
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.
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] audi
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
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
syst
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
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:
> Firmwa
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
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:
14 matches
Mail list logo
