On 6/28/24 11:25 AM, Jeffrey Walton wrote:
Another one to avoid: cheap SSDs with duplicate serial numbers. Some
manufacturers repeat (clone?) serial numbers, and when you try to use
them in a RAID configuration, things go badly. A fellow on a Ubuntu
list struggled for months because of it.
That
On 2024-06-28 14:25, Jeffrey Walton wrote:
Another one to avoid: cheap SSDs with duplicate serial numbers. Some
manufacturers repeat (clone?) serial numbers, and when you try to use
them in a RAID configuration, things go badly. A fellow on a Ubuntu
list struggled for months because of it.
At
On Fri, Jun 28, 2024 at 2:10 PM Frank Bures wrote:
>
> On 2024-06-23 11:43, Frank Bures wrote:
> > On 2024-06-23 04:29, Tim wrote:
>
> > I followed
> >
> > https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configuration_on_UEFI_systems
> >
> > and then I tried to run
> > grub2-emu
> >
On 2024-06-23 11:43, Frank Bures wrote:
On 2024-06-23 04:29, Tim wrote:
I followed
https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configuration_on_UEFI_systems
and then I tried to run
grub2-emu
I get the list of installed kernels OK, but any choice for boot returns
error: .
dot at the end of the
line, is it normal?
No matter which kernel I choose, I get the error that kernel file was not
found. All kernel files are in /boot and have correct permissions.
I checked UUIDs of /boot, /boot/efi and / and they are all correct.
I think this is the original problem that
On Sat, 2024-06-22 at 23:54 -0400, Frank Bures wrote:
> This is what my efibootmgr returns:
>
> root@ryzen:/# efibootmgr
> BootCurrent: 0002
> Timeout: 1 seconds
> BootOrder: 0002,,0001
> Boot Fedora
> HD(1,GPT,e8838c34-c364-4347-afb7-1c516782b114,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI
On 2024-06-22 20:59, Frank Bures wrote:
Hi,
I just did a kernel update and after reboot I ended up in a grub prompt.
I booted from USB F40 and followed instructions at
https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_restoring_the_bootloader_using_the_live_disk
However
Hi,
I just did a kernel update and after reboot I ended up in a grub prompt.
I booted from USB F40 and followed instructions at
https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_restoring_the_bootloader_using_the_live_disk
However, whatever I did I was not able to
On Mon, Apr 22, 2024 at 8:26 AM Klaus-Peter Schrage via users <
users@lists.fedoraproject.org> wrote:
> [...]
>
I have checked/rechecked three times:
> /boot/efi/EFI/fedora/grub.cfg with flag "--root-dev-only": grub goes to
> prompt, $prefix is obviously not set.
> /boot/efi/EFI/fedora/grub.cfg wi
Am 21.04.24 um 18:34 schrieb Go Canes:
On Sun, Apr 21, 2024 at 12:15 PM Klaus-Peter Schrage via users
wrote:
/boot/efi/EFI/fedora/grub.cfg:
search --no-floppy --root-dev-only --fs-uuid --set=dev
206c0b5f-eddf-42e8-96f1-e666c5635cd0
set prefix=($dev)/grub2
export $prefix
B_DISTRIBUTOR= on EXT4-formatted nvme0n1p7.
If you can correctly equate your installed values for those in my Grub stanza
above, you should be able to boot by typing in each of the necessary lines from
your grub> prompt to get booted.
--
Evolution as taught in public schools is, like religion,
On Sun, Apr 21, 2024 at 12:15 PM Klaus-Peter Schrage via users
wrote:
>
> Am 20.04.24 um 23:16 schrieb George N. White III:
> > I assume you can still boot with manual grub commands.
> Yes, linux ..., initrd ..., boot
> or: >configfile (hd0,1)/grub2/grub.cfg
> which immediately brings back the gru
far as I remember, the system simply wouldn't boot if there were a typo
in fstab.
As described earlier, I always ended up at the grub prompt.
What I found: If I write the "real" grub.conf directly to the efi
partition (*|grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg), then I
boot to t
Joe Zeff:
>> In all the years I've been using Linux, I've never yet run across a .pdf
>> file that Linux's default viewer couldn't read. What is it about those
>> files that requires Windows to read?
George N. White III:
> a) fillable forms that explicitly say they must be completed using Windows
On Sat, Apr 20, 2024 at 6:43 PM Joe Zeff wrote:
> On 04/20/2024 03:16 PM, George N. White III wrote:
> > In preparation for converting my dual boot Win10+Fedora system
> > to Fedora only, I needed to expand the Win11 partition on another
> > dual boot system because some "mission critical" Adobe
On 04/20/2024 03:16 PM, George N. White III wrote:
In preparation for converting my dual boot Win10+Fedora system
to Fedora only, I needed to expand the Win11 partition on another
dual boot system because some "mission critical" Adobe PDF documents
require Windows.
In all the years I've been us
On Wed, Apr 17, 2024 at 11:48 AM Klaus-Peter Schrage via users <
users@lists.fedoraproject.org> wrote:
> After many years of maintaing dual boot setups (Fedora/Windows) my
> harddisk layout got a bit confusing: Linux and Windows partition were
> scattered on mainly two harddisks (all gpt). I was a
explanation! I went
through all the steps, checked the IDs from efibootmgr and
blkid with respect to the various configuration files - and
found no mismatch, but again I ended up with the grub prompt.
Tomorrow I am going to spend another rainy afternoon
double
o the various configuration files - and found no mismatch,
>> but again I ended up with the grub prompt.
>> Tomorrow I am going to spend another rainy afternoon double-checking -
>> and then I'll give up and do a fresh fedora install on blank /dev/sda
>> (which might
On 4/20/2024 1:14 PM, Klaus-Peter Schrage via users wrote:
I am really grateful for your detailed explanation!
I went through all the steps, checked the IDs from efibootmgr and blkid
with respect to the various configuration files - and found no mismatch,
but again I ended up with the grub
led explanation!
I went through all the steps, checked the IDs from efibootmgr and blkid
with respect to the various configuration files - and found no mismatch,
but again I ended up with the grub prompt.
Tomorrow I am going to spend another rainy afternoon double-checking -
and then I'll giv
will load grub while will
use grub.cfg from the same directory.
[root@fubar ~]# cat /boot/efi/EFI/fedora/grub.cfg
search --no-floppy --fs-uuid --set=dev c5f18a2c-ee16-454e-b85d-6d7f03b86532
set prefix=($dev)/grub2
export $prefix
configfile $prefix/grub.cfg
[ Since you are getting a grub prompt, I thi
Am 17.04.24 um 18:45 schrieb Felix Miata:
Klaus-Peter Schrage via users composed on 2024-04-17 16:48 (UTC+0200):
After many years of maintaing dual boot setups (Fedora/Windows) my
harddisk layout got a bit confusing: Linux and Windows partition were
scattered on mainly two harddisks (all gpt).
Am 17.04.24 um 17:51 schrieb Go Canes:
Step by step:
I recently had similar problems. These are the things to check:
o use blkid to get the current UUID(s)
The current UUIDs correspond to the ones in /etc/fstab, that hadn't been
changed btw.
o check /etc/kernel/cmdline if it exists - make sure
ARTUUID. In my case I needed the *new* UUID for
the root partition in both of the grub.cfg files (*not* the PARTUUID).
IIRC, I was getting dropped into the dracut shell (not grub) until I
updated both of the grub.cfg files, and then was stopped at the grub
prompt until I found and updated /etc
Klaus-Peter Schrage via users composed on 2024-04-17 16:48 (UTC+0200):
> After many years of maintaing dual boot setups (Fedora/Windows) my
> harddisk layout got a bit confusing: Linux and Windows partition were
> scattered on mainly two harddisks (all gpt). I was able to free a third
> harddisk (
Thanks for your quick reply!
I faintly remembered the dracut thing, so I tried that first - but it
didn't help.
I will look into the UUID stuff tomorrow, although I had already checked
that gparted really did not change UUIDs when moving partitions around.
And as I said, I can get into Fedora a
On Wed, Apr 17, 2024 at 10:48 AM Klaus-Peter Schrage via users
wrote:
> But rebooting still gets me to the dreaded grub>.
> So what am I missing?
> BTW, I did NOT use the grub2-install command which shoud not be used on
> UEFI systems.
I recently had similar problems. These are the things to che
After many years of maintaing dual boot setups (Fedora/Windows) my
harddisk layout got a bit confusing: Linux and Windows partition were
scattered on mainly two harddisks (all gpt). I was able to free a third
harddisk (ssd) and copied the linux partitions boot, root and home over
to the new disk,
p from Fedora-MATE_Compiz-Live-x86_64-32-1.6.iso.
> Then updated.
> It seem that if I try to boot I just get the dreaded grub> prompt.
> But if I have the live-usb stick inserted it boots normally.
>
> Any ideas?
>
> --
> Those who don't unders
I installed F32 on a laptop
from Fedora-MATE_Compiz-Live-x86_64-32-1.6.iso. Then updated.
It seem that if I try to boot I just get the dreaded grub> prompt.
But if I have the live-usb stick inserted it boots normally.
Any ideas?
--
*Those who don't understand recursion are doomed to r
This morning I got the dreaded grub prompt on boot.
Took me 3 hours to understand what
https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade
was talking about. I did a bunch of searching and trying things out before
I hit upon
the configfile grub command
to an older one from
Fedora 29. I never saw this before. So I have to catch up before the
Grub prompt automatically selects the second kernel in the boot menu.
Anybody experiencing this?
--
David Dusanic
___
users mailing list -- users@lists.fedorapro
On Thu, May 2, 2019 at 8:10 AM Ralf Corsepius wrote:
> On 5/1/19 8:24 AM, Chris Murphy wrote:
>
>> It happens if the most recent 'grub2-install' happened with a Fedora
>> 20 or older GRUB package. e.g. if you installed Fedora 20 clean, then
>> did an OS upgrade every 6-12 months all the way throug
On Wed, May 1, 2019 at 7:19 PM Charles R. Dennett wrote:
> On 5/1/19 11:07 AM, Tom H wrote:
>> On Wed, May 1, 2019 at 12:48 PM Charles R. Dennett
>> wrote:
>>>
>>> Is there any way to tell just by looking for the presence or absence
>>> of any particular file or directory that you would run into
On 5/1/19 8:24 AM, Chris Murphy wrote:
It happens if the most recent 'grub2-install' happened with a Fedora
20 or older GRUB package. e.g. if you installed Fedora 20 clean, then
did an OS upgrade every 6-12 months all the way through to Fedora 30,
then you'd probably run into this bug. But if at
On 5/1/19 11:07 AM, Tom H wrote:
> On Wed, May 1, 2019 at 12:48 PM Charles R. Dennett wrote:
>>
>> Is there any way to tell just by looking for the presence or absence
>> of any particular file or directory that you would run into this
>> bug?
>
> Unless you're multi-booting and grub's managed
On Wed, May 1, 2019 at 12:48 PM Charles R. Dennett wrote:
> On 5/1/19 5:25 AM, Tom H wrote:
>> On Wed, May 1, 2019 at 3:21 AM Todd Zullinger wrote:
>>>
>>> What I took from the prior wording is that if you installed Fedora
>>> 20 or earlier and then only updated the OS since (and had not
>>> manu
On 5/1/19 5:25 AM, Tom H wrote:
> On Wed, May 1, 2019 at 3:21 AM Todd Zullinger wrote:
>>
>> What I took from the prior wording is that if you installed Fedora
>> 20 or earlier and then only updated the OS since (and had not
>> manually run grub2-update), that you would hit this bug.
>
> "grub2
On Wed, May 1, 2019 at 3:21 AM Todd Zullinger wrote:
>
> What I took from the prior wording is that if you installed Fedora
> 20 or earlier and then only updated the OS since (and had not
> manually run grub2-update), that you would hit this bug.
"grub2-install" not "grub2-update".
__
On Wed, May 1, 2019 at 2:49 AM Chris Murphy wrote:
> On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
> wrote:
>> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
>>>
>>> Just a heads up that this can be an issue, but I'm not sure how
>>> common it is. It applies to BIOS (not UEFI) firmw
On Tue, Apr 30, 2019 at 7:21 PM Todd Zullinger wrote:
>
> Chris Murphy wrote:
> > On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
> > wrote:
> >>
> >> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> >>> Just a heads up that this can be an issue, but I'm not sure how common
> >>> it i
Chris Murphy writes:
On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
wrote:
>
> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> > Just a heads up that this can be an issue, but I'm not sure how common
> > it is. It applies to BIOS (not UEFI) firmware, and for systems that
> > origi
Chris Murphy wrote:
> On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
> wrote:
>>
>> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
>>> Just a heads up that this can be an issue, but I'm not sure how common
>>> it is. It applies to BIOS (not UEFI) firmware, and for systems that
>>> ori
On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan
wrote:
>
> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> > Just a heads up that this can be an issue, but I'm not sure how common
> > it is. It applies to BIOS (not UEFI) firmware, and for systems that
> > originally had Fedora 20 or o
On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
> Just a heads up that this can be an issue, but I'm not sure how common
> it is. It applies to BIOS (not UEFI) firmware, and for systems that
> originally had Fedora 20 or older installed and also never had
> 'grub2-install' issued since then.
Just a heads up that this can be an issue, but I'm not sure how common
it is. It applies to BIOS (not UEFI) firmware, and for systems that
originally had Fedora 20 or older installed and also never had
'grub2-install' issued since then. Therefore it can be prevented just
by running 'grub2-install'
On Tue, 2018-11-27 at 16:17 -0700, linux guy wrote:
> Interesting. /boot/efi/EFI/fedora/grub.cfg didn't exist on my
> workstation. But /etc/grub2-efi.cfg points to it ! /boot/efi
> existed, but it was empty.
This means that either /boot/efi/ isn't mounted after you reboot (check
/etc/fstab)
On 11/27/18 3:17 PM, linux guy wrote:
Interesting. /boot/efi/EFI/fedora/grub.cfg didn't exist on my
workstation. But /etc/grub2-efi.cfg points to it ! /boot/efi existed,
but it was empty.
How are you booting into it right now to do this?
Btw, both grub.cfg symlinks are always created whet
ow
It rebooted to the grub prompt.
Now what ?
On Mon, Nov 26, 2018 at 11:12 PM Samuel Sieb wrote:
> On 11/26/18 7:56 PM, linux guy wrote:
> > It still boots to the grub prompt, even when I use -o
> /boot/grub2/grub.cfg
>
> That is still the wrong file. You need either
> /boot/ef
Thank you.
On Mon, Nov 26, 2018 at 11:12 PM Samuel Sieb wrote:
> On 11/26/18 7:56 PM, linux guy wrote:
> > It still boots to the grub prompt, even when I use -o
> /boot/grub2/grub.cfg
>
> That is still the wrong file. You need either
> /boot/efi/EFI/fedora/grub.cfg
>
On 11/26/18 7:56 PM, linux guy wrote:
It still boots to the grub prompt, even when I use -o /boot/grub2/grub.cfg
That is still the wrong file. You need either
/boot/efi/EFI/fedora/grub.cfg
or
/etc/grub2-efi.cfg which is a symlink to the first one
I'm using UEFI.
On Tue, Oct 30, 2018 at 2:43 PM stan wrote:
> On Tue, 30 Oct 2018 11:28:36 -0600
> linux guy wrote:
>
> > I have an up to date F28 server that boots to the grub prompt. This
> > started after a failed dnf update.
> >
> > The computer
It still boots to the grub prompt, even when I use -o /boot/grub2/grub.cfg
On Thu, Nov 1, 2018 at 1:33 PM linux guy wrote:
> I was running grub2-mkconfig. I did not use -o.
>
> I never even thought of that. I was running it from the wrong directory
> ! Good catch. Thanks
I was running grub2-mkconfig. I did not use -o.
I never even thought of that. I was running it from the wrong directory
! Good catch. Thanks for replying.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-
On Tue, Oct 30, 2018 at 7:23 PM linux guy wrote:
>
> I have an up to date F28 server that boots to the grub prompt. This started
> after a failed dnf update.
>
> The computer will boot to an emergency mode command prompt if I set it up
> properly from the grub prompt.
>
On Tue, 30 Oct 2018 11:28:36 -0600
linux guy wrote:
> I have an up to date F28 server that boots to the grub prompt. This
> started after a failed dnf update.
>
> The computer will boot to an emergency mode command prompt if I set
> it up properly from the grub prompt.
>
I have an up to date F28 server that boots to the grub prompt. This
started after a failed dnf update.
The computer will boot to an emergency mode command prompt if I set it up
properly from the grub prompt.
grub> set root=(lvm/fedora-root)
grub> linuxefi (hd0,gpt2)/vmlinuz-0-rescue..
58 matches
Mail list logo
