I've upgrades couple of my Ubuntu installations onto 26.04 in preparation for the upgrade flood gates opening in a month or so when upgrading will be officially supported.
-
I've upgrades couple of my Ubuntu installations onto 26.04 in preparation for the upgrade flood gates opening in a month or so when upgrading will be officially supported.
My virtual test machine went from 25.10 without issues, ditto with our streaming PC from 24.04. But my arcade desktop decided to turn into a fuster cluck.
My test virtual had a weird glitch in 25.04 to 25.10 upgrade. The upgrade process just died about halfway there and kicked me into the login screen. This happened in both, X and text console. After the do-release-upgrade script had died, I had to sort it out manually, which fortunately was just finishing the interrupted dpkg run and clearing out the obsoleted packages manually.
But the arcade's desktop decided to do this, except it has ZFS encrypted root and it died in a way that sudo nor su didn't work!
I had to boot off a live CD, unlock and mount the root, finish the installation from there. It did result with a working system, but I've now seen this weird issue twice but couldn't catch what exactly happened. It's just like the whole login session just disappears.
-
I've upgrades couple of my Ubuntu installations onto 26.04 in preparation for the upgrade flood gates opening in a month or so when upgrading will be officially supported.
My virtual test machine went from 25.10 without issues, ditto with our streaming PC from 24.04. But my arcade desktop decided to turn into a fuster cluck.
My test virtual had a weird glitch in 25.04 to 25.10 upgrade. The upgrade process just died about halfway there and kicked me into the login screen. This happened in both, X and text console. After the do-release-upgrade script had died, I had to sort it out manually, which fortunately was just finishing the interrupted dpkg run and clearing out the obsoleted packages manually.
But the arcade's desktop decided to do this, except it has ZFS encrypted root and it died in a way that sudo nor su didn't work!
I had to boot off a live CD, unlock and mount the root, finish the installation from there. It did result with a working system, but I've now seen this weird issue twice but couldn't catch what exactly happened. It's just like the whole login session just disappears.
And for the future reference, if you have any Ubuntu variant with encrypted ZFS root, here's how you can mount the root and boot partitions while pulling the encryption key from dmcrypted zvol:
mkdir /mnt/target
mkdir /mnt/key
zpool import -N -f -R /mnt/target rpool
cryptsetup open /dev/zvol/rpool/keystore zfs-key
mount -v /dev/mapper/zfs-key /mnt/key/
zfs load-key -L file:///mnt/key/system.key rpool
zpool import -N -f -R /mnt/target bpool
zfs mount -a -
And for the future reference, if you have any Ubuntu variant with encrypted ZFS root, here's how you can mount the root and boot partitions while pulling the encryption key from dmcrypted zvol:
mkdir /mnt/target
mkdir /mnt/key
zpool import -N -f -R /mnt/target rpool
cryptsetup open /dev/zvol/rpool/keystore zfs-key
mount -v /dev/mapper/zfs-key /mnt/key/
zfs load-key -L file:///mnt/key/system.key rpool
zpool import -N -f -R /mnt/target bpool
zfs mount -aCurious, I managed to replicate this crash on another computer. The updater just dies and the machine is thrown onto the first tty login screen. The end result is so badly half-installed there's no way to log in.
It does however result in a working system if booted from a rescue system and the dpkg is continued in a chroot.
-
Curious, I managed to replicate this crash on another computer. The updater just dies and the machine is thrown onto the first tty login screen. The end result is so badly half-installed there's no way to log in.
It does however result in a working system if booted from a rescue system and the dpkg is continued in a chroot.
@apz and that's exactly why for my "production" machines (my PC, laptop and server) I never go more complicated that LVM+ext4, plus LUKS on my laptop.
KISS!
-
@apz and that's exactly why for my "production" machines (my PC, laptop and server) I never go more complicated that LVM+ext4, plus LUKS on my laptop.
KISS!
@leniwcowaty I'm having hard time finding the KISSiness on putting an LVM on a crypto block device and a filesystem on top of that.
ZFS is all that in a single system.
What comes to the failure on update, it is not related to the filesystem.
-
R relay@relay.mycrowd.ca shared this topic
