MichaIng

Do you have a backup you can restore from before the update? Or do you remember which DietPi version you originally upgraded from? I would like to see really all...

Okay your last output shows the broken `/dev/null` before `dietpi-update` even started to do anything. Now I also see the capped lines in your first paste, which contains the same...

Okay so far so good, probably it is one of the stopped services: ```sh ls -l /dev/null dietpi-services stop ls -l /dev/null ```

The `/dev/null` file however is again broken. More importantly, it is broken now, after the reboot. Since `/dev` is recreated from scratch, this means that not the DietPi update, but...

Ah sorry, the node needs to be repaired first, of course: ```sh rm /dev/null mknod -m 0666 /dev/null c 1 3 ls -l /dev/null dietpi-services restart ls -l /dev/null ```

Okay, service restarts did not break it. Can you do another `reboot` and see if it is broken again? If so, let's check journal logs whether we can see related...

The daily cron job throws this error, but we don't know yet whether it also causes is, or whether it is done at boot only. Can you try this: ```sh...

Since the daily cron job did not cause it, the daily update check obviously does not cause the issue. So it seems to be something at boot then. Let's try...

Oh typo, `ls -l` of course, to see the details of the file: ```sh ls -l /dev/null systemctl start systemd-tmpfiles-setup-dev-early ls -l /dev/null systemctl start systemd-tmpfiles-setup-dev ls -l /dev/null systemctl...

Hmm, I faced a very similar issue some weeks ago. The `/dev/null` node was somehow replaced by an actual file, which of course breaks everything which tries to redirect output...