systemd can't start sshd after 5.x -> 6.x upgrade

[jimmyjoe]

Hi,
Anyone know how to fix this? I can start sshd by hand using /usr/sbin/sshd -DDD and no errors are present. At boot however, systemd is having problems and I can't login. journalctl -xb says this:

pam_systemd(sshd:session): Failed to connect to system bus: No such file or directory

 

[oguz]

hi,

what does systemctl status dbus say? if it's not active, try starting the service (systemctl start dbus and enable)

 

[jimmyjoe]

Thanks for the reply. I think the ssh issue was due to being booted in "Emergency Mode" (single user mode?) and I'll bet you're right about dbus being disabled too. I started commenting things out of /etc/fstab and suddenly it booted normally. my /dev/pve/data partition seemed to be the problem and I have no idea why. It's a local partition which was previously mounted with noatime,nodiratime,defaults,relatime 0 1. I changed the fsck field to a 2 and added the noauto to hopefully get it out of any boot dependencies. That seems to have done the trick.

I've got five more hypervisors to upgrade, all configured the same way so we'll see how the rest go.