GRUB_TIMEOUT in /etc/default/grub not changing the wait time with LVM












1















First of all: YES, I did the update-grub after changing the value.



After a new install of Ubuntu 18.10 on an empty disk the wait time at the grub menu is of 30 seconds (half an eternity!).



The line GRUB_TIMEOUT in /etc/default/grub had a value of 0. Changing this to 10 did not change the wait time, it was still 30 seconds.



Any ideas?










share|improve this question

























  • Do you have root on LVM or btrfs?

    – Pilot6
    10 hours ago











  • @Pilot6 I have LVM, the file systems are ext4.

    – muclux
    10 hours ago











  • This is by design, I will post an answer.

    – Pilot6
    10 hours ago
















1















First of all: YES, I did the update-grub after changing the value.



After a new install of Ubuntu 18.10 on an empty disk the wait time at the grub menu is of 30 seconds (half an eternity!).



The line GRUB_TIMEOUT in /etc/default/grub had a value of 0. Changing this to 10 did not change the wait time, it was still 30 seconds.



Any ideas?










share|improve this question

























  • Do you have root on LVM or btrfs?

    – Pilot6
    10 hours ago











  • @Pilot6 I have LVM, the file systems are ext4.

    – muclux
    10 hours ago











  • This is by design, I will post an answer.

    – Pilot6
    10 hours ago














1












1








1








First of all: YES, I did the update-grub after changing the value.



After a new install of Ubuntu 18.10 on an empty disk the wait time at the grub menu is of 30 seconds (half an eternity!).



The line GRUB_TIMEOUT in /etc/default/grub had a value of 0. Changing this to 10 did not change the wait time, it was still 30 seconds.



Any ideas?










share|improve this question
















First of all: YES, I did the update-grub after changing the value.



After a new install of Ubuntu 18.10 on an empty disk the wait time at the grub menu is of 30 seconds (half an eternity!).



The line GRUB_TIMEOUT in /etc/default/grub had a value of 0. Changing this to 10 did not change the wait time, it was still 30 seconds.



Any ideas?







boot grub2 18.10 lvm






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 9 hours ago









Pilot6

53k15108197




53k15108197










asked 10 hours ago









mucluxmuclux

2,4361725




2,4361725













  • Do you have root on LVM or btrfs?

    – Pilot6
    10 hours ago











  • @Pilot6 I have LVM, the file systems are ext4.

    – muclux
    10 hours ago











  • This is by design, I will post an answer.

    – Pilot6
    10 hours ago



















  • Do you have root on LVM or btrfs?

    – Pilot6
    10 hours ago











  • @Pilot6 I have LVM, the file systems are ext4.

    – muclux
    10 hours ago











  • This is by design, I will post an answer.

    – Pilot6
    10 hours ago

















Do you have root on LVM or btrfs?

– Pilot6
10 hours ago





Do you have root on LVM or btrfs?

– Pilot6
10 hours ago













@Pilot6 I have LVM, the file systems are ext4.

– muclux
10 hours ago





@Pilot6 I have LVM, the file systems are ext4.

– muclux
10 hours ago













This is by design, I will post an answer.

– Pilot6
10 hours ago





This is by design, I will post an answer.

– Pilot6
10 hours ago










1 Answer
1






active

oldest

votes


















0














Recently a patch has been merged fixing grub timeout menu to 30 seconds for UEFI systems with /boot on lvm or btrfs.



The reason for that in some cases a user can't access boot menu. grub can't write to lvm or btrfs.



See this bug report for more details.



If you look into grub.cfg, you'll see this:



if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
if [ $grub_platform = efi ]; then
set timeout=30
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi


You can change it manually, but it will be reverted on update-grub.






share|improve this answer


























  • Thank you for this fast answer. I have EFI and LVM, but /boot is the only partition outside of the Volume Group. So it seems that I have to "suffer" for the benefit of those who have put /boot into LVM (or stop the wait by hitting 'ENTER').

    – muclux
    9 hours ago













  • I have to suffer too with boot on btrfs. It makes no sense for me, but this is not my decision.

    – Pilot6
    9 hours ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1123290%2fgrub-timeout-in-etc-default-grub-not-changing-the-wait-time-with-lvm%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Recently a patch has been merged fixing grub timeout menu to 30 seconds for UEFI systems with /boot on lvm or btrfs.



The reason for that in some cases a user can't access boot menu. grub can't write to lvm or btrfs.



See this bug report for more details.



If you look into grub.cfg, you'll see this:



if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
if [ $grub_platform = efi ]; then
set timeout=30
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi


You can change it manually, but it will be reverted on update-grub.






share|improve this answer


























  • Thank you for this fast answer. I have EFI and LVM, but /boot is the only partition outside of the Volume Group. So it seems that I have to "suffer" for the benefit of those who have put /boot into LVM (or stop the wait by hitting 'ENTER').

    – muclux
    9 hours ago













  • I have to suffer too with boot on btrfs. It makes no sense for me, but this is not my decision.

    – Pilot6
    9 hours ago
















0














Recently a patch has been merged fixing grub timeout menu to 30 seconds for UEFI systems with /boot on lvm or btrfs.



The reason for that in some cases a user can't access boot menu. grub can't write to lvm or btrfs.



See this bug report for more details.



If you look into grub.cfg, you'll see this:



if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
if [ $grub_platform = efi ]; then
set timeout=30
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi


You can change it manually, but it will be reverted on update-grub.






share|improve this answer


























  • Thank you for this fast answer. I have EFI and LVM, but /boot is the only partition outside of the Volume Group. So it seems that I have to "suffer" for the benefit of those who have put /boot into LVM (or stop the wait by hitting 'ENTER').

    – muclux
    9 hours ago













  • I have to suffer too with boot on btrfs. It makes no sense for me, but this is not my decision.

    – Pilot6
    9 hours ago














0












0








0







Recently a patch has been merged fixing grub timeout menu to 30 seconds for UEFI systems with /boot on lvm or btrfs.



The reason for that in some cases a user can't access boot menu. grub can't write to lvm or btrfs.



See this bug report for more details.



If you look into grub.cfg, you'll see this:



if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
if [ $grub_platform = efi ]; then
set timeout=30
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi


You can change it manually, but it will be reverted on update-grub.






share|improve this answer















Recently a patch has been merged fixing grub timeout menu to 30 seconds for UEFI systems with /boot on lvm or btrfs.



The reason for that in some cases a user can't access boot menu. grub can't write to lvm or btrfs.



See this bug report for more details.



If you look into grub.cfg, you'll see this:



if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
if [ $grub_platform = efi ]; then
set timeout=30
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi


You can change it manually, but it will be reverted on update-grub.







share|improve this answer














share|improve this answer



share|improve this answer








edited 9 hours ago

























answered 9 hours ago









Pilot6Pilot6

53k15108197




53k15108197













  • Thank you for this fast answer. I have EFI and LVM, but /boot is the only partition outside of the Volume Group. So it seems that I have to "suffer" for the benefit of those who have put /boot into LVM (or stop the wait by hitting 'ENTER').

    – muclux
    9 hours ago













  • I have to suffer too with boot on btrfs. It makes no sense for me, but this is not my decision.

    – Pilot6
    9 hours ago



















  • Thank you for this fast answer. I have EFI and LVM, but /boot is the only partition outside of the Volume Group. So it seems that I have to "suffer" for the benefit of those who have put /boot into LVM (or stop the wait by hitting 'ENTER').

    – muclux
    9 hours ago













  • I have to suffer too with boot on btrfs. It makes no sense for me, but this is not my decision.

    – Pilot6
    9 hours ago

















Thank you for this fast answer. I have EFI and LVM, but /boot is the only partition outside of the Volume Group. So it seems that I have to "suffer" for the benefit of those who have put /boot into LVM (or stop the wait by hitting 'ENTER').

– muclux
9 hours ago







Thank you for this fast answer. I have EFI and LVM, but /boot is the only partition outside of the Volume Group. So it seems that I have to "suffer" for the benefit of those who have put /boot into LVM (or stop the wait by hitting 'ENTER').

– muclux
9 hours ago















I have to suffer too with boot on btrfs. It makes no sense for me, but this is not my decision.

– Pilot6
9 hours ago





I have to suffer too with boot on btrfs. It makes no sense for me, but this is not my decision.

– Pilot6
9 hours ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1123290%2fgrub-timeout-in-etc-default-grub-not-changing-the-wait-time-with-lvm%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

GameSpot

日野市

Tu-95轟炸機