GRUB Timeout - LM20 & LM20.1

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

I have been searching for ages but can't find the answer, sorry.

My Mint Cinnamon start-up includes a 30s delay on (what I presume is) the GRUB menu: default to start normally, or a couple of fallback options. 30s? Really?

Search hits say...

Code: Select all

gksudo xed /etc/default/grub
...to adjust the timeout, but the first problem is gksudo doesn't exist! Eventually I found an alternative:

Code: Select all

xed admin:///etc/default/grub
...so I would appreciate comments on the correct way to edit system files in a graphical environment.

Having got to /etc/default/grub though, nothing there corresponds with a 30s timeout:

Code: Select all

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
For reference (somebody is bound to ask), inxi output:

Code: Select all

$ inxi -Fxxxrz
System:
  Kernel: 5.4.0-70-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B350-F GAMING v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 5406 date: 11/13/2019 
CPU:
  Topology: 6-Core model: AMD Ryzen 5 1600 bits: 64 type: MT MCP arch: Zen 
  rev: 1 L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 76645 
  Speed: 1375 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 
  1: 1375 2: 1375 3: 1372 4: 1375 5: 1375 6: 1373 7: 1373 8: 1374 9: 1375 
  10: 1375 11: 1375 12: 1372 
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI 
  driver: nvidia v: 450.102.04 bus ID: 08:00.0 chip ID: 10de:128b 
  Display: x11 server: X.Org 1.20.9 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 3840x2160~60Hz 
  OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 450.102.04 
  direct render: Yes 
Audio:
  Device-1: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 08:00.1 chip ID: 10de:0e0f 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 0b:00.3 chip ID: 1022:1457 
  Sound Server: ALSA v: k5.4.0-70-generic 
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb 
  v: 5.6.0-k port: e000 bus ID: 03:00.0 chip ID: 8086:1539 
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 3.87 TiB used: 541.26 GiB (13.7%) 
  ID-1: /dev/sda model: RAID_B size: 1.36 TiB speed: <unknown> serial: N/A 
  rev: V1.0 scheme: GPT 
  ID-2: /dev/sdb model: RAID_A size: 1.82 TiB speed: <unknown> serial: N/A 
  rev: V1.0 scheme: GPT 
  ID-3: /dev/sdc vendor: OCZ model: VECTOR size: 238.47 GiB speed: 6.0 Gb/s 
  serial: <filter> rev: 2.0 scheme: GPT 
  ID-4: /dev/sdd vendor: Seagate model: ST3500312CS size: 465.76 GiB 
  speed: 1.5 Gb/s rotation: 5900 rpm serial: <filter> rev: SC13 scheme: GPT 
RAID:
  Hardware-1: Adaptec Series 6 - 6G SAS/PCIe 2 driver: aacraid 
  v: 1.2.1[50877]-custom port: d000 bus ID: 09:00.0 chip ID: 9005.028b 
  rev: 01 
Partition:
  ID-1: / size: 237.97 GiB used: 12.71 GiB (5.3%) fs: btrfs dev: /dev/sdc2 
  ID-2: /home size: 1.79 TiB used: 85.41 GiB (4.7%) fs: ext4 dev: /dev/sdb1 
  ID-3: /tmp size: 439.12 GiB used: 72.1 MiB (0.0%) fs: ext4 dev: /dev/sdd2 
  ID-4: swap-1 size: 18.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdd1 
