[Bug 1887257] Re: update-grub does not create any entry on grub.cfg for ZFS on root

[Thomas Eason]

Why is this an invalid issue?  There are a number of commercial packages
for redhat that don't really support ubuntu unless you change the shell.
Also you get zero notification from dash that you are about to break
your zfs system.  It appears from /usr/share/doc/dash/NEWS.Debian.gz
that changing your shell is supported behavior.

Even if changing your shell is not allowed, how is silently breaking
your system in a way that will make your system unbootable an acceptable
solution?   Especially when you could just call 10_linux_zfs explicitly
with /bin/dash if it relies on undefined behavior in dash?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887257

Title:
  update-grub does not create any entry on grub.cfg for ZFS on root

Status in grub2 package in Ubuntu:
  Invalid

Bug description:
  I observed after a lot of updates my kernel did not get update after
  reboot. I found my /boot zfs pool not mounted properly and re-imported
  it, but when I generate new grub.cfg, the 10_linux_zfs section is
  empty, even with /boot mounted properlly:

  root at manauara:~# zpool list
  NAME    SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
  bpool  1,88G   196M  1,68G        -         -     0%    10%  1.00x    ONLINE  -
  rpool   114G  43,8G  70,2G        -         -    46%    38%  1.00x    ONLINE  -

  root at manauara:~# mount | grep boot
  bpool/BOOT/ubuntu_bpn5ci on /boot type zfs (rw,nodev,relatime,xattr,posixacl)
  /dev/sdb1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  /dev/sdb1 on /boot/grub type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

  root at manauara:~# 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>
  # /boot/efi was on /dev/sdb1 during installation
  UUID=3663-2075  /boot/efi       vfat    umask=0022,fmask=0022,dmask=0022      0       1
  /boot/efi/grub	/boot/grub	none	defaults,bind	0	0
  UUID=9b5b207e-da46-4b16-b827-d8521151c8bf	none	swap	discard	0	0

  root at manauara:~# cat /etc/zfs/zfs-list.cache/bpool
  bpool	/boot	off	on	on	off	on	off	on	off	-	none
  bpool/BOOT	none	off	on	on	off	on	off	on	off	-	none
  bpool/BOOT/ubuntu_bpn5ci	/boot	on	on	on	off	on	off	on	off	-	none

  I have cleaned all snapshots because another issue with zsys and
  images, so my snapshot tree is almost clean:

  root at manauara:~# zfs list -t snapshot
  NAME                                                               USED  AVAIL     REFER  MOUNTPOINT
  bpool/BOOT/ubuntu_bpn5ci at autozsys_n55ov3                          90,6M      -      104M  -
  rpool/ROOT/ubuntu_bpn5ci at autozsys_n55ov3                          43,5M      -     6,22G  -
  rpool/ROOT/ubuntu_bpn5ci/srv at autozsys_n55ov3                         0B      -       96K  -
  rpool/ROOT/ubuntu_bpn5ci/usr at autozsys_n55ov3                         0B      -       96K  -
  rpool/ROOT/ubuntu_bpn5ci/usr/local at autozsys_n55ov3                   0B      -     2,94M  -
  rpool/ROOT/ubuntu_bpn5ci/var at autozsys_n55ov3                         0B      -       96K  -
  rpool/ROOT/ubuntu_bpn5ci/var/games at autozsys_n55ov3                   0B      -       96K  -
  rpool/ROOT/ubuntu_bpn5ci/var/lib at autozsys_n55ov3                   464K      -     7,93G  -
  rpool/ROOT/ubuntu_bpn5ci/var/lib/AccountsService at autozsys_n55ov3     0B      -      336K  -
  rpool/ROOT/ubuntu_bpn5ci/var/lib/NetworkManager at autozsys_n55ov3    116K      -      168K  -
  rpool/ROOT/ubuntu_bpn5ci/var/lib/apt at autozsys_n55ov3               136K      -     95,7M  -
  rpool/ROOT/ubuntu_bpn5ci/var/lib/dpkg at autozsys_n55ov3             2,32M      -     55,2M  -
  rpool/ROOT/ubuntu_bpn5ci/var/log at autozsys_n55ov3                  7,54M      -     1,13G  -
  rpool/ROOT/ubuntu_bpn5ci/var/mail at autozsys_n55ov3                    0B      -       96K  -
  rpool/ROOT/ubuntu_bpn5ci/var/snap at autozsys_n55ov3                    0B      -     2,17M  -
  rpool/ROOT/ubuntu_bpn5ci/var/spool at autozsys_n55ov3                  56K      -      208K  -
  rpool/ROOT/ubuntu_bpn5ci/var/www at autozsys_n55ov3                     0B      -       96K  -
  rpool/USERDATA/leonardo_xoeglb at autozsys_n55ov3                    16,8M      -     27,0G  -
  rpool/USERDATA/leonardo_xoeglb at autozsys_qc46s7                    7,86M      -     27,0G  -
  rpool/USERDATA/root_xoeglb at autozsys_n55ov3                         132K      -     1,17G  -

  
  The output of upgrade-grub (With sh -x in 10_linux_zen) is attached and other system information is at ubuntu-bug report attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: grub2-common 2.04-1ubuntu26
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 11 20:24:10 2020
  InstallationDate: Installed on 2020-04-27 (75 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1887257/+subscriptions