DietPi-Backup stops services and does not restart them after successfull backup

Hello guys!

I use the “DietPi-Backup” function for regular automatic backups. I have set it up to perform backups daily at 03:30 AM and to retain a maximum of the last three backups.

From time to time, I notice that while the backup runs successfully, the services that were stopped beforehand are not automatically restarted. This doesn’t happen every time, but at irregular intervals. I’ve noticed it with the “Jellyfin” service, which then becomes unreachable. I can see that the service hasn’t restarted in the “DietPi-Dashboard” under the “Services” section. The start time there is then very close to 03:30 AM. This issue doesn’t just affect “Jellyfin,” but also services like “minidlna” or “docker,” for example.

The destination for backups is a connected external HDD via USB 3.0 with an extra origin power supply (WD My Book with 18 TB).

Is this a normal behaviour? Or how can I avoid that services get unreachable after automatic backups?

Greetings from GER :waving_hand:

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | CORE=9 SUB=13 RC=2
  • Distro version | bookworm
  • Kernel version | 6.1.0-37-amd64 6.1.140-1 (2025-05-22)
  • Architecture | amd64
  • SBC model | Native PC (x86_64) Lenovo M720Q
  • Power supply used | Lenovo Power Supply 90 Watt
  • SD card used | No, 128 GB SSD (brand: Crucial)

Additional Information (if applicable)

  • Software title | dietpi-backup
  • Was the software title installed freshly or updated/migrated? Preinstalled
  • Can this issue be replicated on a fresh installation of DietPi? No, only sometimes

Usually services should be restarted automatically afterwards. You would need to check service logs. Maybe there is a hint for the service not starting correctly.

But the rest of the system is stell repsonsive? You can execute commands and stuff?

@Joulinar Could you please give me advice which log should I check?

@Jappe Yes, I can connect via SSH for example or I can log in to the dietpi dashboard.

You can use following to check service logs

journalctl -u <service-name>

Replace <service-name> with the service in question