i did update my machine with pacman -Syu. after rebooting, i cannot login. i con see this error Failed to start Virtual Console Setup a tiny second right before log in screen. i had to capture it in slow mo to able to read it. i attach the image below.

and on the login, after i enter my username and hit enter it just hangs for a while without asking the password and asks for username again. it acts like when you enter wrong password.

  • bloodfart@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    agetty[349]: tty1: can’t exec /bin/login: No such file or directory

    Well there’s your problem.

    Login gets called to check if the username you put in is in the list of users and if it is it asks for a password (behavior subject to configuration). If you don’t have /bin/login you can’t login!

    Advice to fix arch is as follows: boot from usb, chroot to your environment and use the built in tools to fix it automatically.

      • ProgrammingSocks@pawb.social
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        3 months ago

        Chroot sidesteps login entirely. When you use chroot you’re always root and you don’t need the password of the machine you’re chrooting into.

  • Static_Rocket@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    3 months ago

    That warning comes up if you are using sd-vconsole but do not have systemd in the mkinitcpio hooks. You should fix that but it is most likely unrelated to the login issue.

    Login issues normally hint at either the user shell or pam configs being wrong but you can also get this behavior if (the users home directory is on a secondary disk && that disk failed to mount && you aren’t using systemd-homed).

    • t0mri@lemmy.mlOP
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      sorry for late reply. yeah, my /bin got messed up somehow, thats why it couldnt find the essentials, more likely bash

  • Handles@leminal.space
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    I’m curious about this because I had a bunch of dracut warnings when I updated my EndeavourOS to 6.8.7 the other day. Seeing this doesn’t make me too keen on rebooting until I’ve updated without error messages…

  • www-gem@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    3 months ago

    To investigate the issue you may want to use a bootable drive and chroot into your system. This will allow you to see any error messages using the journactl command. Once you know what’s going on exactly you’ll be able to fix it or get a better assistance from people here or on the Arch forum.
    I know someone who encountered the exact same login behavior after this update. It appeared that some packages were broken and he had to reinstall them.