Hi,
recently I noticed that sometimes after booting my Raspberry not all of the Dietpi Services are starting, I assume it's all the postboot services, see this screenshot:
At first I felt this only happens if I login via ssh directly after reboot, but this seems not to be the cause.
I already tried to find a hint by looking at the journalctl output and other log files, but could not find an error. Any ideas, where to search?
Dietpi Services not starting
-
- Posts: 12
- Joined: Sat Dec 22, 2018 1:33 pm
Re: Dietpi Services not starting
Update:
I digged into the journal messages and compared a successful with an unsuccessful boot. Seems the problem is somehow related to Systemd and/or Plymouth.
I can see that plymouth-quit-wait.service is started, because it says:
but plymouth-quit.service, which also should be started, is not. There is no
as in the successful start's journal.
So it waits for plymouth to finish, without asking it to stop. Thus, target Multi-User System is not reached, and dietpi-postboot is not started. I have no access to a system to test right now, but will check if a manual start/restart of plymouth-quit.service forces to other services to follow.
I found a couple of similar problems when googling it, but no good explanation or solution so far. So still, any hint would be appreciated
I digged into the journal messages and compared a successful with an unsuccessful boot. Seems the problem is somehow related to Systemd and/or Plymouth.
I can see that plymouth-quit-wait.service is started, because it says:
Code: Select all
Starting Hold until boot process finishes up...
Code: Select all
Starting Terminate Plymouth Boot Screen...
So it waits for plymouth to finish, without asking it to stop. Thus, target Multi-User System is not reached, and dietpi-postboot is not started. I have no access to a system to test right now, but will check if a manual start/restart of plymouth-quit.service forces to other services to follow.
I found a couple of similar problems when googling it, but no good explanation or solution so far. So still, any hint would be appreciated

Re: Dietpi Services not starting
Can you please try to edit /etc/systemd/system/dietpi-postboot.service and remove multi-user.target from the After= line?
Then systemctl daemon-reload an check on next reboot.
Then systemctl daemon-reload an check on next reboot.
Re: Dietpi Services not starting
Okay, glad to here. This is already patched for DietPi v6.22 as well.
-
- Posts: 12
- Joined: Sat Dec 22, 2018 1:33 pm
Re: Dietpi Services not starting
In the last few days every boot went fine, and I was wondering how that happened... I had switched to the dev branch in the meantime, with the already updated dietpi-postboot.service
So obviously no more problems now, thanks!

So obviously no more problems now, thanks!
Re: Dietpi Services not starting
Okay, just keep in mind that the dev branch indeed is under development and not tested throughout. But current stage at least does not contain some unfinished things, should work fine.