18.04 upgrade, systemd fails to isolate target, boot and recovery fail

[afrodeity]

Upgraded to 16.04 to 18.04.

No recovery or graphical mode.

Systemd, reports that it failed to isolate default target and also recovery target.

Am only able to boot to an init=/bin/bash shell without systemd or networking.

Any help appreciated.

[1fallen]

Sorry to hear this, i have had luck with information provided here: https://linuxconfig.org/how-to-boot-ubuntu-18-04-into-emergency-and-rescue-mode
And this also has helped me recover from my errant ways: https://www.systutorials.com/239880/change-systemd-boot-target-linux/
Good Luck :)

systemctl cat emergency.target
# /usr/lib/systemd/system/emergency.target
# SPDX-License-Identifier: LGPL-2.1+
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.

[Unit]
Description=Emergency Mode
Documentation=man:systemd.special(7)
Requires=emergency.service
After=emergency.service
AllowIsolate=yes

[afrodeity]

Thanks

While informative about systemd, neither articles provide any answers as to solving the problem with a system that is unable to boot with failed target.

This link seems more like a possible solution (https://wiki.ubuntu.com/SystemdForUpstartUsers)

[afrodeity]

I can chroot into the drive (https://www.cyberciti.biz/faq/ubuntu-mounting-your-encrypted-home-from-livecd/) like this, but what now?

will try this


mount /dev/sda2 /mnt/recovery
mount -t sysfs none /mnt/recovery/sys
mount -t proc none /mnt/recovery/proc
mount --bind /dev/ /mnt/recovery/dev
mount --bind /dev/pts /mnt/recovery/dev/pts
mount -o bind /etc/resolv.conf /mnt/recovery/etc/resolv.conf
chroot /mnt/recovery