[Bug 2056646] Re: Ubuntu dual boot mix up from zfs and from ext4
BertN45
2056646 at bugs.launchpad.net
Fri Mar 15 15:01:16 UTC 2024
Content of fstab and the swap file lines have 7 items instead of 6,
because I added priority, but that has always been like this since many
years. The system should use first the nvme swap and only if full the
HDD swap :)
# /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>
/dev/disk/by-uuid/6e6abccf-46b7-4915-ac0e-9aaa264965ab none swap sw pri=0 0 0
/dev/disk/by-uuid/7454fc6f-80d7-478e-a67b-84eacf44c40f none swap sw pri=-1 0 0
# Use `zfs list` for current zfs mount info
# bpool none defaults 0 0
# Use `zfs list` for current zfs mount info
# rpool none defaults 0 0
# Use `zfs list` for current zfs mount info
# rpool / defaults 0 0
# Use `zfs list` for current zfs mount info
# bpool /boot defaults 0 0
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/C4D7-B106 /boot/efi vfat defaults 0 1
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/2056646
Title:
Ubuntu dual boot mix up from zfs and from ext4
Status in ubuntu-release-upgrader package in Ubuntu:
New
Bug description:
I dual boot Ubuntu 23.10 from openzfs from nvme (main OS) and from
ext4 from HDD (backup OS). In 23.10 everything worked, I could use my
datapools on both systems also rpool, The nvme datapool rpool contains
the ROOT dataset and 2 datasets with my main VMs.
I upgraded the ext4 system to 24.04 (do-release-upgrade -d) and that
worked fine. I have 2 other datapools on the HDD and I can use them
without any issue after (zpool import -f) on the ext4 system.
As soon as I try to import the datapool rpool the problem starts, it
gives the following error message:
"Broadcast message from systemd-journald at Host-sdb5 (Sat 2024-03-09
12:50:47 AST): systemd[1]: Caught <ABRT>, from our own process."
Afterwards it is impossible to use the terminal, it just does not
start. However most other applications still work as normal. It is
also impossible to shut-down the system from the menu. I have to
power off the system with the power button.
On reboot I get the following error messages;
zfs: module license "CDDL" taints kernel.
Disabling lock debugging due to kernel taint
zfs: module license taints kernel
It seems to load the zfs kernel modules again, why? It is superfluous
and wrong, because they are already loaded from ext4 much earlier.
Afterward the system is completely confused and hangs. (see the
annexed photo)
My nvme system does not boot anymore, because it is missing rpool, but
it nicely advises in initramfs to use "zpool import -f" and that
works.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.7
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 9 13:12:08 2024
InstallationDate: Installed on 2023-12-21 (80 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to noble on 2024-03-09 (0 days ago)
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056646/+subscriptions
More information about the foundations-bugs
mailing list