Quantcast
Channel: Linux Device Hacking
Viewing all articles
Browse latest Browse all 3247

System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down (9 replies)

$
0
0
Quote
System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down

I have a few Pogoplug Pro's and I keep having this same issue as stated above. It seemed to start when things went from 4.xx to 5.xx and hopefully someone smarter than I can help with a solution. After I get that message I can no longer ssh to the Pogoplug.

I have started from scratch many times and install Debian-4.14.180-oxnas-tld-1-rootfs-bodhi.tar.bz2 on the Pogoplug Pro. Everything seems to run well and I upgrade to Bullseye and the latest kernel, linux-5.4.224-oxnas-tld-1.bodhi.tar.bz2. I am using the Pogoplug Pro for Time Machine backups so I install netatalk and avahi-daemon and the backups work fine.

The message above starts after I create a swap file and reboot the machine. All this is done via ssh. The Pogoplug seems to reboot and come up, but I can no longer connect to it via ssh. My router shows it is connected and has an ip, though I cannot successfully ping that ip or log in. I end up starting from scratch again, hoping to pin down what it is but I'm not getting anywhere. I can connect the drive to another box and access everything but I don't know what to do to fix this.

Anybody run across this? Thanks for any help you may provide.

Viewing all articles
Browse latest Browse all 3247

Trending Articles