This bug was fixed in the package grub2 - 2.04-1ubuntu3
---
grub2 (2.04-1ubuntu3) eoan; urgency=medium
[ Mathieu Trudel-Lapierre ]
* debian/patches/ubuntu-add-devicetree-command-support.patch: import patch
into git-dpm: drop [PATCH] tag and add Patch-Name.
[ Didier Roche ]
This can be closed. The changelog has been rewritten apparently and so,
didn't have the stenza on this fix, but it's in 2.04-1ubuntu2.
** Changed in: grub2 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Reopening, this isn't in ubuntu yet.
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834095
Title:
update-grub fails on
This is committed in the grub ubuntu packaging branch, waiting for the
next release handled by the foundation team (due to a FTBFS to debug +
merge)
** Changed in: grub2 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Thanks for confirming!
After deep analysis, the best path is to rewrite a critical part of the
logic in shell it seems. At least, you are unblocked!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After installing gawk and updating the system (including grub), the
issue reported with update-grub is resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834095
Title:
update-grub fails on
ok, found the issue. I think if you followed the zol ubuntu
administration guide
(https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS), which
is only using a debootstrap, you are using mawk and not gawk, which is
why the regexp don't match and find your kernel.
Traditional ubuntu
** Changed in: grub2 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834095
Title:
update-grub fails on zfs with root and boot datasets
To manage
zfs get all bpool/BOOT/ubuntu
NAME PROPERTY VALUE SOURCE
bpool/BOOT/ubuntu type filesystem -
bpool/BOOT/ubuntu creation Sat Apr 27 22:23 2019 -
bpool/BOOT/ubuntu used 211M -
Additional information:
cat /etc/systemd/system/zfs-import.target.wants/zfs-import-bpool.service
[Unit]
DefaultDependencies=no
Before=zfs-import-scan.service
Before=zfs-import-cache.service
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/zpool import -N -o cachefile=none bpool
Thanks for the results!
Can you run "zfs get all bpool/BOOT/ubuntu" please?
I'm a little bit puzzled about this line:
bpool/BOOT/ubuntu 121M 246M 120M legacy
legacy means you have a manual mountpoint set on this dataset. How do you mount
it? Can you paste your /etc/fstab (I guess you
zpool list
NAMESIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT
bpool 496M 122M 374M -18%24% 1.00x ONLINE -
rpool 39.2G 5.18G 34.1G -19%13% 1.00x ONLINE -
zfs list
NAME USED AVAIL REFER MOUNTPOINT
bpool
Hey, thanks for reporting this bug and help to make ubuntu better.
Can you please post the following so that we can debug what went wrong. Outputs
of:
* zpool list
* zfs list
for each dataset:
* zfs get all
That way, we can find why your datasets and boot pools were not detected
and add a test
Thank you for your bug report, could you give some details/specific on
the error and maybe add the update-grub log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834095
Title:
update-grub fails on
14 matches
Mail list logo
