Hi there. After much troubleshooting, I have gotten it to boot out of emergency mode.
`systemctl --failed` revealed that an external hard drive, proc-sys-fs-binfmt_misc.automount, gpu-manager.service , grub-common.service, snap.xlxd.active.service and systemd-networkd-wait-online.service all failed. I unplugged the external drive, and restarted, commenting out all external drives in `/etc/fstab`. I reloaded the daemon (`system daemon-reload`), brought the ethernet back online, and ran `apt update` and `apt dist-update -y`. I uploaded the bootloader and grub (`update-initramfs -u -k all` `update-grub`). That led me to discover that I had a bunch of 20.04 kernels mixed in with 22.04 kernels. `dpkg --list | grep linux-image` revealed >50 with `linux-image-5.4.0-*`. So I purged as many of those as I could `sudo apt-get purge linux-image-5.4.0-* linux-modules-5.4.0-*` Then ran: `apt-get autoremove --purge` `update-initramfs -u -k 5.15.0-168-generic` `update-grub` `systemctl enable ssh` `reboot` That worked. I'm out of emergency mode, but now on boot up I see: `Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-168-generic x86_64)` and `* Ubuntu 20.04 LTS Focal Fossa has reached its end of standard support on 31 May 2025.` Sounds like I still have some images from 20.04 that I failed to update. I think this all spurred from trying to upgrade a 20.04 image that had the GUI installed instead of just the server version. What are the best practices for cleaning up this install now? I'm fine to delete all gnome/desktop applications. The server doesn't even have bluetooth to my knowledge. <http://www.tbconservation.org> Alex Krohn, PhD Director of Conservation Genomics Tangled Bank Conservation tbconservation.org <http://www.tbconservation.org> On Mon, Feb 9, 2026 at 1:50 AM Daniel van Vugt <[email protected]> wrote: > I should also note that bluetoothd crashing is a temporary failure. The > upgrade system ideally shouldn't be representing that as a permanent > problem. If bluetoothd isn't repeatedly crashing after reboots then it's > not a problem we really need to prioritise here. It sounds like being > stuck in emergency mode is the bigger issue -- that too is likely to be > an upgrade problem. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2140585 > > Title: > Failed to update to 2022 LTS because of bluez, bluetooth or gnome-core > > Status in bluez package in Ubuntu: > Incomplete > > Bug description: > Attempting to update an old machine from 20.04 LTS to 22.04 LTS sudo > sudo do-release-upgrade. Upgrade failed with errors: > > Errors were encountered while processing: > bluez > gnome-bluetooth > pulseaudio-module-bluetooth > gnome-core > gnome > Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned > an error code (1) > > > lsb_release -rd shows Ubuntu 22.04.5LTS so some part of the upgrade was > completed. Not sure which of those packages may be malformed though... > > ProblemType: Package > DistroRelease: Ubuntu 22.04 > Package: bluez 5.64-0ubuntu1.4 > ProcVersionSignature: Ubuntu 5.4.0-216.236-generic 5.4.291 > Uname: Linux 5.4.0-216-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.10 > Architecture: amd64 > CasperMD5CheckResult: pass > CloudArchitecture: x86_64 > CloudID: none > CloudName: none > CloudPlatform: none > CloudSubPlatform: config > Date: Thu Feb 5 09:33:41 2026 > ErrorMessage: installed bluez package post-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2022-01-28 (1469 days ago) > InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release > amd64 (20210824) > InterestingModules: bluetooth > MachineType: Dell Inc. PowerEdge R810 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-216-generic > root=UUID=eb218b7c-d1b2-4356-ace3-c131a6f57309 ro maybe-ubiquity > Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, > 3.10.6-1~22.04.1 > PythonDetails: N/A > RebootRequiredPkgs: Error: path contained symlinks. > RelatedPackageVersions: > dpkg 1.21.1ubuntu2.6 > apt 2.4.14 > SourcePackage: bluez > Title: package bluez 5.64-0ubuntu1.4 failed to install/upgrade: > installed bluez package post-installation script subprocess returned error > exit status 1 > UpgradeStatus: Upgraded to jammy on 2026-02-05 (0 days ago) > dmi.bios.date: 06/04/2018 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 2.11.0 > dmi.board.name: 0TT6JF > dmi.board.vendor: Dell Inc. > dmi.board.version: A02 > dmi.chassis.type: 23 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr2.11.0:bd06/04/2018:svnDellInc.:pnPowerEdgeR810:pvr:rvnDellInc.:rn0TT6JF:rvrA02:cvnDellInc.:ct23:cvr: > dmi.product.name: PowerEdge R810 > dmi.sys.vendor: Dell Inc. > hciconfig: > > syslog: > Feb 05 08:31:54 tbc-comp1 NetworkManager[1885]: <info> > [1770298314.5587] Loaded device plugin: NMBluezManager > (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) > Feb 05 08:32:00 tbc-comp1 systemd[1]: Condition check resulted in > Bluetooth service being skipped. > Feb 05 08:42:27 tbc-comp1 systemd[1]: Condition check resulted in > Bluetooth service being skipped. > Feb 05 09:54:48 tbc-comp1 NetworkManager[94596]: <info> > [1770303288.1671] Loaded device plugin: NMBluezManager > (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-bluetooth.so) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2140585/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2140585 Title: Failed to update to 2022 LTS because of bluez, bluetooth or gnome-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2140585/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
