veral
> >> disks, should I have a single /boot/efi ?
> >
> > It will work as long as none of the installed distributions are
> > duplicated, because that will duplicate the label. e.g. default
> > fedora label is fedora, so if more than one is installed there will
On Wed, Jul 27, 2022, at 11:20 AM, stan via users wrote:
> On Wed, 27 Jul 2022 10:54:51 +0200
> Patrick Dupre wrote:
>
>> If I have several distributions on a single machine with several
>> disks, should I have a single /boot/efi ?
>
> It will work as lo
On Wed, 27 Jul 2022 10:54:51 +0200
Patrick Dupre wrote:
> If I have several distributions on a single machine with several
> disks, should I have a single /boot/efi ?
It will work as long as none of the installed distributions are
duplicated, because that will duplicate the label
On Wed, 2022-07-27 at 10:54 +0200, Patrick Dupre wrote:
> If I have several distributions on a single machine with several
> disks, should I have a single /boot/efi ?
That is the general idea. It's part of the system bootloader, and
different OSs put their bits in there.
You'll
Hello,
If I have several distributions on a single machine with several
disks, should I have a single /boot/efi ?
Thank
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire
d 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
xt4
> 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 o
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/vmli
> 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 ?
>
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
t; 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
>
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 hav
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):
[
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 a
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 "journalc
t;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-
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
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
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
Thanks for the suggestions. I did boot off liveusb and ran fsck on
/boot/efi. It did report problems, and I answered questions with wild
guesses.
Seems to be OK now, and the dnf update completed OK.
On Sat, Jul 25, 2020 at 3:55 PM Joe Zeff wrote:
> On 07/25/2020 12:42 PM, Sam Varshavc
On 07/25/2020 12:42 PM, Sam Varshavchik wrote:
Perhaps the /boot/efi FAT partition got corrupted. Try fscking it.
Before you go that far, you might consider trying this:
df -h /boot/efi
This will tell you how much space is used and how much is free, in a
human readable format
Neal Becker writes:
« HTML content follows »
Trying to install updates today failed because not enough space on
/boot/efi. Any idea how I can fix this?
installing package grub2-efi-x64-cdboot-1:2.04-21.fc32.x86_64 needs 6MB on
the /boot/efi filesystem
Error Summary
On Sat, 25 Jul 2020 13:30:24 -0400
Neal Becker wrote:
> Trying to install updates today failed because not enough space on
> /boot/efi. Any idea how I can fix this?
>
> installing package grub2-efi-x64-cdboot-1:2.04-21.fc32.x86_64 needs
> 6MB on the /boot/efi filesystem
>
On Sat, 25 Jul 2020 at 14:31, Neal Becker wrote:
> Trying to install updates today failed because not enough space on
> /boot/efi. Any idea how I can fix this?
>
> installing package grub2-efi-x64-cdboot-1:2.04-21.fc32.x86_64 needs 6MB
> on the /boot/efi filesystem
&g
Trying to install updates today failed because not enough space on
/boot/efi. Any idea how I can fix this?
installing package grub2-efi-x64-cdboot-1:2.04-21.fc32.x86_64 needs 6MB
on the /boot/efi filesystem
Error Summary
-
Disk Requirements:
At least 6MB more space needed on
Tim via users writes:
On Tue, 2019-10-29 at 18:17 -0400, Sam Varshavchik wrote:
> Doesn't really matter, just curious that Anaconda sets /dev/sdb4 to
> be first in the boot order.
Did you install from some kind of boot disc? That can shuffle the
order of things, so (temporarily) it's sda, maki
On Tue, 2019-10-29 at 18:17 -0400, Sam Varshavchik wrote:
> Doesn't really matter, just curious that Anaconda sets /dev/sdb4 to
> be first in the boot order.
Did you install from some kind of boot disc? That can shuffle the
order of things, so (temporarily) it's sda, making your drives sdb,
sdc,
Gordon Messmer writes:
On 10/28/19 4:32 PM, Sam Varshavchik wrote:
With BIOS I knew I needed to run grub-install to manually install grub on
/dev/sdb in addition to /dev/sda; do I need to do anything analogous to
that, with EFI?
Typically, no. Anaconda should have created boot records fo
On 10/28/19 4:32 PM, Sam Varshavchik wrote:
With BIOS I knew I needed to run grub-install to manually install grub
on /dev/sdb in addition to /dev/sda; do I need to do anything
analogous to that, with EFI?
Typically, no. Anaconda should have created boot records for both. Use
"efibootmgr
On 10/28/19 4:32 PM, Sam Varshavchik wrote:
I want to make sure that in the event one of the disks fail I'll be able
to boot off the other one. Are any additional steps needed for this,
beyond the ones that were done by F30's installer?
You could make another EFI boot entry that points to the
I installed F30 on a replacement server with two HDDs. My existing hardware
earned its well-deserved retirement. My replacement hardware is the first
server hardware I'm using that uses EFI and the GPT.
I configured all my partitions with mdraid, including /boot/efi:
/dev/md124 on /boo
On 2015-04-09 20:52, Robin Laing wrote:
Hello,
A Fedora 21 laptop that was working now will not boot.
Fully updated dual boot machine. Windows quit working but Fedora worked
until last night.
Trying to boot today, it won't mount the efi partition. /boot/efi so
the boot process cannot
On Aug 31, 2014, at 8:50 AM, D. Hugh Redelmeier wrote:
> As I type this, I'm installing Fedora 20 on a UEFI system which already
> has CentOS 7 (and nothing else).
>
> Should the two systems share /boot/efi?
Ideally yes, although it's not required by the UEFI spec.
&
As I type this, I'm installing Fedora 20 on a UEFI system which already
has CentOS 7 (and nothing else).
Should the two systems share /boot/efi?
As I understand it, the answer is yes: /boot/efi is universal on a
machine. It is where the firmware goes to load things. Not just OS
bootl
35 matches
Mail list logo
