Stuck in login loop after upgrade to fedora 41 server edition

The title says it all. I can’t login to my M1 mac mini after upgrade to fedora 41 server edition.

Cockpit is unreachable. I can ping the server but can’t connect to cockpit.

When I hook a monitor and keyboard up to the M1 mac mini I get a prompt to log in. When I enter my credentials the screen just flashs real fast and the login prompt appears again. There is no error message displayed.

In the grub menu I can obtain a command line when I add “rw init=/bin/bash”. I can’t do much with that command line though. I can’t get an internet connection. With that command line active I can’t ping the server.

I tried to see what services were running…

$ systemctl --type=service --state=running
Failed to connect to system scope bus via local transport: No such file or directory

Same response when running as root.

Running nmcli was fruitless as well. I can get a version number and help but that is about it. Everything else with nmcli gives an error…

Error: Could not create NMClient object: Could not connect: No such file or directory

ssh from Windows 11 gives me this error…

ssh client_loop: send disconnect: Connection reset

When I am using that command prompt as MYUSERNAME and I type “cd” I get this error message…

cd: /home/MYUSERNAME: No such file or directory

Although when I echo $HOME it does return…

/home/MYUSERNAME

I experimented with entering the wrong password and that results in an error message and another login prompt is presented below the first. A correct password results in no error and the screen flashing and a log in prompt appearing where the original login prompt was.

When I ssh in to the server and enter the wrong password I get this error message…

Permission denied, please try again.

So the system is checking and can tell the correct login from incorrect login.

You cannot run most system management utilities when booted via init=/bin/bash, since no services are up. /home will also not be mounted (that’s why your home is missing), and you also need to be careful to do a SELinux relabel after any changes or your system will break.

Follow the standard Fedora instructions to set the root password. You should then be able to log in as root after a normal boot and inspect what is wrong.

Best wild guess, you have something in your shell profile as your user which broke the shell after the F41 update, which causes the login shell to crash and throw you back at the login prompt.

1 Like

I disabled SELinux by editing /etc/selinux/config. I was then able to login. Cockpit is now reachable and I can log in there as well. I then did a SELinux relabel.

There are a couple of things that are still broken (SELinux module for cockpit and Failed to start valkey.service). I will have to investigate and see what happened.

I’m leaving SELinux disabled for now till I have a chance to troubleshoot.

Thanks for your help.