Multiple systemd unit failed to start and then systemd hang boot log at github gist

what I did before I ended up here

  • changed boot partion
  • modified /etc/fstab
  • disabled SELinux (I thought file label problem)

[!NOTE] If I add <space>3 at end of kernel command line I will end up with

mmap: Permission denied
mmap: Permission denied

and prompt for username and I can’t log; I don’t reach password prompt

  • DoctorNope@lemmy.world
    2·
    7 months ago

    From here I’d boot from a rescue usb stick or something and mount the system partitions under it to continue troubleshooting.

    If you don’t have one or it doesn’t work, you may be able to get into the system by passing init=/bin/sh or similar on the kernel cmdline. You’ll get a bare minimum root shell without a login prompt.

      • DeltaWingDragon@sh.itjust.works
        1·
        6 months ago
        1. Boot live USB
        2. Find the correct partitions using lsblk (you may only need the root partition)
        3. Mount them (root goes on /mnt, others go within the root)
        4. chroot /mnt (if permission denied, run it with sudo)
        5. Search the logs or journals for the error (journald was the first to fail, maybe check its logs first)

        If you get errors like “no proc filesystem mounted”, then you also need to mount special filesystems before entering the chroot. Run these commands as root:

        mount /proc -t proc /mnt/proc
mount /sys -t sysfs /mnt/sys
mount /dev -t devtmpfs /mnt/dev