Is there a chance that you’ll push those fixes so that they can be obtained by dietpi-upgrade (possibly with some --beta flag)? I’d like to test but am unwilling to reinstall the system once again. I have experienced the disappearing folder issue before, but for the last weeks it’s been running stable.
Thanks for your hard work!
Hi,
No worries.
The RPi attempted fix will be applied in DietPi v144 update. We couldnt find any issues with the image partitions, however, we did regenerate the image anyway just to be sure.
The Odroid C2 image was corrupted at image level. We had to re-generate the 1st partition of this image. So in this case, that would only be resolved with the new image.
this also happens to me, but I thought the problem was because of the USB drive goes into sleep mode after a while, and so it can only wake again if I reboot the system.
i use an orange pi pc (v1)
i have dietpi v.143 installed
i have the usb drive mounted through dietpi-drive-manager (/mnt/usb_1) and use it as part of the system for sickrage and such
i also have a problem with installing Kodi, I don’t understand how i can install it since it’s not available on the list of software :-/
i did it on my own and it doesn’t start properly (black screen) and the sound is all glitched
aaand when i startx , then the ssh server seems to stop and if i restart it manually it usually refuses the connection :-c
Hi,
GPU features (eg: Kodi, Desktop) are disabled on this board, the only boards we support for GPU are:
Its mostly due to lack of stable driver/documentation for H3, and, with the H3 heat issues, GPU load ontop puts the CPU under excessive heat. Not recommended.
Thanks for the info 
! !
Any news of the possible updated image for OrangePi PC?
Kudos on the release of v144! Is it possible to wget the dietpi-update script and run it on an install with an empty Dietpi folder? My RPi is 1400 miles away so rebuilding the SD card just isn’t possible…
Thanks
Problem till exist (RPI2) when you Change your root Partition to usbstick
https://dietpi.com/forum/t/tutorial-outdated-rpi-move-the-filesystem-to-a-usb-drive/317/1
tryed also:
reboot from sdcard, copy again /DietPI/ * (config.txt, dietpi Folder,…) to /mnt/usb_1/DietPI but after reboot, Folder is again empty.
Hey there,
I run into a similar issue - only that I use an Odroid XU4.
After I did the upgrade to v145 and rebooted the device, the DietPi-folder is empty. Before that everything was fine and working for a few weeks now (v144).
I have to say that I switched (from point of installation DietPi) the system to an external usb-drive using the drive-manager.
So I unplugged my sdcard and changed the root partition back from the usb-drive to the sdcard in the boot.ini. After that I was able to access the device and the DietpI-folder (now on the sdcard) wasn’t empty (as it should be and logically couldn’t be).
Here are a few more infos:
Device I’m using Odroid Xu4
SdCard: Kingston 8GB
USB-Drive Transcend SDD 32gb TS32GSSD 370 connected via cloudshell
Software installed: webmin, samba, pihole
last command: dietpu-upgrade && reboot
PSU: official one of Odroid for the XU4
The not so useful ramlog cause it is the one generated using the sdcard as root-device ( the generated on on the usb-card isn’t accessible):
systemctl status dietpi-ramlog -l
● dietpi-ramlog.service - DietPi-RAMlog
Loaded: loaded (/etc/systemd/system/dietpi-ramlog.service; enabled)
Active: active (exited) since Fr 2017-03-03 21:00:39 CET; 2 days ago
Process: 631 ExecStart=/bin/bash -c /boot/dietpi/dietpi-ramlog 0 (code=exited, status=0/SUCCESS)
Mär 03 21:00:38 dietpiserver systemd[1]: Starting DietPi-RAMlog...
Mär 03 21:00:38 dietpiserver bash[631]: DietPi-Ramlog: Starting
Mär 03 21:00:39 dietpiserver bash[631]: chown: invalid user: ‘debian-tor:nogroup’
Mär 03 21:00:39 dietpiserver bash[631]: DietPi-Ramlog: Completed
Mär 03 21:00:39 dietpiserver systemd[1]: Started DietPi-RAMlog.
When more infos are needed plz let me know.
Thx for your support!!
Michael
Just a (belated) report on my issues with OrangePi PC Plus and the DietPi folder.
I’ve reinstalled the available image (OrangePi PC) from the Download section, and immediately did an upgrade - it was upgraded to 144, and I haven’t had any related problems since (almost a week). So, for me the “disappearing DietPi folder” issue is resolved.
Thanks Fourdee!
Does anyone know of a way to patch this remotely?
Thanks in advance.
Device used : Odroid C1+
Software installed (both through dietpi-software and manually): None, freh image writen to SD Card, First boot
What was the last command run, before this occurred (eg: dietpi-update): N/A
PSU used (eg: Official RPi 5v/2A): Official Hardkernel PSU (works finr for other Odroid’s)
SD card used: GoodRAM 16 GB UHS-I
fstab entries (hide any pass worded network drives)
#Samba Client------------------------------------------------------
#/mnt/samba . Please use dietpi-config and the Networking Options: NAS menu to setup this mount
#FTP Client Mount--------------------------------------------------
#/mnt/ftp_client . Please use dietpi-config and the Networking Options: NAS menu to setup this mount
#NFS Client Mount--------------------------------------------------
#/mnt/nfs_client . Please use dietpi-config and the Networking Options: NAS menu to setup this mount
#TMPFS / MISC ------------------------------------------------------
proc /proc proc defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,nodev,nosuid,mode=1777 0 0
tmpfs /var/log tmpfs defaults,size=20m,noatime,nodev,nosuid,mode=1777 0 0
tmpfs /DietPi tmpfs defaults,size=10m,noatime,nodev,nosuid,mode=1777 0 0
#Internal Drives---------------------------------------------------
UUID=A8BB-B5EF /boot auto defaults,noatime,nofail 0 0
UUID=036991cc-0afd-4758-a0bb-05fef1b614dd / auto defaults,noatime,nofail 0 0
DietPi-RAMlog status
systemctl status dietpi-ramlog -l
● dietpi-ramlog.service - DietPi-RAMlog
Loaded: loaded (/etc/systemd/system/dietpi-ramlog.service; enabled)
Active: failed (Result: exit-code) since Thu 2018-01-18 20:07:04 GMT; 4min 55s ago
Jan 18 20:07:03 DietPi bash[514]: /bin/bash: /var/tmp/dietpi/logs/dietpi-ramlog.log: Read-only file system
Jan 18 20:07:04 DietPi systemd[1]: dietpi-ramlog.service: control process exited, code=exited status=1
Jan 18 20:07:04 DietPi systemd[1]: Failed to start DietPi-RAMlog.
Jan 18 20:07:04 DietPi systemd[1]: Unit dietpi-ramlog.service entered failed state.
GoodRAM 16 GB UHS-I
/var/tmp/dietpi/logs/dietpi-ramlog.log: Read-only file system
I’am 100% certain this is due to the instability of the GoodRAM SD card. Please use a well branded/established SD card for stability, eg:
You were correct, I took my old Sandisk UHS 16GB and … The result was the same…
But luckily I found and old image of v145 and writen it to both.
GoodRAM - no luck (No Ethernet controller found error)
Sandisk - It works!!!
So here, any idea why the new 6.0 image in the download section is causing issues no matter what SD Card is used?
EDIT>
NVM, tried yet another SD, v160 went on without problems with missing Folder.
However, now I am facing an issue with NTPD: Waiting for completion of time sync (7/30) and so on untill 30/30.
18 Jan 20:07:06 ntpd[801]: proto: precision = 1.000 usec
18 Jan 20:07:06 ntpd[801]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
18 Jan 20:07:06 ntpd[801]: Listen and drop on 1 v6wildcard :: UDP 123
18 Jan 20:07:06 ntpd[801]: Listen normally on 2 lo 127.0.0.1 UDP 123
18 Jan 20:07:06 ntpd[801]: Listen normally on 3 lo ::1 UDP 123
18 Jan 20:07:06 ntpd[801]: peers refreshed
18 Jan 20:07:06 ntpd[801]: Listening on routing socket on fd #20 for interface updates
18 Jan 20:07:06 ntpd[801]: Deferring DNS for 0.debian.pool.ntp.org 10
18 Jan 20:07:06 ntpd[801]: Deferring DNS for 1.debian.pool.ntp.org 10
18 Jan 20:07:06 ntpd[801]: Deferring DNS for 2.debian.pool.ntp.org 10
18 Jan 20:07:06 ntpd[801]: Deferring DNS for 3.debian.pool.ntp.org 10
18 Jan 20:07:06 ntpd[821]: signal_no_reset: signal 17 had flags 4000000
18 Jan 20:07:08 ntpd[821]: host name not found: 0.debian.pool.ntp.org
18 Jan 20:07:08 ntpd[821]: host name not found: 1.debian.pool.ntp.org
18 Jan 20:07:08 ntpd[821]: host name not found: 2.debian.pool.ntp.org
18 Jan 20:07:08 ntpd[821]: host name not found: 3.debian.pool.ntp.org
18 Jan 20:07:09 ntpd[801]: Listen normally on 4 eth0 fe80::21e:6ff:fe20:58b UDP 123
18 Jan 20:07:09 ntpd[801]: peers refreshed
18 Jan 20:07:11 ntpd[821]: host name not found: 0.debian.pool.ntp.org
18 Jan 20:07:11 ntpd[821]: host name not found: 1.debian.pool.ntp.org
18 Jan 20:07:11 ntpd[821]: host name not found: 2.debian.pool.ntp.org
18 Jan 20:07:11 ntpd[821]: host name not found: 3.debian.pool.ntp.org
18 Jan 20:07:15 ntpd[801]: Deleting interface #4 eth0, fe80::21e:6ff:fe20:58b#123, interface stats: received=0, sent=0, dropped=0, active_time=6 secs
18 Jan 20:07:15 ntpd[801]: peers refreshed
18 Jan 20:07:21 ntpd[801]: ntpd exiting on signal 15
18 Jan 20:07:21 ntpd[821]: ntpd exiting on signal 15
18 Jan 20:07:23 ntpd[1556]: proto: precision = 1.000 usec
18 Jan 20:07:23 ntpd[1556]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
18 Jan 20:07:24 ntpd[1556]: Listen and drop on 1 v6wildcard :: UDP 123
18 Jan 20:07:24 ntpd[1556]: Listen normally on 2 lo 127.0.0.1 UDP 123
18 Jan 20:07:24 ntpd[1556]: Listen normally on 3 eth0 192.168.1.123 UDP 123
18 Jan 20:07:24 ntpd[1556]: Listen normally on 4 lo ::1 UDP 123
18 Jan 20:07:24 ntpd[1556]: Listen normally on 5 eth0 fe80::21e:6ff:fe20:58b UDP 123
18 Jan 20:07:24 ntpd[1556]: peers refreshed
18 Jan 20:07:24 ntpd[1556]: Listening on routing socket on fd #22 for interface updates
18 Jan 20:09:49 ntpd[1556]: ntpd exiting on signal 15
18 Jan 20:09:51 ntpd[2136]: proto: precision = 1.000 usec
18 Jan 20:09:51 ntpd[2136]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
18 Jan 20:09:51 ntpd[2136]: Listen and drop on 1 v6wildcard :: UDP 123
18 Jan 20:09:51 ntpd[2136]: Listen normally on 2 lo 127.0.0.1 UDP 123
18 Jan 20:09:51 ntpd[2136]: Listen normally on 3 eth0 192.168.1.123 UDP 123
18 Jan 20:09:51 ntpd[2136]: Listen normally on 4 lo ::1 UDP 123
18 Jan 20:09:51 ntpd[2136]: Listen normally on 5 eth0 fe80::21e:6ff:fe20:58b UDP 123
18 Jan 20:09:51 ntpd[2136]: peers refreshed
18 Jan 20:09:51 ntpd[2136]: Listening on routing socket on fd #22 for interface updates
18 Jan 20:10:35 ntpd[2136]: ntpd exiting on signal 15
EDIT 2
Tried a workaround: https://dietpi.com/forum/t/time-sync-with-ntpd-issue/1271/1 Resulted in the same…
Try a full format on the SD card prior to v6.2 image write, on the Sandisk:
https://github.com/Fourdee/DietPi/issues/769#issuecomment-283030267
However, now I am facing an issue with NTPD: Waiting for completion of time sync (7/30) and so on untill 30/30.
We are aware of this and we are looking into it:
https://github.com/Fourdee/DietPi/issues/1580
In the mean time, set NTP back to “Boot + daily” and try changing the NTPD mirror in:
dietpi-config > Networking Options: NAS/MISC > NTPD mirror
Hi, I’m having the same problem after a reboot: The DietPi folder is empty
Running on C2 with latest Dietpi package (installed it yesterday).
For a quick solution: is there any way to replace the Dietpi system files or should I just re install Dietpi on the SD?
root@DietPi:/# mount -o remount,rw /dev/nvme0n1p2 /
root@DietPi:/# systemctl start dietpi-ramdisk
Job for dietpi-ramdisk.service failed. See 'systemctl status dietpi-ramdisk.service' and 'journalctl -xn' for details.
root@DietPi:/# systemctl status dietpi-ramdisk.service
● dietpi-ramdisk.service - DietPi-RAMdisk
Loaded: loaded (/etc/systemd/system/dietpi-ramdisk.service; enabled)
Active: failed (Result: exit-code) since Thu 2018-03-08 14:24:54 -03; 7s ago
Process: 648 ExecStart=/bin/bash -c /boot/dietpi/dietpi-ramdisk 0 &>> /var/tmp/dietpi/logs/dietpi-ramdisk.log (code=exited, status=1/FAILURE)
Mar 08 14:24:54 DietPi systemd[1]: Starting DietPi-RAMdisk...
Mar 08 14:24:54 DietPi bash[648]: /bin/bash: /var/tmp/dietpi/logs/dietpi-ramdisk.log: No such file or directory
Mar 08 14:24:54 DietPi systemd[1]: dietpi-ramdisk.service: control process exited, code=exited status=1
Mar 08 14:24:54 DietPi systemd[1]: Failed to start DietPi-RAMdisk.
Mar 08 14:24:54 DietPi systemd[1]: Unit dietpi-ramdisk.service entered failed state.
root@DietPi:/# systemctl status dietpi-ramlog -l
● dietpi-ramlog.service - DietPi-RAMlog
Loaded: loaded (/etc/systemd/system/dietpi-ramlog.service; enabled)
Active: failed (Result: exit-code) since Thu 2018-03-08 14:20:47 -03; 4min 54s ago
Process: 482 ExecStart=/bin/bash -c /boot/dietpi/dietpi-ramlog 0 &>> /var/tmp/dietpi/logs/dietpi-ramlog.log (code=exited, status=1/FAILURE)
Mar 08 14:20:47 DietPi bash[482]: /bin/bash: /var/tmp/dietpi/logs/dietpi-ramlog.log: No such file or directory
Mar 08 14:20:47 DietPi systemd[1]: dietpi-ramlog.service: control process exited, code=exited status=1
Mar 08 14:20:47 DietPi systemd[1]: Failed to start DietPi-RAMlog.
Mar 08 14:20:47 DietPi systemd[1]: Unit dietpi-ramlog.service entered failed state.
root@DietPi:/# cat /etc/dietpi/logs/dietpi-ramdisk.log
cat: /etc/dietpi/logs/dietpi-ramdisk.log: No such file or directory
root@DietPi:/# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 15G 1.5G 13G 11% /
udev 10M 0 10M 0% /dev
tmpfs 344M 5.6M 338M 2% /run
tmpfs 859M 0 859M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 859M 0 859M 0% /sys/fs/cgroup
tmpfs 10M 0 10M 0% /DietPi
tmpfs 20M 8.0K 20M 1% /var/log
tmpfs 858M 0 858M 0% /tmp
/dev/mmcblk0p1 128M 46M 82M 36% /boot
Hi
Please paste results:
ls -lha /var/tmp/dietpi/logs
If it doesn’t exist, create it and reboot:
mkdir -p /var/tmp/dietpi/logs
reboot
I’m having the same problem. I tried to use dietpi-software to install the Plex server. The SD card may have filled up, lots of error messages about not having space. So the install failed and then when I rebooted I got the same empty dietpi folder error. After making some space the error persists.
Raspberry pi 3, 32GB SD card, DietPi v6.3
root@DietPi:~# ls -lha /var/tmp/dietpi/logs
total 296K
drwxr-xr-x 2 root root 4.0K Mar 7 11:52 .
drw-rw---- 3 dietpi dietpi 4.0K Feb 18 13:59 …
-rw-r–r-- 1 root root 217K Mar 7 07:58 dietpi-firstrun-setup.log
-rw-r–r-- 1 root root 1.9K Mar 8 18:32 dietpi-ramdisk.log
-rw-r–r-- 1 root root 1.1K Mar 8 18:32 dietpi-ramlog.log
-rw-r–r-- 1 root root 173 Mar 8 18:29 dietpi-software_apt.log
-rw-r–r-- 1 root root 44K Mar 7 11:54 dietpi-update.log
-rw-r–r-- 1 root root 211 Feb 18 13:39 fs_expand.log
-rw-r–r-- 1 root root 1.8K Feb 18 13:39 fs_partition_resize.log
I found what was wrong but not why it happened.
/etc/fstab was BLANK and the filesystem was read only. I copied the fstab file from the image and everything seems fine.
Then I installed plexserver without issue. The only thing I can think of is that I had a manual entry on fstab to load a samba share. Now I’m mounting it through diepi-config and I left fstab as it was.
I’m a new user but unfortunately I believe I just joined this club. Installed DietPi on a fresh Odroid C2 w/ a Sandisk 128gb card. Had things up and running and was tinkering with it. Connected an external USB drive and rebooted – and directory is now empty. Boots and I can login but can’t run any dietpi commands.
dietpi@DietPi:~$ sudo ls -lha /var/tmp/dietpi/logs
total 80K
drwxr-xr-x 2 root root 4.0K Apr 29 13:34 .
drw-rw---- 3 dietpi dietpi 4.0K Jan 10 07:16 ..
-rw-r--r-- 1 root root 28K Apr 29 13:37 dietpi-firstrun-setup.log
-rw-r--r-- 1 root root 1.7K Apr 30 10:59 dietpi-ramdisk.log
-rw-r--r-- 1 root root 940 Apr 30 10:59 dietpi-ramlog.log
-rw-r--r-- 1 root root 0 Apr 30 11:37 dietpi-software_apt.log
-rw-r--r-- 1 root root 28K Apr 29 13:35 dietpi-update.log
-rw-r--r-- 1 root root 213 Dec 31 1969 fs_expand.log
-rw-r--r-- 1 root root 1.8K Dec 31 1969 fs_partition_resize.log