# Call to Reboot failed. Cannot get RPI to reboot properly

**URL:** <https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947>\
**Category:** Troubleshooting\
**Created:** [2 March 2025 05:42 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947 "2025-03-02T05:42:14Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![shaxs](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@shaxs](https://dietpi.com/forum/u/shaxs)\
**Post date:** [2 March 2025 05:42 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/1 "2025-03-02T05:42:14Z")

</div>

### 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.

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [2 March 2025 06:58 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/2 "2025-03-02T06:58:21Z")

</div>

The command is simply `reboot` without the `now`

---

<div class="post-metadata">

**Author:** ![shaxs](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@shaxs](https://dietpi.com/forum/u/shaxs)\
**Post date:** [2 March 2025 17:40 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/3 "2025-03-02T17:40:09Z")

</div>

Using just reboot produces the same results.

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [2 March 2025 20:54 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/4 "2025-03-02T20:54:02Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![shaxs](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@shaxs](https://dietpi.com/forum/u/shaxs)\
**Post date:** [2 March 2025 23:14 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/5 "2025-03-02T23:14:49Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [2 March 2025 23:26 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/6 "2025-03-02T23:26:36Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![shaxs](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@shaxs](https://dietpi.com/forum/u/shaxs)\
**Post date:** [3 March 2025 00:38 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/7 "2025-03-03T00:38:04Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [3 March 2025 08:43 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/8 "2025-03-03T08:43:52Z")

</div>

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. 🤔

---

<div class="post-metadata">

**Author:** ![shaxs](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@shaxs](https://dietpi.com/forum/u/shaxs)\
**Post date:** [3 March 2025 16:29 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/9 "2025-03-03T16:29:26Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://dietpi.com/forum/uploads/default/original/1X/7e1021de2213860bce185915ce2c1786e56490ec.png) [@system](https://dietpi.com/forum/u/system)\
**Post date:** [29 August 2025 04:29 UTC](https://dietpi.com/forum/t/call-to-reboot-failed-cannot-get-rpi-to-reboot-properly/22947/10 "2025-08-29T04:29:28Z")

</div>

Closed on 29 August 2025 04:29 UTC

This topic was automatically closed 178 days after the last reply. New replies are no longer allowed.
