Not sure if that is intentional, but if I am not mistaken, boot menu used to be hidden if there were no issues, but it seems to be always on ATM. Is this intentional?
Vít
On Mon, Sep 6 2021 at 05:13:59 PM +0200, Vít Ondruch vondruch@redhat.com wrote:
Is this intentional?
No, please report a bug. Thanks.
On 06/09/2021 17:13, Vít Ondruch wrote:
Not sure if that is intentional, but if I am not mistaken, boot menu used to be hidden if there were no issues, but it seems to be always on ATM. Is this intentional?
Btw, /boot on BTRFS with GRUB menu hiding will cause breakages with an "sparse file not allowed" error.
Bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1955901
Hi,
On 9/6/21 5:13 PM, Vít Ondruch wrote:
Not sure if that is intentional, but if I am not mistaken, boot menu used to be hidden if there were no issues, but it seems to be always on ATM. Is this intentional?
What is the output of running:
sudo grub2-editenv - list
Also is this a multi-boot system, or does grub at least think it is a multiboot system? IOW does your grub-menu have a "Windows" boot entry?
On multiboot systems the menu is always shown so that you can pick Windows at boot.
Regards,
Hans
Dne 07. 09. 21 v 9:26 Hans de Goede napsal(a):
Hi,
On 9/6/21 5:13 PM, Vít Ondruch wrote:
Not sure if that is intentional, but if I am not mistaken, boot menu used to be hidden if there were no issues, but it seems to be always on ATM. Is this intentional?
What is the output of running:
sudo grub2-editenv - list
~~~ $ sudo grub2-editenv - list boot_success=1 boot_indeterminate=0 saved_entry=ec300db9bfdf4776bc07b7f4281374a5-5.14.1-300.fc35.x86_64
$ uname -a Linux localhost.localdomain 5.14.1-300.fc35.x86_64 #1 SMP Fri Sep 3 16:27:33 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ~~~
Also is this a multi-boot system, or does grub at least think it is a multiboot system? IOW does your grub-menu have a "Windows" boot entry?
No, it is not, never was, never will be.
I have reported this against grub2:
https://bugzilla.redhat.com/show_bug.cgi?id=2001885
Vít
On multiboot systems the menu is always shown so that you can pick Windows at boot.
Regards,
Hans
Hi,
On 9/7/21 1:34 PM, Vít Ondruch wrote:
Dne 07. 09. 21 v 9:26 Hans de Goede napsal(a):
Hi,
On 9/6/21 5:13 PM, Vít Ondruch wrote:
Not sure if that is intentional, but if I am not mistaken, boot menu used to be hidden if there were no issues, but it seems to be always on ATM. Is this intentional?
What is the output of running:
sudo grub2-editenv - list
$ sudo grub2-editenv - list boot_success=1 boot_indeterminate=0 saved_entry=ec300db9bfdf4776bc07b7f4281374a5-5.14.1-300.fc35.x86_64 $ uname -a Linux localhost.localdomain 5.14.1-300.fc35.x86_64 #1 SMP Fri Sep 3 16:27:33 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Ok, so for some reason this is missing the "menu_auto_hide=1" setting.
You can fix this by running:
sudo grub2-editenv - set menu_auto_hide=1
The question is why anaconda did not do this though. How did you install this system?
I have reported this against grub2:
I've added the same comment there.
Regards,
Hans
On Wed, 2021-09-08 at 09:21 +0200, Hans de Goede wrote:
Hi,
On 9/7/21 1:34 PM, Vít Ondruch wrote:
Dne 07. 09. 21 v 9:26 Hans de Goede napsal(a):
Hi,
On 9/6/21 5:13 PM, Vít Ondruch wrote:
Not sure if that is intentional, but if I am not mistaken, boot menu used to be hidden if there were no issues, but it seems to be always on ATM. Is this intentional?
What is the output of running:
sudo grub2-editenv - list
$ sudo grub2-editenv - list boot_success=1 boot_indeterminate=0 saved_entry=ec300db9bfdf4776bc07b7f4281374a5-5.14.1-300.fc35.x86_64 $ uname -a Linux localhost.localdomain 5.14.1-300.fc35.x86_64 #1 SMP Fri Sep 3 16:27:33 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Ok, so for some reason this is missing the "menu_auto_hide=1" setting.
You can fix this by running:
sudo grub2-editenv - set menu_auto_hide=1
The question is why anaconda did not do this though. How did you install this system?
If I try to do this I get an error: # grub2-editenv - set menu_auto_hide=1 grub2-editenv: error: environment block too small.
What the issue here ? (This machine has been installed a while ago, and then upgraded over time)
Simo.
I have reported this against grub2:
I've added the same comment there.
Regards,
Hans _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
V Wed, Sep 08, 2021 at 09:01:42AM -0400, Simo Sorce napsal(a):
If I try to do this I get an error: # grub2-editenv - set menu_auto_hide=1 grub2-editenv: error: environment block too small.
What the issue here ?
Perhaps /boot/grub2/grubenv is corrupted and grub2-editenv is not very good at reporting errors. This happens when the file was accidentally truncated. Does it have 1024-byte size?
If it does not, back up the file and reinitilize it with "grub2-editenv - create" and then insert the original values with "grub2-editenv - set ...". If you don't have UEFI system, you will need to reistall grub in MBR to locate the new file's position on a block device and write the position into the newly installed loader.
-- Petr
On Wed, 2021-09-08 at 15:23 +0200, Petr Pisar wrote:
V Wed, Sep 08, 2021 at 09:01:42AM -0400, Simo Sorce napsal(a):
If I try to do this I get an error: # grub2-editenv - set menu_auto_hide=1 grub2-editenv: error: environment block too small.
What the issue here ?
Perhaps /boot/grub2/grubenv is corrupted and grub2-editenv is not very good at reporting errors. This happens when the file was accidentally truncated. Does it have 1024-byte size?
It is exactly 1024 bytes in size. With a ton of # characters in the tail.
If it does not, back up the file and reinitilize it with "grub2-editenv - create" and then insert the original values with "grub2-editenv - set ...". If you don't have UEFI system, you will need to reistall grub in MBR to locate the new file's position on a block device and write the position into the newly installed loader.
-- Petr _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Dne 08. 09. 21 v 15:23 Petr Pisar napsal(a):
V Wed, Sep 08, 2021 at 09:01:42AM -0400, Simo Sorce napsal(a):
If I try to do this I get an error: # grub2-editenv - set menu_auto_hide=1 grub2-editenv: error: environment block too small.
What the issue here ?
Perhaps /boot/grub2/grubenv is corrupted and grub2-editenv is not very good at reporting errors. This happens when the file was accidentally truncated. Does it have 1024-byte size?
If it does not, back up the file and reinitilize it with "grub2-editenv - create"
Why it does not contain the `menu_auto_hide=1` by default when running this command?? :/
Vít
and then insert the original values with "grub2-editenv - set ...". If you don't have UEFI system, you will need to reistall grub in MBR to locate the new file's position on a block device and write the position into the newly installed loader.
-- Petr
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
V Wed, Sep 08, 2021 at 05:34:42PM +0200, Vít Ondruch napsal(a):
Dne 08. 09. 21 v 15:23 Petr Pisar napsal(a):
V Wed, Sep 08, 2021 at 09:01:42AM -0400, Simo Sorce napsal(a):
If I try to do this I get an error: # grub2-editenv - set menu_auto_hide=1 grub2-editenv: error: environment block too small.
What the issue here ?
Perhaps /boot/grub2/grubenv is corrupted and grub2-editenv is not very good at reporting errors. This happens when the file was accidentally truncated. Does it have 1024-byte size?
If it does not, back up the file and reinitilize it with "grub2-editenv - create"
Why it does not contain the `menu_auto_hide=1` by default when running this command?? :/
Because this how upstream works. From the manual:
COMMANDS create Create a blank environment block file.
-- Petr
Dne 09. 09. 21 v 8:25 Petr Pisar napsal(a):
V Wed, Sep 08, 2021 at 05:34:42PM +0200, Vít Ondruch napsal(a):
Dne 08. 09. 21 v 15:23 Petr Pisar napsal(a):
V Wed, Sep 08, 2021 at 09:01:42AM -0400, Simo Sorce napsal(a):
If I try to do this I get an error: # grub2-editenv - set menu_auto_hide=1 grub2-editenv: error: environment block too small.
What the issue here ?
Perhaps /boot/grub2/grubenv is corrupted and grub2-editenv is not very good at reporting errors. This happens when the file was accidentally truncated. Does it have 1024-byte size?
If it does not, back up the file and reinitilize it with "grub2-editenv - create"
Why it does not contain the `menu_auto_hide=1` by default when running this command?? :/
Because this how upstream works. From the manual:
COMMANDS create Create a blank environment block file.
You took the question too literally, while my whine was more figurative.
Initially, I was going to answer this:
IOW I don't think this is good default and even if this might be considered good default for upstream (because from upstream POV, the empty file is sufficient), it is not good default for Fedora IMO. In Fedora, the output of such (or similar) command should already include `menu_auto_hide=1`.
But thinking about this more, I think my biggest pet peeve with this issue is that there is no simple way to reset to Fedora default. Would the system boot without the `/boot/grub2/grubenv` file? I hope so. So can I delete it to fix the issue at hand? I can't. Can I recreate the file? I can't. Can I reinstall some package to fix the issue? I can't. I don't know how else should I figure that I am supposed to put `menu_auto_hide=1` somewhere to get the Fedora experience back?
Vít
FYI: I recreated the file anyway and it works now.
The difference seem to be that there is a new second comment line at the top of the file about not modifying it.
Was the format changed and no update scriplet provided at some point ?
Simo.
On Wed, 2021-09-08 at 15:23 +0200, Petr Pisar wrote:
V Wed, Sep 08, 2021 at 09:01:42AM -0400, Simo Sorce napsal(a):
If I try to do this I get an error: # grub2-editenv - set menu_auto_hide=1 grub2-editenv: error: environment block too small.
What the issue here ?
Perhaps /boot/grub2/grubenv is corrupted and grub2-editenv is not very good at reporting errors. This happens when the file was accidentally truncated. Does it have 1024-byte size?
If it does not, back up the file and reinitilize it with "grub2-editenv - create" and then insert the original values with "grub2-editenv - set ...". If you don't have UEFI system, you will need to reistall grub in MBR to locate the new file's position on a block device and write the position into the newly installed loader.
-- Petr _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure