8:37 a.m.
Have 5 Fedora Linux machines at home. 3 with Fedora 34
and 2 with Fedora 35.
One of the Fedora 34 machines after kernel upgrade two
times ago has stopped auto booting?? Comes up with
grub menu and sits there doing nothing?
Pressing the Enter key has it boot the highlighted top
latest kernel, and it then works fine.
Looked at log files, but didn't see anything.
Did a reinstall of the kernel-core no change.
Did a reinstall of grub2 files and again no change.
Looked at /etc/defaults/grub seems same as other
machines.
Saw some lines about hibernation in boot.log, but never
have used hibernation.
This machine is generally headless (no monitor).
Have a monitor hooked at moment, but anytime I do a
reboot on it, have to manually hit the enter key.
Today dnf update included another kernel, but same
thing. New kernel shows at top, but no timeout, and only
manually pressing enter gets it to boot.
Any ideals? Was planning on upgrading machine to 35,
but with boot process acting up don't know.
Thanks.
9:30 a.m.
On Tue, 29 Mar 2022 23:37:43 +1000
Michael D. Setzer II via users wrote:
Any ideals? Was planning on upgrading machine to 35,
but with boot process acting up don't know.
I had a lot of trouble with "helpful" logic in the grub scripts
wanting to do a lot of nonsense based on info it stashed in
the grub environment. I don't remember if there is logic to prevent
a boot when it imagines you want to know something, but it
wouldn't surprise me. The grub2-editenv tool can print the
environment for you (and modify it if you get the confusing
arguments in the right order), perhaps you can see something
different in the environment file.
9:59 a.m.
Machine that doesn't timeout boot, before it has a similar
saved_entry, but tried resetting it to 0 to boot from 1st
one.
grub2-editenv list
saved_entry=0
boot_success=1
boot_indeterminate=0
This notebook that works fine
grub2-editenv list
saved_entry=189711f94e78436d9618b891a8fce70e-5.16.
17-100.fc34.x86_64
boot_success=1
boot_indeterminate=0
I comparied the 2 grub.cfg files and they were pretty
much identicle. Only difference is notebook has windows
7 on hard disk originally, so the linux uses msdos5
instead of msdos1 on the other. The only other thing was
kernel number at front, but matches with the /boot/loader
on each machine, and the blkid of machines, but those
match with machines.
So, strange generally do a dnf update on all machines,
and for many years, they all reported normally with
nothing needing to be done?
Pressing the enter gets a normal boot with no message,
but requires the manual step of physically hitting enter
on the keyboard.
Thanks for the quick reply. Hopefully, someone can figure
something that might do it, or at least get something to
show why it doesn't do the count down and autoboot.
On 29 Mar 2022 at 10:30, Tom Horsley wrote:
Date sent: Tue, 29 Mar 2022 10:30:30 -0400
From: Tom Horsley <horsley1953(a)gmail.com>
To: users(a)lists.fedoraproject.org
Subject: Re: Have one of 5 machines that no longer
autoboots??
Send reply to: Community support for Fedora
users <users(a)lists.fedoraproject.org>
On Tue, 29 Mar 2022 23:37:43 +1000
Michael D. Setzer II via users wrote:
> Any ideals? Was planning on upgrading machine to 35,
> but with boot process acting up don't know.
I had a lot of trouble with "helpful" logic in the grub scripts
wanting to do a lot of nonsense based on info it stashed in
the grub environment. I don't remember if there is logic to prevent
a boot when it imagines you want to know something, but it
wouldn't surprise me. The grub2-editenv tool can print the
environment for you (and modify it if you get the confusing
arguments in the right order), perhaps you can see something
different in the environment file.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
10:51 a.m.
On Wed, 30 Mar 2022 00:59:54 +1000
"Michael D. Setzer II via users" <users(a)lists.fedoraproject.org> wrote:
Machine that doesn't timeout boot, before it has a similar
saved_entry, but tried resetting it to 0 to boot from 1st
one.
grub2-editenv list
saved_entry=0
boot_success=1
boot_indeterminate=0
This notebook that works fine
grub2-editenv list
saved_entry=189711f94e78436d9618b891a8fce70e-5.16.
17-100.fc34.x86_64
boot_success=1
boot_indeterminate=0
I haven't had to examine grub for a long time. So, I'm not familiar
enough with it to say what is incorrect. What do the successful and
failing system have in
/etc/default/grub ?
I think if you put the line
GRUB_DEFAULT=saved
in that file on the failing machine, and then run
grub2-mkconfig -o grub.cfg
on the failing machine in the directory where the grub.cfg is,
it will start booting properly again. The location of grub.cfg
*should* be in /boot/grub2/ unless the machines are booting EFI. Then
the grub.cfg will be in /boot/efi/EFI/fedora. This has changed since
f34 so that grub.cfg is *always* in /boot/grub2/ now.
If you install / have installed pinfo, you can get lots of information
about grub by running
pinfo grub2
Arrow keys will move around, space will move to links.
11:14 a.m.
On 29 Mar 2022 at 8:51, stan via users wrote:
Date sent: Tue, 29 Mar 2022 08:51:13 -0700
To: users(a)lists.fedoraproject.org
Subject: Re: Have one of 5 machines that no longer
autoboots??
Organization: zohofree
Send reply to: Community support for Fedora
users <users(a)lists.fedoraproject.org>
From: stan via users
<users(a)lists.fedoraproject.org>
Copies to: stan <upaitag(a)zoho.com>
On Wed, 30 Mar 2022 00:59:54 +1000
"Michael D. Setzer II via users" <users(a)lists.fedoraproject.org> wrote:
> Machine that doesn't timeout boot, before it has a similar
> saved_entry, but tried resetting it to 0 to boot from 1st
> one.
>
> grub2-editenv list
> saved_entry=0
> boot_success=1
> boot_indeterminate=0
>
> This notebook that works fine
> grub2-editenv list
> saved_entry=189711f94e78436d9618b891a8fce70e-5.16.
> 17-100.fc34.x86_64
> boot_success=1
> boot_indeterminate=0
I haven't had to examine grub for a long time. So, I'm not familiar
enough with it to say what is incorrect. What do the successful and
failing system have in
/etc/default/grub ?
I think if you put the line
GRUB_DEFAULT=saved
in that file on the failing machine, and then run
grub2-mkconfig -o grub.cfg
on the failing machine in the directory where the grub.cfg is,
it will start booting properly again. The location of grub.cfg
*should* be in /boot/grub2/ unless the machines are booting EFI. Then
the grub.cfg will be in /boot/efi/EFI/fedora. This has changed since
f34 so that grub.cfg is *always* in /boot/grub2/ now.
the default grub was exactly
the same.
Neither machine using EFI boot.
If you install / have installed pinfo, you can get lots of information
about grub by running
pinfo grub2
will take a look at pinfo. Only really reboot machine when
new kernels come out. So not a big problem, but just
strange...
Arrow keys will move around, space will move to links.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
2:32 p.m.
On 3/29/22 06:37, Michael D. Setzer II via users wrote:
Have 5 Fedora Linux machines at home. 3 with Fedora 34
and 2 with Fedora 35.
One of the Fedora 34 machines after kernel upgrade two
times ago has stopped auto booting?? Comes up with
grub menu and sits there doing nothing?
Pressing the Enter key has it boot the highlighted top
latest kernel, and it then works fine.
I haven't seen this with any of the many computers I've upgraded. Is
this EFI or BIOS boot? Look in /boot/grub2/grub.cfg and see if there is
a "set timeout=5" section somewhat near the top.
5:11 p.m.
On 29 Mar 2022 at 12:32, Samuel Sieb wrote:
Date sent: Tue, 29 Mar 2022 12:32:43 -0700
Subject: Re: Have one of 5 machines that no longer
autoboots??
To: users(a)lists.fedoraproject.org
From: Samuel Sieb <samuel(a)sieb.net>
Send reply to: Community support for Fedora
users <users(a)lists.fedoraproject.org>
On 3/29/22 06:37, Michael D. Setzer II via users wrote:
> Have 5 Fedora Linux machines at home. 3 with Fedora 34
> and 2 with Fedora 35.
> One of the Fedora 34 machines after kernel upgrade two
> times ago has stopped auto booting?? Comes up with
> grub menu and sits there doing nothing?
> Pressing the Enter key has it boot the highlighted top
> latest kernel, and it then works fine.
I haven't seen this with any of the many computers I've upgraded. Is
this EFI or BIOS boot? Look in /boot/grub2/grub.cfg and see if there is
a "set timeout=5" section somewhat near the top.
In looking at stuff
found something strange?
Don't recall any machine setup with efi boot, but found
this?
On the machine that doesn't boot
/boot/grub.env has
# GRUB Environment Block
# WARNING: Do not edit this file by tools other than grub-editenv!!!
saved_entry=0
boot_success=1
boot_indeterminate=0
/boot/efi/EFI/fedora has
# GRUB Environment Block
saved_entry=be4e5629d05040d192af245eeace0de2-5.14.12-100.fc33.x86_64
boot_success=0
kernelopts=root=UUID=a6fe5146-7a91-4f6d-ad5f-b04f68d46316 ro
resume=UUID=bb597a53-7ccc-44b5-bf2c-9ebc40564f7f rhgb quiet
boot_indeterminate=1
Not sure what created that resume option, or why it
would cause a change in boot, since it isn't EFI??
Machine that isn't auto booting has
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2099199 2097152 1G 83 Linux
/dev/sda2 2099200 17498111 15398912 7.3G 82 Linux swap / Solaris
/dev/sda3 17498112 164298751 146800640 70G 83 Linux
/dev/sda4 164298752 976773119 812474368 387.4G 5 Extended
/dev/sda5 164300800 976773119 812472320 387.4G 83 Linux
So don't see an EFI partition?
On this noteboot
/boot/grub2/grubenv has
# GRUB Environment Block
# WARNING: Do not edit this file by tools other than grub-editenv!!!
saved_entry=189711f94e78436d9618b891a8fce70e-5.16.17-100.fc34.x86_64
boot_success=1
boot_indeterminate=0
/boot/efi/EFI/fedora has
# GRUB Environment Block
saved_entry=189711f94e78436d9618b891a8fce70e-5.14.12-100.fc33.x86_64
boot_success=0
boot_indeterminate=1
kernelopts=root=UUID=12b58c6d-c9f1-4ffe-ba7a-aa816f762ba3 ro rhgb quiet
Original response I had started before I notice
boot/efi/EFI/fedora/grubenv issue??
Thanks.
Bios boot on all 5 machines.
terminal_output console
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style
feature is
# unavailable.
else
set timeout=5
fi
The grub.cfg file between two machines is identicle
between two machines with exception of one machine
having msdos5 instead of msdos1 because notebook
original had windows 7 partition, and windows 7 boot
option.
Only other difference are lines theses a6fe.. and 8410..
lines.
set kernelopts="root=UUID=a6fe5146-7a91-4f6d-ad5f-b04f68d46316 ro rhgb quiet
"
search --no-floppy --fs-uuid --set=root 8410d98a-36ea-4189-80e0-8cd00f2eec66
The rest in the grub.cfg same.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
9:52 p.m.
Got it working, but no clue what did it??
Had booted and just got menu list again.
Then went to grub command prompt and echo timeout
value and nothing showed? So set it to 5, and then did
exit.
It then went back to menu, but did the timeout, but then
it got in some loop? So had to hard reset it.
Then it seemed to boot, but grubenv had saved value as
0.
Found instructions to reset saved entry, but they didn't
work, since they were getting menu enter from grub.cfg,
which no longer has the kernel entries.
Did this to set the grubenv to list the latest kernel.
Don't know if this would always work.
grub2-editenv - set saved_entry=$(ls -1
/boot/loader/entries/ | tail -n 1 | sed 's/.conf//')
But now grubenv has this as beginning lines.
cat grubenv
# GRUB Environment Block
# WARNING: Do not edit this file by tools other than
grub-editenv!!!
saved_entry=be4e5629d05040d192af245eeace0de2-5.16.
17-100.fc34.x86_64
boot_success=1
boot_indeterminate=0
Noticed in a number of places it still shows grub- instead
of the grub2-
Did also notice that sometimes shows boot_success=0
right after boot, but then it changes to the =1??
On 29 Mar 2022 at 12:32, Samuel Sieb wrote:
Date sent: Tue, 29 Mar 2022 12:32:43 -0700
Subject: Re: Have one of 5 machines that no longer
autoboots??
To: users(a)lists.fedoraproject.org
From: Samuel Sieb <samuel(a)sieb.net>
Send reply to: Community support for Fedora
users <users(a)lists.fedoraproject.org>
On 3/29/22 06:37, Michael D. Setzer II via users wrote:
> Have 5 Fedora Linux machines at home. 3 with Fedora 34
> and 2 with Fedora 35.
> One of the Fedora 34 machines after kernel upgrade two
> times ago has stopped auto booting?? Comes up with
> grub menu and sits there doing nothing?
> Pressing the Enter key has it boot the highlighted top
> latest kernel, and it then works fine.
I haven't seen this with any of the many computers I've upgraded. Is
this EFI or BIOS boot? Look in /boot/grub2/grub.cfg and see if there is
a "set timeout=5" section somewhat near the top.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
766
days inactive
767
days old
7 comments
4 participants
participants (4)
-
Michael D. Setzer II -
Samuel Sieb -
stan -
Tom Horsley