Call to Reboot failed. Cannot get RPI to reboot properly

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues and while I found some issues discussed, my issue is a little different.

Required Information

  • DietPi version |
    G_DIETPI_VERSION_CORE=9
    G_DIETPI_VERSION_SUB=11
    G_DIETPI_VERSION_RC=2
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’

  • Distro version | Bookworm

  • Kernel version | Linux

  • Architecture | Arm64

  • SBC model | RPI 4

  • Power supply used | Meanwell 5v PSU

  • SD card used | SanDisk ultra 64gb

Additional Information (if applicable)

  • New install of dietpi.
  • Also have Kalico Klipper installed along with crowsnest, moonraker, Kiauh, Klipper screen, and Mainsail. This is for a Voron 3d printer.

Steps to reproduce

  1. SSH into machine using dietpi user.
  2. Request a reboot using “sudo reboot now”

Expected behaviour

  • System would properly reboot. Should be able to SSH after reboot is done.

Actual behaviour

  • Get the following error messages:
    “Failed to set wall message, ignoring: Unit dbus-org.freedesktop.login1.service failed to load properly, please adjust/correct and reload service manager: File exists
    Call to Reboot failed: Unit dbus-org.freedesktop.login1.service failed to load properly, please adjust/correct and reload service manager: File exists”
  • Screen on the system is blank.
  • Reboot never happens. I have to manually power off and on again.

Extra details

  • Tried to install Dbus but it was already there and up to date.
2

The command is simply reboot without the now

3

Using just reboot produces the same results.

4

you are trying to reboot via SSH? You are using root user?

5

using user ‘dietpi’ not user ‘root’. I am using sudo in the command though if that matters.

6

For testing, how does it behave using root? And are you connected via SSH?

7

Yes connected via SSH. Logging in as root does not give me the error message. However, the machine does not successfully reboot. It acts more like a shutdown instead. I still have to manually power off and power back on for the dietpi to load.

8

so it’s going to shutdown but did not reboot afterwards?

That’s hard to check why system is not booting up because we don’t have a log for this. Best would be to use a serial adapter to verify messages during shutdown and to check where is stops. :thinking:

9

That is correct. I never had an issue on bookworm that was flashed via the official Raspberry Pi flashing tool. I do not have a serial adapter unfortunately.