No bootmenu items generated by grub-mkconfig on ZFS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Environment:
# lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
# apt-cache policy grub2-common
grub2-common:
Installed: 2.06-2ubuntu7.2
Candidate: 2.06-2ubuntu7.2
Version table:
*** 2.06-2ubuntu7.2 500
500 http://
100 /var/lib/
2.06-2ubuntu7 500
500 http://
Observed behavior: Got unbootable system after kernel upgrade.
Expected behavior: Booting perfectly booting shiny new linux system. :-)
Symptoms:
Ubuntu 20.04 is installed on ZFS. Datasets on bpool (and rpool) use are being snapshot as part of recovery plan. Package upgrade triggered grub-mkconfig. There is always a lot of warnings. This time the generated grub.cfg contained no items to boot linux. The system was unbootable.
Steps to reproduce (and correction):
Run
# grub-mkconfig
observe stderr message "/etc/grub.
and the output from /etc/grub.
Run
# GRUB_DISTRIBUTOR= GRUB_CMDLINE_
the output contans linux boot items generated by /etc/grub.
Comments and suggestions:
It seems that either the required parameters (environnment variables) are not set during apt-upgrade or 10_linux_zfs misbehaves when optional parameters in envvars are missing.
I can't decide.
Anyway, there is an availability problem after upgrade, so I am considering this as a security incident.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: grub2-common 2.06-2ubuntu7.2
ProcVersionSign
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 11 08:07:09 2024
InstallationDate: Installed on 2022-11-19 (448 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
GRUB_DISTRIBUTOR and the other variables are set in /etc/default/grub on a normal system, but it seems you have inadvertently broken this file. I suggest having a look at that and fixing it, and reaching out to one of the support forums if you need further assistance.