/run/dietpi folder not created on boot

Hello kind folks.
I recently upgraded to Bullseye Armv8 64bit version on my RPi 4 4GB. Since I wanted a fresh installation and migrate my data to the new installation, I first flashed the image on a separate USB stick. Once I ran the initial setup I then replaced the /boot and / partitions over my existing USB drive having the older Buster image.
Changed UUIDs to read partitions correctly, mounted the user data partition and setup all my dockers as well. Everything is setup up fine and running great. It was a relatively quicker setup than I had expected. :smiley:
The only thing now is I’m not able to see the MOTD message in the banner anymore and it’s showing this error instead:

curl: (23) Failure writing output to destination

On digging a little bit, I found that the /run/dietpi folder isn’t being created on boot, which is why the banner script isn’t able to find the MOTD message to display. On manually creating this folder, banner is correctly displaying MOTD. However, every time I reboot, the folder goes missing and isn’t created automatically.
On the other hand, the USB stick which has a fresh installation is able to do this fine. So I think I might have changed some permissions unknowingly somewhere. I did not create/write images of partitions when migrating, but had simply copied them over and changed some of the permissions where required.

Can somebody help in fixing this? Are there any other Dietpi scripts that rely on this path? I haven’t faced any other issues till now, but don’t know if something might be amiss in the background.

yes the directory should be created during boot process and it is used by a couple of scripts. can you check related service

journalctl -u systemd-tmpfiles-setup
systemctl status systemd-tmpfiles-setup

Looks like I didn’t check close enough. systemctl from dietpi user isn’t working:

Failed to connect to bus: No such file or directory

Here’s the output with sudo:

dietpi@nas:~$ sudo journalctl -u systemd-tmpfiles-setup
-- Journal begins at Mon 2021-10-25 15:06:01 IST, ends at Mon 2021-10-25 16:58:32 IST. --
Oct 25 15:06:01 nas systemd[1]: Starting Create Volatile Files and Directories...
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/lock.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/resolvconf.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/resolvconf.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/resolvconf.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/resolvconf.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/sudo.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/lib/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd/netif.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd/netif.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/systemd/netif.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/lib/systemd.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/lib.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/log.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/cache.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/log.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/log.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var/log.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /var during canonicalization of /var.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal/f0dfe7327d214b12ab1ed445764f68ba.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal/f0dfe7327d214b12ab1ed445764f68ba/system.journal.
Oct 25 15:06:01 nas systemd[1]: Finished Create Volatile Files and Directories.



dietpi@nas:~$ sudo systemctl status systemd-tmpfiles-setup
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
     Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static)
     Active: active (exited) since Mon 2021-10-25 15:06:01 IST; 1h 53min ago
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)
    Process: 278 ExecStart=systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=73)
   Main PID: 278 (code=exited, status=73)
        CPU: 35ms

Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /tmp during canonicalization of /tmp.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal/f0dfe7327d214b12ab1ed445764f68ba.
Oct 25 15:06:01 nas systemd-tmpfiles[278]: Detected unsafe path transition / → /run during canonicalization of /run/log/journal/f0dfe7327d214b12ab1ed445764f68ba/system.journal.
Oct 25 15:06:01 nas systemd[1]: Finished Create Volatile Files and Directories.

I guess some permission issues on Root Partition. Can you share following

ls -la /

And of course sudo to be used as non-root user.

Most systemctl commands will need root, but just systemctl should give some result as well right?

Output for ls -la /:

total 64
drwxrwxr-x  18 dietpi dietpi  4096 Oct 24 16:21 .
drwxrwxr-x  18 dietpi dietpi  4096 Oct 24 16:21 ..
lrwxrwxrwx   1 root   root       7 Aug 12 19:01 bin -> usr/bin
drwxr-xr-x   5 root   root    4096 Jan  1  1970 boot
drwxr-xr-x  16 root   root    3420 Oct 25 15:06 dev
drwxr-xr-x  66 root   root    4096 Oct 24 21:27 etc
drwxr-xr-x   4 root   root    4096 Oct 24 15:40 home
lrwxrwxrwx   1 root   root       7 Aug 12 19:01 lib -> usr/lib
drwx------   2 root   root   16384 Aug 12 18:59 lost+found
drwxr-xr-x   2 root   root    4096 Aug 12 19:39 media
drwxr-xr-x   6 root   root    4096 Oct 24 15:34 mnt
drwxr-xr-x   3 root   root    4096 Oct 24 15:12 opt
dr-xr-xr-x 190 root   root       0 Jan  1  1970 proc
drwx------   5 root   root    4096 Oct 24 15:38 root
drwxr-xr-x  17 root   root     500 Oct 25 15:06 run
lrwxrwxrwx   1 root   root       8 Aug 12 19:01 sbin -> usr/sbin
drwxr-xr-x   2 root   root    4096 Aug 12 19:01 srv
dr-xr-xr-x  12 root   root       0 Jan  1  1970 sys
drwxrwxrwt   2 root   root      40 Oct 25 17:36 tmp
drwxr-xr-x  11 root   root    4096 Aug 12 19:01 usr
drwxr-xr-x  12 root   root    4096 Oct 24 15:01 var

Most systemctl commands will need root, but just systemctl should give some result as well right?

Yes if you use sudo :wink:

Pls do following to fix the permission issues on root / directory

chown root:root /
chmod 755 /
reboot

Thanks for your help!
That worked fine. I missed checking / dir for permissions.

that happen :sunglasses: