Grub header lsefi not working causing delayed grub menu

[oshunluvr]

You should have this package version:

stuart@Precision7730:~$ dpkg -l |grep grub-common | awk '{ print $3 }'
2.02-2ubuntu8.12

[oshunluvr]

Did you run sudo update-grub after updating the package?

[mr_raider]

It seems to have solved nothing for me on my installs. I still get a 30 second countdown unless I put a GRUB_RECORDFAIL_TIMEOUT value in /etc/default/grub

Am I missing something?

[Qqmike]

Yeah, that was quick. Very nice of them!

[oshunluvr]

Bug identified and squashed.

https://bugs.launchpad.net/ubuntu/+s...2/+bug/1814403

[oshunluvr]

You can go here and click "This bug effects you"

[oshunluvr]

A little more research here. After trying several different recordfail settings in grubenv, I pulled the grub.cfg from my older 16.04 install and compared it to my current one. I discovered a paragraph in 00_header in 18.04 that is not in 16.04:

[FONT=monospace][COLOR=#000000]if lsefi; then[/COLOR]
  set timeout=30 
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
  fi
fi[/FONT]

Note "timeout=30" which is the same as the recordfail timeout. As a test, I edited /boot/grub/grub.cfg and changed the 30 to 17 and sure enough, that's the source of the log timeout.

Here's the paragraph from 00_header:

if lsefi; then  set timeout=${GRUB_RECORDFAIL_TIMEOUT:-30}
  if [ x\$feature_timeout_style = xy ] ; then
    set timeout_style=menu
  fi
fi

One odd thing is the 00_header file is from Jan 9th but this bug has just appeared so it must be related to grub-common not the the header file.

Still looking for answers...

[mr_raider]

I've got the same issue. It affects any 18.04 based install, and seems to have been introduced by arecent grub update.

[oshunluvr]

Yeah, I've gone through most of those. I know I can shorten the recordfail timeout in default/grub but I was hoping to just make it work right again.

Could be a bug, but if no one else is seeing it, more likely something here.

[Qqmike]

Never gave grubenv much thought until reading your post. Checked my /boot/grub/grubenv and it is this:

# GRUB Environment Block
#######################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################

Googled this, and got the following, although many older posts but some might indicate diagnostic ideas:
https://www.google.com/search?client...utf-8&oe=utf-8

Sorry, I'm not much help here.

[oshunluvr]

This morning I rebooted and casually noticed my boot time out for the grub menu was 30 seconds - a number I have set at 3. A couple minutes looking and I discovered (or at least it appears) that grub is defaulting to the "recordfail" timeout time which is 30 seconds. That means - or should mean - that grubenv has recordfail set to "true".

I have re-created the grubenv several times, compared the current one to another I have which does not do this, and verified the variable is not set. Nothing seems to change it.

Anyone else seeing this?

EDIT: See later posts. Turns out to be related to a function in grub 00_header file