Public bug reported:
The last update of Ubuntu 20.04 inc. ZFS destroyed my boot process, fortunately
I dual boot between zfs and ext4.
My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The
system has been upgraded I think through 19.04 and 19.10 to 20.04; The last
system upgrade of 20.04 went wrong, the system did hang in the BIOS screen, so
I thought about HW issues. Without my SSHD and also with another HDD, the
system got passed the BIOS. So now I started thinking about boot issues. I
downloaded boot-repair and that one repaired the ext4 install, so I was happy
for a short moment.
Did run update-grub, but caused the zfs ubuntu to show up in the boot
menu, but the system failed to boot, because it needed bootpool/BOOT,
which never existed on this laptop, running update-grub in the ext
install had the next result, see:
bertadmin@Ubuntu-ext:~$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-70-generic
Found initrd image: /boot/initrd.img-5.4.0-70-generic
cannot open 'bpool/BOOT/mate-1804': dataset does not exist
<------
Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804
Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804
cannot open 'bpool/BOOT/mate-1804@210213-linux43': dataset does not exist
<------
Found linux image: vmlinuz-5.8.0-43-generic in
vms/roots/mate-1804@210213-linux43
Found initrd image: initrd.img-5.8.0-43-generic in
vms/roots/mate-1804@210213-linux43
/usr/sbin/grub-probe: error: unknown filesystem.
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
device-mapper: reload ioctl on osprober-linux-sda3 failed: Device or resource
busy
Command failed.
device-mapper: reload ioctl on osprober-linux-sda4 failed: Device or resource
busy
Command failed.
done
This does not make me happy, not at all. Fortunately I have access to all my
data through the ext4 installation.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: zfs-initramfs (not installed)
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 27 20:07:56 2021
InstallationDate: Installed on 2019-09-09 (565 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
SourcePackage: zfs-linux
UpgradeStatus: Upgraded to focal on 2020-05-21 (310 days ago)
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921603
Title:
The last update detroyed my Ubuntu boot in use since 18.04
Status in zfs-linux package in Ubuntu:
New
Bug description:
The last update of Ubuntu 20.04 inc. ZFS destroyed my boot process,
fortunately I dual boot between zfs and ext4.
My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The
system has been upgraded I think through 19.04 and 19.10 to 20.04; The last
system upgrade of 20.04 went wrong, the system did hang in the BIOS screen, so
I thought about HW issues. Without my SSHD and also with another HDD, the
system got passed the BIOS. So now I started thinking about boot issues. I
downloaded boot-repair and that one repaired the ext4 install, so I was happy
for a short moment.
Did run update-grub, but caused the zfs ubuntu to show up in the boot
menu, but the system failed to boot, because it needed bootpool/BOOT,
which never existed on this laptop, running update-grub in the ext
install had the next result, see:
bertadmin@Ubuntu-ext:~$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-70-generic
Found initrd image: /boot/initrd.img-5.4.0-70-generic
cannot open 'bpool/BOOT/mate-1804': dataset does not exist
<------
Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804
Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804
cannot open 'bpool/BOOT/mate-1804@210213-linux43': dataset does not exist
<------
Found linux image: vmlinuz-5.8.0-43-generic in
vms/roots/mate-1804@210213-linux43
Found initrd image: initrd.img-5.8.0-43-generic in
vms/roots/mate-1804@210213-linux43
/usr/sbin/grub-probe: error: unknown filesystem.
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
device-mapper: reload ioctl on osprober-linux-sda3 failed: Device or
resource busy
Command failed.
device-mapper: reload ioctl on osprober-linux-sda4 failed: Device or
resource busy
Command failed.
done
This does not make me happy, not at all. Fortunately I have access to all my
data through the ext4 installation.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: zfs-initramfs (not installed)
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 27 20:07:56 2021
InstallationDate: Installed on 2019-09-09 (565 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
SourcePackage: zfs-linux
UpgradeStatus: Upgraded to focal on 2020-05-21 (310 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1921603/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