Sensors:
  System Temperatures: cpu: 36.4 C mobo: N/A gpu: nvidia temp: 70 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 60% 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
  Processes: 324 Uptime: 43m Memory: 15.63 GiB used: 1.69 GiB (10.8%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
senjoz
Level 5
Level 5
Posts: 890
Joined: Tue Jun 09, 2020 3:55 am
Location: Kamnik

Re: GRUB Timeout - LM20 & LM20.1

Post by senjoz »

Make Grub menu visible for a few seconds with GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=5 and make boot messages visible with GRUB_CMDLINE_LINUX_DEFAULT="". Update Grub with sudo update-grub, restart and see if you can identify where 30 seconds delay is.

Regards, Jože
User avatar
JOPETA
Level 17
Level 17
Posts: 7762
Joined: Thu Nov 20, 2014 6:10 am
Location: En un lugar de cuyo nombre no quiero acordarme

Re: GRUB Timeout - LM20 & LM20.1

Post by JOPETA »

Dark Owl wrote: Sun Apr 18, 2021 2:37 am Having got to /etc/default/grub though, nothing there corresponds with a 30s timeout:
That is not the file where to look but there you can change default grub option as time-out. as senjoz indicates.

Those delays are defined in GRUB executables scriipts in /etc/grub.d . If you look inside 00_header (cat /etc/grub.d/00_header) you can see them in time-out section.

Also you can see then in /boot/grub/grub.cfg (cat /boot/grub/grub.cfg) executable sections ( 00_header), as this file is created when running sudo update-grub. Run that code a see if there is something wrong (errors or warnings)

When GRUB menu shows discount/delay differents than fixed in that /etc/default/grub, and no error result in last code, then something went wrong when charging GRUB menu. In my case there is no such problems, timeout is set to 5 seconds in default grub file and it is shown in GRUB menu.
if [ "${recordfail}" = 1 ] ; then
set timeout=30

else
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
fi
Last edited by JOPETA on Mon Apr 19, 2021 4:07 am, edited 2 times in total.
Ni cola de león ni cabeza de ratón, prefiero ser diente de ajo.(Javier Krahe)
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

JOPETA wrote: Sun Apr 18, 2021 4:07 am

Code: Select all

if [ "${recordfail}" = 1 ] ; then
  set timeout=30
So this is saying some kind of "recordfail" is causing the 30s delay? And if I do this:
senjoz wrote: Sun Apr 18, 2021 3:57 am Make Grub menu visible for a few seconds with GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=5 and make boot messages visible with GRUB_CMDLINE_LINUX_DEFAULT="". Update Grub with sudo update-grub, restart and see if you can identify where 30 seconds delay is.
...it will tell me what the "recordfail" is? I'll give it a try.

Can I assume other people don't have this problem and it's something to do with when I installed the LM20β?
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

The modifications have made no difference, other than to throw up screenfuls of (what looks like) dmesg text after the 30s timeout. I made a video so I could refer back to the sequence of events:

1. Hardware RAID boot screen (~30s);
2. Motherboard boot screen (~5s);
3. GRUB(?) boot menu with 30s timeout:
Linux Mint 20.1 Cinnamon
Advanced options for Linux Mint 20.1 Cinnamon
UEFI Firmware Settings
-----------------
enter: boot, 'e': options, 'c': cmd-line
4. dmesg-like scrolling text;
5. Mint graphical login screen.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Larry78723
Level 14
Level 14
Posts: 5479
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: GRUB Timeout - LM20 & LM20.1

Post by Larry78723 »

It sounds like you might have a mismatch in your fstab file. Please post the results of the following commands:

Code: Select all

lsblk -f

Code: Select all

cat /etc/fstab
Image
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
User avatar
JOPETA
Level 17
Level 17
Posts: 7762
Joined: Thu Nov 20, 2014 6:10 am
Location: En un lugar de cuyo nombre no quiero acordarme

Re: GRUB Timeout - LM20 & LM20.1

Post by JOPETA »

You can try also adding GRUB_RECORDFAIL_TIMEOUT=5 line to /etc/default/grub, save file and run sudo update-grub. Post back this code result.

If it is recordfail variable it would reduce delay from 30 to that 5 seconds, but maybe it is intentioned as stated here in certain installations (only one system installed in UEFI mode in a RAID array or LVM). Did you find something as follow in cat /boot/grub/grub.cfg ?
if [ $grub_platform = efi ]; then
set timeout=30
Any way some details are need as per Larry's post also dpkg -l grub-*.
Last edited by JOPETA on Wed Apr 21, 2021 2:04 am, edited 1 time in total.
Ni cola de león ni cabeza de ratón, prefiero ser diente de ajo.(Javier Krahe)
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

Thanks both:

Code: Select all

owl@ZEN:~$ lsblk -f
NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                   
└─sda1
     ext4         aa1e1fc1-237a-4b3c-ae2d-9560cba4a033  669.6G    46% /media/owl
sdb                                                                   
└─sdb1
     ext4         f89f16f9-457d-43a5-bcb3-250ce00a53bc    1.6T     5% /home
sdc                                                                   
├─sdc1
│    vfat         4EA2-A177                             503.1M     2% /boot/efi
└─sdc2
     btrfs        2deb10f5-283c-4e56-9fc7-ca510fac3f60  224.6G     5% /run/times
sdd                                                                   
├─sdd1
│    swap         ca366817-fc8f-4d07-a15d-447ce8a2269e                [SWAP]
└─sdd2
     ext4         1814bc93-d087-4a14-ae84-74421b1cbc80  416.7G     0% /tmp
sr0                                                                   

Code: Select all

owl@ZEN:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc2 during installation
UUID=2deb10f5-283c-4e56-9fc7-ca510fac3f60 /               btrfs   defaults,subvol=@ 0       1
# /boot/efi was on /dev/sdc1 during installation
UUID=4EA2-A177  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sdb1 during installation
UUID=f89f16f9-457d-43a5-bcb3-250ce00a53bc /home           ext4    defaults        0       2
# /tmp was on /dev/sdd2 during installation
UUID=1814bc93-d087-4a14-ae84-74421b1cbc80 /tmp            ext4    defaults        0       2
# swap was on /dev/sdd1 during installation
UUID=ca366817-fc8f-4d07-a15d-447ce8a2269e none            swap    sw              0       0

Code: Select all

owl@ZEN:~$ dpkg -l grub-*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                  Version                   Architecture Description
+++-=====================-=========================-============-==============>
un  grub-cloud-amd64      <none>                    <none>       (no descriptio>
ii  grub-common           2.04-1ubuntu26.9          amd64        GRand Unified >
un  grub-coreboot         <none>                    <none>       (no descriptio>
un  grub-doc              <none>                    <none>       (no descriptio>
un  grub-efi              <none>                    <none>       (no descriptio>
un  grub-efi-amd64        <none>                    <none>       (no descriptio>
ii  grub-efi-amd64-bin    2.04-1ubuntu26.9          amd64        GRand Unified >
ii  grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9 amd64        GRand Unified >
un  grub-efi-arm          <none>                    <none>       (no descriptio>
un  grub-efi-arm64        <none>                    <none>       (no descriptio>
un  grub-efi-arm64-signed <none>                    <none>       (no descriptio>
un  grub-efi-ia32         <none>                    <none>       (no descriptio>
un  grub-efi-ia64         <none>                    <none>       (no descriptio>
un  grub-emu              <none>                    <none>       (no descriptio>
ii  grub-gfxpayload-lists 0.7                       amd64        GRUB gfxpayloa>
un  grub-ieee1275         <none>                    <none>       (no descriptio>
un  grub-legacy           <none>                    <none>       (no descriptio>
un  grub-legacy-doc       <none>                    <none>       (no descriptio>
un  grub-linuxbios        <none>                    <none>       (no descriptio>
ii  grub-pc               2.04-1ubuntu26.9          amd64        GRand Unified >
ii  grub-pc-bin           2.04-1ubuntu26.9          amd64        GRand Unified >
un  grub-uboot            <none>                    <none>       (no descriptio>
un  grub-xen              <none>                    <none>       (no descriptio>
un  grub-yeeloong         <none>                    <none>       (no descriptio>
lines 7-29/29 (END)
JOPETA wrote: Tue Apr 20, 2021 10:42 am Did you find somethig as follow in cat /boot/grub/grub.cfg ?
Yes:

Code: Select all

if [ $grub_platform = efi ]; then
  set timeout=30
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
  fi
fi
It strikes me that is the culprit. (Update: no it doesn't - see next post)
JOPETA wrote: Tue Apr 20, 2021 10:42 am You can try also adding GRUB_RECORDFAIL_TIMEOUT=5 line to /etc/default/grub, save file and run sudo update-grub. Post back this code result.
Will do, results to follow. BTW: how are you managing to insert inline code boxes in your posts? I can only find a tool for stand-alone code boxes.
JOPETA wrote: Tue Apr 20, 2021 10:42 amdeliverated
What does that mean??
Last edited by Dark Owl on Wed Apr 21, 2021 2:38 am, edited 1 time in total.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

JOPETA wrote: Tue Apr 20, 2021 10:42 am You can try also adding GRUB_RECORDFAIL_TIMEOUT=5 line to /etc/default/grub, save file and run sudo update-grub. Post back this code result.
This did indeed cut the timeout to 5s.

Is this actually caused by a problem? A post in the Ubuntu forum thread you linked says:
https://ubuntuforums.org/showthread.php?t=2412153&p=13848908#post13848908 wrote:
There is no actual failure. It's a deliberately faked failure set by a script to force grub menu to appear. I think this is set only on systems with one OS, UEFI and LVM. All three must be satisfied* to trigger this.

The reasoning was that otherwise you can't get the grub menu to appear on such a system if you needed it for an advanced option (like recovery mode). Just press enter to cancel the 30 sec time delay. Boot will then continue.
...but I'm prepared to take that with a pinch of salt!

Is there any way to divert the start-up scrolling text to a file for later inspection? Within the text I have spotted one [FAILED] amongst a sea of [ OK ]:

Code: Select all

[FAILED] Failed to start VirtualBox Web Service.
...but I have no idea why, and it doesn't sound like it has any bearing anyway.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

I have found this:
https://docs.hetzner.com/robot/dedicated-server/operating-systems/deactivate-grub2-recordfail/ wrote:
GRUB2 comes with a feature that, after a failed boot attempt, during the next boot will automatically stop at the boot menu.
I am not qualified to judge the authenticity of this statement, but it does not seem unreasonable.

So, what are these "failed boot attempts"? My system boots and runs fine (after the GRUB delay). I guess it could be that this (in the scrolling boot text, which I have since turned off again):
Dark Owl wrote: Tue Apr 20, 2021 3:41 pm

Code: Select all

[FAILED] Failed to start VirtualBox Web Service.
...sets the recordfail flag for next time.

How to fix?

It's a pity GRUB isn't more explicit. A message on the GRUB menu screen would be very helpful, such as:
A fault was noted the previous time this system booted. To view the fault report see <some file or other>.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Larry78723
Level 14
Level 14
Posts: 5479
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: GRUB Timeout - LM20 & LM20.1

Post by Larry78723 »

I'm not familiar with BTRF systems but I'm curious about something I spotted in your outputs.

From your lsblk -f:

Code: Select all

sdc                                                                   
├─sdc1
│    vfat         4EA2-A177                             503.1M     2% /boot/efi
└─sdc2
     btrfs        2deb10f5-283c-4e56-9fc7-ca510fac3f60  224.6G     5% /run/times
From your fstab:

Code: Select all

# / was on /dev/sdc2 during installation
UUID=2deb10f5-283c-4e56-9fc7-ca510fac3f60 /               btrfs   defaults,subvol=@ 0       1
Here's my confusion: fstab says that UUID=2deb10f5-283c-4e56-9fc7-ca510fac3f60 is mounted at / but lsblk -f shows it mounted at /run/times. Could this be the source of the problem?
Image
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

Thanks for taking an interest.
Larry78723 wrote: Thu Apr 22, 2021 2:55 pm Could this be the source of the problem?
In as much as the GRUB boot text throws up a FAIL line as in "Failed to start VirtualBox web Service", I suggest not. If I manage to clear that particular fault but the overall problem remains, I'll come back to your suggestion.

The VirtualBox start problem is addressed in another thread: viewtopic.php?f=46&t=347813.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

I have eliminated the fail from the boot report by the simple expedient of uninstalling VirtualBox. Doing so has not altered the actual boot process, other than not to have any fail reports in the scrolling text. I have tried resetting the recordfail variable using sudo grub-editenv /boot/grub/grubenv unset recordfail, but I'm working in the dark and it made no difference.

Returning to the question of fstab, I don't know what to tell you. The btrfs partition is used by Timeshift. fstab has been generated automatically, not manually. All the various partitions and allocations were made at install time using the "other" option.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

It would be very helpful if I could capture the grub boot messages (as exposed by replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="" in /etc/default/grub and running sudo update-grub) into a file for later inspection (and publication if necessary). Searches came up with bootlogd: Daemon To Log Boot Messages.

I tried to install bootlogd using sudo apt-get install bootlogd, but all I got for my trouble was "unable to locate package bootlogd". This: Ubuntu Manpage for bootlogd seems to suggest it was only available in Ubuntu 16.04 not 20.04 (but I could be wrong).

I have tried journalctl -b, but the output does not (at first glance) appear to be the same as the scrolling stuff I get between the Grub menu and the login prompt, and neither does dmesg. I see there are boot.log.1, .2, ..., files in /var/log, but these are marked as type=binary and not amenable to being opened for viewing.

Any ideas, or am I on my own with this? To be fair, the grub menu coming up during boot doesn't actually stop me doing anything (it's just an annoyance, and less so now I have control over the timeout delay), but:
  1. If recordfail is a red herring it really shouldn't get set;
  2. If it is not a red herring, it really ought to be a lot easier to find out what the problem is.
Could it be as simple as "this system does not support being able to force the grub menu by holding shift during boot, so we'll make sure the user can always get to the boot menu if needed by fudging the recordfail flag"?
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Larry78723
Level 14
Level 14
Posts: 5479
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: GRUB Timeout - LM20 & LM20.1

Post by Larry78723 »

I suggest you proceed like this in order to post the current systemlog entries to us for inspection.

Here is how:

Reboot
Open a terminal window and maximize it.
Execute the following commandline:

Code: Select all

journalctl -b -1 | grep -i "error\|warn\|fail" | tee >(gzip --stdout > journalctl_$USER.gz)
This command will write the current system log problems to the file journalctl_(yourname).gz. The file will be located in your /home/login_name directory

Attach this file to your next reply, please.
Image
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

Larry78723 wrote: Sat Apr 24, 2021 5:58 am Reboot
Open a terminal window and maximize it.
Execute the following commandline...
Thanks :thumbsup:

The output isn't long enough to need zipping, so here it is in plain text for easy inspection (and attached as well, for good measure):

Code: Select all

Apr 24 17:43:07 ZEN kernel: tsc: Fast TSC calibration failed
Apr 24 17:43:07 ZEN kernel: RAS: Correctable Errors collector initialized.
Apr 24 17:43:08 ZEN kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Apr 24 17:43:09 ZEN systemd[1]: Starting GRUB failed boot detection...
Apr 24 17:43:09 ZEN systemd[1]: Finished GRUB failed boot detection.
Apr 24 17:43:09 ZEN thermald[1008]: [WARN]NO RAPL sysfs present
Apr 24 17:43:09 ZEN thermald[1008]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Apr 24 17:43:09 ZEN thermald[1008]: [WARN]error: could not parse file /etc/thermald/thermal-conf.xml
Apr 24 17:43:09 ZEN thermald[1008]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check
Apr 24 17:43:09 ZEN thermald[1008]: [ERR]THD engine start failed
Apr 24 17:43:09 ZEN udisksd[1010]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Apr 24 17:43:09 ZEN udisksd[1010]: Failed to load the 'mdraid' libblockdev plugin
Apr 24 17:43:09 ZEN systemd[1]: vboxweb.service: Failed with result 'protocol'.
Apr 24 17:43:09 ZEN systemd[1]: Failed to start VirtualBox Web Service.
Apr 24 17:43:09 ZEN networkd-dispatcher[1113]: WARNING: systemd-networkd is not running, output will be incomplete.
Apr 24 17:43:09 ZEN colord[1081]: failed to get session [pid 975]: No data available
Apr 24 17:43:09 ZEN colord[1081]: failed to get session [pid 975]: No data available
Apr 24 17:43:11 ZEN /slick-greeter-set-keyboard-layout[1186]: Result: Warning! Multiple definitions of keyboard model
                                                              Warning! Multiple definitions of keyboard layout
Apr 24 17:43:32 ZEN pulseaudio[1172]: Error opening PCM device hdmi:0,1: No such file or directory
Apr 24 17:43:32 ZEN pulseaudio[1172]: Error opening PCM device front:1: No such file or directory
Apr 24 17:43:33 ZEN lightdm[1608]: Error: can't open /lib/modules/5.4.0-70-generic/updates/dkms
Apr 24 17:43:33 ZEN lightdm[1608]: Error: can't open /lib/modules/5.4.0-70-generic/updates/dkms
Apr 24 17:43:33 ZEN ifdown[1636]: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
Apr 24 17:43:33 ZEN dbus-daemon[976]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
"ZEN" is the name of my system.

I'm pleased to see "Failed to start VirtualBox Web Service" is in there (although not presented in the same way as in the boot text). In case you're wondering why it's back: having proved uninstalling VirtualBox made no difference, I restored it with Timeshift.

The lines which catch my attention are Starting GRUB failed boot detection... Finished GRUB failed boot detection.

In case more detail is required, I have also attached the un-grepped dump.
Attachments
journalctl_dump.gz
(46.74 KiB) Downloaded 23 times
journalctl_owl.gz
(946 Bytes) Downloaded 26 times
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

Dark Owl wrote: Sat Apr 24, 2021 1:01 pm The lines which catch my attention are Starting GRUB failed boot detection... Finished GRUB failed boot detection.
Here's the full dump starting and ending at those lines (means nothing to me, but there's no obvious smoking gun):

Code: Select all

Apr 24 17:43:09 ZEN systemd[1]: Starting GRUB failed boot detection...
Apr 24 17:43:09 ZEN systemd-logind[1007]: New seat seat0.
Apr 24 17:43:09 ZEN dbus-daemon[976]: dbus[976]: Unknown group "power" in message bus configuration file
Apr 24 17:43:09 ZEN systemd-logind[1007]: Watching system buttons on /dev/input/event1 (Power Button)
Apr 24 17:43:09 ZEN systemd-logind[1007]: Watching system buttons on /dev/input/event0 (Power Button)
Apr 24 17:43:09 ZEN systemd-logind[1007]: Watching system buttons on /dev/input/event3 (YICHIP Wireless Device System Control)
Apr 24 17:43:09 ZEN systemd-logind[1007]: Watching system buttons on /dev/input/event4 (YICHIP Wireless Device Consumer Control)
Apr 24 17:43:09 ZEN systemd-logind[1007]: Watching system buttons on /dev/input/event5 (HS-HW156A-SE-01-00-   USB Keyboard)
Apr 24 17:43:09 ZEN systemd-logind[1007]: Watching system buttons on /dev/input/event6 (HS-HW156A-SE-01-00-   USB Keyboard Consumer Control)
Apr 24 17:43:09 ZEN systemd[1]: grub-initrd-fallback.service: Succeeded.
Apr 24 17:43:09 ZEN systemd-logind[1007]: Watching system buttons on /dev/input/event7 (HS-HW156A-SE-01-00-   USB Keyboard System Control)
Apr 24 17:43:09 ZEN systemd[1]: Finished GRUB failed boot detection.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
JOPETA
Level 17
Level 17
Posts: 7762
Joined: Thu Nov 20, 2014 6:10 am
Location: En un lugar de cuyo nombre no quiero acordarme

Re: GRUB Timeout - LM20 & LM20.1

Post by JOPETA »

Sure I'm missing someting but It looks like you have activated RAID in SATA Configuration but no array is defined so you'd better change it to SATA mode AHCI. :roll:
Last edited by JOPETA on Sat Apr 24, 2021 2:33 pm, edited 1 time in total.
Ni cola de león ni cabeza de ratón, prefiero ser diente de ajo.(Javier Krahe)
User avatar
Dark Owl
Level 5
Level 5
Posts: 553
Joined: Sat May 02, 2020 7:43 am
Location: Brit

Re: GRUB Timeout - LM20 & LM20.1

Post by Dark Owl »

JOPETA wrote: Sat Apr 24, 2021 2:09 pm It looks like you have activated RAID in SATA Configuration but no array is defined so you'd better change it to SATA mode AHCI. :roll:
I need you to be more explicit please. I have hardware RAID; the adapter boots and checks the configuration of the HDDs before the BIOS passes control to Grub. Mint is not booting from RAID, the RAID arrays are user data only. I have SSD for OS, and a small HDD for other stuff.
Currently: Linux Mint 21.2 Cinnamon 64-bit 5.8.4, AMD Ryzen5 + Geforce GT 710
Previously: LM20.3 LM20.2 LM20.1, LM20, LM20β, LM18.2
User avatar
JOPETA
Level 17
Level 17
Posts: 7762
Joined: Thu Nov 20, 2014 6:10 am
Location: En un lugar de cuyo nombre no quiero acordarme

Re: GRUB Timeout - LM20 & LM20.1

Post by JOPETA »

Dark Owl wrote: Sat Apr 24, 2021 2:16 pm I need you to be more explicit please
I would like but I'm not an expert and you are right, this has nothing to be with booting/grub as EFI and /(root) partition are in another non-raided disk (sdc). Any way I'm going to try to explain myself [/tab]

As a far I can understand, when selecting RAID in your UEFI setting SATA mode you are telling you want to create a RAID array. As it is hardware RAID you would be able to create such array in UEFI setting (disks forming RAID 0, RAID 1,.. ). Then you will need to manage that array with appropriated software (dmraid in Linux) in order to define/use volumes or partitions before installing.

Disks forming RAID arrays (sda and sdb) can not be accessed as normal disks as it is shown in inxi but as per fstab /home is/was is in /dev/sdb2 on installing .
# /home was on /dev/sdb1 during installation
UUID=f89f16f9-457d-43a5-bcb3-250ce00a53bc /home ext4 defaults 0 2
If a raid volume was defined installer would use dmraid and would show /home was in /dev/mapper/..).

In resume, I mean if you did not create a RAID array you don't need such SATA mode in UEFI settings or you will need to complete dmraid installation with libblockdev-mdraid2 package to avoid those warnings in systemd.

In other hand, i don't know much about systemd but that lines in journal only mean service named "failed boot detection service" start and stop w/o problem. Don't ask me if you need that service ( or another systemd service as virtual box web service) because I don't know.
Last edited by JOPETA on Sun Apr 25, 2021 9:50 am, edited 1 time in total.
Ni cola de león ni cabeza de ratón, prefiero ser diente de ajo.(Javier Krahe)
Locked

Return to “Installation & Boot”