DietPi-RAMdisk | /DietPi folder empty after reboot

[Fourdee]

Reports:

http://dietpi.com/phpbb/viewtopic.php?f=11&t=1148&start=20#p5145
http://dietpi.com/phpbb/viewtopic.php?f=11&t=1148&start=20#p5147

Appears random (John).

Add additional debugging to dietpi-ramdisk.service

[Fourdee]

@midwan

Which PSU + SD are you using on the Pine when it caused this: https://github.com/Fourdee/DietPi/issues/726#issue-202412586

[Fourdee]

John reports possible flaky SD card (Kinsgton 8 GD SD card) causing this issue.

[midwan]

@Fourdee
I used the Official Raspberry Pi PSU (5V, 2.5A) and a Sandisk Extreme 16GB SD card.

[Fourdee]

@midwan

Thanks.

When the folder is missing, can you please do the following:
http://dietpi.com/phpbb/viewtopic.php?f=11&t=1148&start=20#p5143

Mostly interested in results of:

systemctl status dietpi-ramlog -l

[WolfganP]

I think the issue is even an step earlier, /boot/dietpi is empty as well so dietpi-ramlog and other scripts aren't present in the system.

[Fourdee]

I think the issue is even an step earlier, /boot/dietpi is empty as well so dietpi-ramlog and other scripts aren't present in the system.

Seems to vary:

• Boot exists : http://dietpi.com/phpbb/viewtopic.php?f=11&t=1148&start=20#p5147
• Boot exists (script corrupted) : http://dietpi.com/phpbb/viewtopic.php?f=11&t=1148&start=20#p5145
• Boot exists-ish (FSCK recovery): http://dietpi.com/phpbb/viewtopic.php?f=11&t=1148#p4868

[midwan]

@Fourdee

In my case, /boot/dietpi does have contents:

root@DietPi:~# ls -al /boot/dietpi
total 116
drwxr-xr-x 3 root root  4096 Jan 22 16:58 .
drwxr-xr-x 5 root root 16384 Jan  1  1970 ..
-rwxr-xr-x 1 root root 13693 Jan 22 16:47 boot
-rwxr-xr-x 1 root root     2 Jan 22 16:47 .dietpi-autostart_index
-rwxr-xr-x 1 root root  5207 Jan 22 16:47 dietpi-cpuinfo
-rwxr-xr-x 1 root root  8299 Jan 22 16:47 dietpi-cron
-rwxr-xr-x 1 root root 33446 Jan 22 16:47 dietpi-drive_manager
-rwxr-xr-x 1 root root  5420 Jan 22 16:47 dietpi-funtime
-rwxr-xr-x 1 root root    83 Jan 22 16:47 .dietpi-process_tool
-rwxr-xr-x 1 root root     4 Jan 22 16:47 .dietpi-survey
drwxr-xr-x 2 root root  2048 Jan 22 16:58 func
-rwxr-xr-x 1 root root   112 Jan 22 16:47 .hw_model
-rwxr-xr-x 1 root root  4277 Jan 22 16:47 .installed
-rwxr-xr-x 1 root root     2 Jan 22 16:47 .install_stage
-rwxr-xr-x 1 root root    24 Jan 22 16:47 .network
-rwxr-xr-x 1 root root   123 Jan 22 16:47 .uninstalled
-rwxr-xr-x 1 root root     2 Jan 22 16:47 .update_stage
-rwxr-xr-x 1 root root     4 Jan 22 16:47 .version

Here are the results, as requested:

• Device used: Pine64, 2GB model
• Software installed: MATE desktop, Plex Media Server, Samba server. Though they worked fine until I did the firmware update.
• Last command run: Firmware update. It did the self-update first (was already on the latest version) then downloaded the firmware without errors, proceeded to extract it, then reboot.
• PSU used: Official RPI (5V, 2.5A)
• SD card used: SanDisk Ultra 16GB
• fstab entries:

root@DietPi:~# cat /etc/fstab
#Internal Drives---------------------------------------------------
proc            /proc           proc    defaults                                                                                        0 0
/dev/mmcblk0p1  /boot           auto    defaults,noatime,discard                                                        0 2
/dev/mmcblk0p2  /               auto    defaults,noatime,discard                                                        0 1
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

#External Drives---------------------------------------------------
#NB: Please use dietpi-drive_manager to setup and control your external drives.
#/dev/sda1       /mnt/usb_1      auto     defaults,noatime,nofail,x-systemd.automount  0 0
#/dev/sdb1       /mnt/usb_2      auto     defaults,noatime,nofail,x-systemd.automount  0 0
#/dev/sdc1       /mnt/usb_3      auto     defaults,noatime,nofail,x-systemd.automount  0 0
#/dev/sdd1       /mnt/usb_4      auto     defaults,noatime,nofail,x-systemd.automount  0 0
#/dev/sde1       /mnt/usb_5      auto     defaults,noatime,nofail,x-systemd.automount  0 0

#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
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that

DietPi-RAMlog status:

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 Sun 2017-01-22 18:05:43 GMT; 6min ago
  Process: 543 ExecStart=/bin/bash -c /boot/dietpi/dietpi-ramlog 0 (code=exited, status=127)

Jan 22 18:05:42 DietPi bash[543]: /bin/bash: /boot/dietpi/dietpi-ramlog: No such file or directory
Jan 22 18:05:43 DietPi systemd[1]: dietpi-ramlog.service: control process exited, code=exited status=127
Jan 22 18:05:43 DietPi systemd[1]: Failed to start DietPi-RAMlog.
Jan 22 18:05:43 DietPi systemd[1]: Unit dietpi-ramlog.service entered failed state.

I hope that helps!

[Fourdee]

@midwan

Thanks 👍

Looks like some of the DietPi scripts are missing from /boot:

root@DietPi:~# ls -al /boot/dietpi

/bin/bash: /boot/dietpi/dietpi-ramlog: No such file or directory

I'll run some tests.

[Fourdee]

@midwan

Whats the size used in /boot?

df -h

[Fourdee]

Ok i've enabled verbose debugging for dietpi-ramdisk.

Logs will be saved to:
/etc/dietpi/logs/dietpi-ramdisk.log

This won't be enabled until v143 is released (or use of testing branch: https://github.com/Fourdee/DietPi/blob/master/TESTING-BRANCH.md), however, once the issue occurs, logs should give us much needed clues.

[Fourdee]

Just wondering if this is a simple case of service running before local-fs.target

Adding following should prevent that:
After=local-fs.target

[Fourdee]

Debugging enabled for v143:

If you experience and issues with missing /DietPi or /boot files, on a fresh install , please paste results of the following command

cat /etc/dietpi/logs/dietpi-ramdisk.log

[Fourdee]

• Report 1: http://dietpi.com/phpbb/viewtopic.php?f=11&t=1148&start=20#p5346. Appears /DietPi/.ramdisk already exists on a fresh boot, causing DietPi-RAMdisk to not copy files to RAM, then, during shutdown, as no RAMdisk, wipes respective /boot scripts.

[WolfganP]

@Fourdee , just to avoid reinstalling from scratch, is there any workaround (ie wget github.com/xyz... ) to recover the /dietpi folder and get the system back to full functionality? (and then dietpi-upgrade for this changes be incorporated in future reboots)
Thx

[Fourdee]

@WolfganP

recover the /dietpi folder and get the system back to full functionality?

You could recover the scripts from git, however, unfortunately, all the DietPi settings cannot be recovered. These are created and unique to your system installation and setup.

root@DietPi:~# ls -lha /DietPi/dietpi/.
./                       .dietpi-survey           .network
../                      .dietpi-sync_exclude     .patch_emr
.dietpi-autostart_index  .dietpi-sync_settings    .uninstalled
.dietpi-backup_settings  .hw_model                .update_available
.dietpi-cloudshell       .installed               .update_stage
.dietpi-process_tool     .install_stage           .version

Following contains dietpi-software software states and settings, without this file, DietPi assumes nothing is installed and system is essentially a fresh installation.

 .installed

Following contains dietpi-config settings:

/DietPi/dietpi.txt

And not to forget the config.txt for RPi is also in /DietPi

So yes, you could recover DietPi scripts, however, not recommended due to loss of generated settings files, will put DietPi into a "new installation" state.

[joshuamcginnis]

I just experienced this exact issue on my Odroid C2 with a fresh install on an emmc.

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 Tue 2017-01-31 17:32:10 PST; 2min 27s ago
  Process: 511 ExecStart=/bin/bash -c /boot/dietpi/dietpi-ramlog 0 (code=exited, status=2)

Jan 31 17:32:10 andromeda bash[511]: /boot/dietpi/dietpi-ramlog: line 1: syntax error near unexpected token `s", sendername="%'
Jan 31 17:32:10 andromeda bash[511]: /boot/dietpi/dietpi-ramlog: line 1: `(sender)s", sendername="%(sendername)s"]'
Jan 31 17:32:10 andromeda systemd[1]: dietpi-ramlog.service: control process exited, code=exited status=2
Jan 31 17:32:10 andromeda systemd[1]: Failed to start DietPi-RAMlog.
Jan 31 17:32:10 andromeda systemd[1]: Unit dietpi-ramlog.service entered failed state.

Let me know If there's any other diagnostic information I provide.

[Fourdee]

Report (user pi):
http://dietpi.com/phpbb/viewtopic.php?f=11&t=1135&p=5391#p5391

[Fourdee]

@joshuamcginnis

Let me know If there's any other diagnostic information I provide.

Thanks 👍

Could you please provide the results of:

cat /etc/dietpi/logs/dietpi-ramdisk.log

And, if possible, upload the file so we can check state:

/boot/dietpi/dietpi-ramlog

[Fourdee]

Boards reported with this issue occurring:

• RPi 2/3 | + FAT16
• C2 | + FAT32/lba
• OPi Zero | + FAT16/lba
• OPi Plus | + FAT16/lba

All images above are using the updated image creation process.

[Fourdee]

@midwan @WolfganP
Hi guys,

Can you remember how you wrote the image to SD card, win32diskimager.exe ?

[midwan]

@Fourdee
I usually do it with Win32DiskImager, but lately I've been testing Etcher also.

[joshuamcginnis]

@Fourdee

cat /etc/dietpi/logs/dietpi-ramdisk.log
DietPi-Ramdisk: Already running
DietPi-Ramdisk: Stopping
DietPi-Ramdisk: Completed
DietPi-Ramdisk: Starting
DietPi-Ramdisk: Completed
DietPi-Ramdisk: Stopping
DietPi-Ramdisk: Completed
DietPi-Ramdisk: Starting
DietPi-Ramdisk: Completed
DietPi-Ramdisk: Starting
DietPi-Ramdisk: Completed
DietPi-Ramdisk: Starting
DietPi-Ramdisk: Completed
/boot/dietpi/dietpi-ramdisk: line 2: /: Is a directory
/boot/dietpi/dietpi-ramdisk: line 3: tmpfs: command not found
/boot/dietpi/dietpi-ramdisk: line 4: tmpfs: command not found
/boot/dietpi/dietpi-ramdisk: line 5: tmpfs: command not found
/boot/dietpi/dietpi-ramdisk: line 75: unexpected EOF while looking for matching `"'
/boot/dietpi/dietpi-ramdisk: line 96: syntax error: unexpected end of file

dietpi-ramlog.txt

I installed to emmc via: sudo dd if=path/to_img of=/dev/disk4

[Fourdee]

@joshuamcginnis

Thanks, look like a possible script/echo leak in tty. I'll retrace steps in code, see if we can figure this one out.

[midwan]

@Fourdee
Not sure if you still need this, but just in case:

root@DietPi:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p2   15G  2.8G   11G  21% /
devtmpfs        962M     0  962M   0% /dev
tmpfs           995M     0  995M   0% /dev/shm
tmpfs           995M  8.5M  986M   1% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           995M     0  995M   0% /sys/fs/cgroup
tmpfs            10M     0   10M   0% /DietPi
tmpfs            20M  4.0K   20M   1% /var/log
tmpfs           995M     0  995M   0% /tmp
/dev/mmcblk0p1   50M   13M   38M  26% /boot
tmpfs           199M     0  199M   0% /run/user/0

[WolfganP]

@Fourdee I use Rufus for the img writing.

[Fourdee]

I believe this issue may be related to a few others users are reporting, eg:

• C2 wont boot on EMMC after updating.

I'am going to change the way we finalize images as I believe this may be a cause. New system with new methods. Once the main culprit images have been updated, I'll post here and we'll need some testers:
https://github.com/Fourdee/DietPi/issues/719#issuecomment-276695879

I don't believe PSU/SD is an issue, but it can never be ruled out. Hopefully the above provides a solution.

[Fourdee]

Ok, C2 image:

• http://dietpi.com/phpbb/viewtopic.php?f=11&t=1280&p=5476#p5467

Loopback reports FAT16, 7Zip reports FAT32:

---

When running a check/repair on this partition (/boot), image is then corrupted with I/O errors on next loopback and mount.

---

Test:

• Manually delete and recreate partitions, boot is now fat32
• Copy /boot and /rootfs files back over
• Write image
• Power on
• 🈴 Hangs at:

MMC Size : 128 GB
----------------------------------
reading boot-logo.bmp.gz
** Unable to read file boot-logo.bmp.gz **
reading boot-logo.bmp
** Unable to read file boot-logo.bmp **
movi: the partiton 'logo' is reading...

MMC read: dev # 0, block # 58976, count 4096 ... 4096 blocks read: OK
hpd_state=1
[CANVAS]addr=0x3f800000 width=3840, height=1440

set hdmitx VIC = 16
hdmitx phy setting done
set hdmitx VIC = 16
hdmitx phy setting done
Error: Bad gzipped data
There is no valid bmp file at the given address
Net:   Meson_Ethernet
Hit [Enter] key twice to stop autoboot:  0
reading boot.ini
2343 bytes read in 3 ms (762.7 KiB/s)
cfgload: applying boot.ini...
cfgload: setenv m "720p60hz"
cfgload: setenv m_bpp "32"
cfgload: setenv hpd "true"
cfgload: setenv condev "console=tty0"
cfgload: setenv mesontimer "1"
cfgload: setenv nographics "0"
cfgload: setenv bootargs "root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro ${condev} no_console_suspend hdmimode=${m} m_bpp=${m_bpp} vout=${vout} fsck.repair=yes net.ifnames=0 elevator=noop disablehpd=${hpd}"
cfgload: setenv loadaddr "0x11000000"
cfgload: setenv dtb_loadaddr "0x1000000"
cfgload: setenv initrd_loadaddr "0x13000000"
cfgload: fatload mmc 0:1 ${initrd_loadaddr} uInitrd
reading uInitrd
4239351 bytes read in 102 ms (39.6 MiB/s)
cfgload: fatload mmc 0:1 ${loadaddr} Image
reading Image
12947760 bytes read in 304 ms (40.6 MiB/s)
cfgload: fatload mmc 0:1 ${dtb_loadaddr} meson64_odroidc2.dtb
reading meson64_odroidc2.dtb
29164 bytes read in 5 ms (5.6 MiB/s)
cfgload: fdt addr ${dtb_loadaddr}
cfgload: if test "${mesontimer}" = "0"; then fdt rm /meson_timer; fdt rm /cpus/cpu@0/timer; fdt rm /cpus/cpu@1/timer; fdt rm /cpus/cpu@2/timer; fdt rm /cpus/cpu@3/timer; fi
cfgload: if test "${mesontimer}" = "1"; then fdt rm /timer; fi
cfgload: if test "${nographics}" = "1"; then fdt rm /reserved-memory; fdt rm /aocec; fi
cfgload: if test "${nographics}" = "1"; then fdt rm /meson-fb; fdt rm /amhdmitx; fdt rm /picdec; fdt rm /ppmgr; fi
cfgload: if test "${nographics}" = "1"; then fdt rm /meson-vout; fdt rm /mesonstream; fdt rm /meson-fb; fi
cfgload: if test "${nographics}" = "1"; then fdt rm /deinterlace; fdt rm /codec_mm; fi
cfgload: booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (uncompressed)
   Data Size:    4239287 Bytes = 4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
load dtb from 0x1000000 ......
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
   Loading Ramdisk to 73b28000, end 73f32fb7 ... OK
   Loading Device Tree to 000000001fff5000, end 000000001ffff1eb ... OK

Starting kernel ...

uboot time: 3968366 us

cfgload: setenv bootargs "root=UUID=e139ce78-9841-40fe-8823-96a304a09859

root=/dev/mmcblk0p2, because regenerating partitions will create a different UUID.

• 🈯️ Works
• 🈴 http://oph.mdrjr.net is now offline, apt-get update hangs 100% [Connecting to oph.mdrjr.net (96.47.231.244)] Happy days lol

[Fourdee]

Lets update our images (also includes updated dietpi-ramdisk forcing data sync after run), recreating the partitions after image read:
https://github.com/Fourdee/DietPi/issues/719#issuecomment-277533451

• 🈯️ C2 | tested, now live download
• 🈯️ RPi | tested, now live download
• 🈴 OPi Zero ~~ FAT16/lba | /boot/armbianEnv.txt > rootdev=/dev/mmcblk0p2 🈴 | /boot/armbianEnv.txt > rootdev=UUID=xxxxxx 🈴 . Previous image same result on 2 SD cards, serial out dead, ~~ Board failure 🈴
• OPi Plus | + FAT16/lba

[WolfganP]

@Fourdee I'm sorry I've missed the images' update. I was waiting for a new version to re-write my SD and start config from scratch to test and get my system back to stability. Do you suggest to wait to v144 to test the new images + new commits related to this issue?

[Fourdee]

@WolfganP

Do you suggest to wait to v144 to test the new images + new commits related to this issue?

You can test these images now.

The new images are essentially v143.5 and contain all the current commits. In other words, they are v144 at this time, containing all the updated code.

[Fourdee]

Ok, informed users on forums, awaiting test results of the new images, from users who experienced the missing /DietPi folder/files:
http://dietpi.com/phpbb/viewtopic.php?f=11&t=1148&p=5617#p5617

[WolfganP]

I rebuilt my SD card from scratch a few days ago with the 1.43.5 RasPi image, using the system as plex media & file server, no issues observed so far. Thanks a lot @Fourdee !

[Fourdee]

@WolfganP

no issues observed so far

Excellent, but please let us know if this changes.

[Fourdee]

No further reports using the updated images. All images have now been updated using our new image creation procedure and force sync in dietpi-ramlog.

Marking as closed. Will reopen if further reports come in, using the latest DietPi v145 images.

[WolfganP]

Just to report that I lost /Dietpi folder again today. Something weird about chown in the logs:

```root@DietPi:~$ systemctl status dietpi-ramlog -l
● dietpi-ramlog.service - DietPi-RAMlog
Loaded: loaded (/etc/systemd/system/dietpi-ramlog.service; enabled)
Active: active (exited) since Tue 2017-04-11 22:53:07 UTC; 12min ago
Process: 399 ExecStart=/bin/bash -c /boot/dietpi/dietpi-ramlog 0 (code=exited, status=0/SUCCESS)

Apr 11 22:53:06 DietPi systemd[1]: Starting DietPi-RAMlog...
Apr 11 22:53:07 DietPi bash[399]: DietPi-Ramlog: Starting
Apr 11 22:53:07 DietPi bash[399]: chown: invalid user: ‘debian-tor:nogroup’
Apr 11 22:53:07 DietPi bash[399]: DietPi-Ramlog: Completed
Apr 11 22:53:07 DietPi systemd[1]: Started DietPi-RAMlog.

[Fourdee]

@WolfganP

Thanks for the report,

chown: invalid user: ‘debian-tor:nogroup’

This is for the RAMlog, we have a special case permission for tor log files, safe to ignore.

Whats the status of RAMdisk /DietPi?:

systemctl status dietpi-ramdisk -l
cat /etc/dietpi/logs/dietpi-ramdisk.log

[msdos]

I received the same error, but I think the problem is the SD card, it's a really old 2gb with only DietPi Jessie installed for the first time. I'm going to stop using the card instead of spending more time with it. I'm posting here just to say that dmesg gives me info as well, maybe it's useful for your debugging approaches.

[   46.855682] FAT-fs (mmcblk0p1): error, corrupted directory (invalid entries)
[   46.855690] FAT-fs (mmcblk0p1): Filesystem has been set read-only
[   47.178695] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[   47.178855] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[   47.698696] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[   47.698891] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[   47.699018] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[   48.326605] Adding 815100k swap on /var/swap.  Priority:-1 extents:5 across:864252k SSFS
[  613.251797] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[  613.783637] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)

[douglasmiranda]

Another common cause for these kind of errors is if you have some volume on /etc/fstab that you are mounting on boot and it fails. Sometimes it fails before the system mounts the first volumes.

So you wait a while and the system will let you inform your root password to enter in maintenance mode, then you can edit your /etc/fstab file, remove / comment the entries that may be the cause of error. Check with mount -a, if there are no errors, just reboot.

[Fffrank]

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

[Fourdee]

@Fffrank

Thanks for the report. To the best of our knowledge, this issue is always related to hardware instability.

Please paste results of the logs:

systemctl status dietpi-ramdisk -l
cat /etc/dietpi/logs/dietpi-ramdisk.log
dmesg | grep mmc

Also, which power supply are you running?

[Fffrank]

@Fourdee This power supply: https://www.amazon.com/gp/product/B0719SX3GC/

dietpi@DietPi:~$ sudo systemctl status dietpi-ramdisk -l Failed to get D-Bus connection: Unknown error -1 dietpi@DietPi:~$ sudo cat /etc/dietpi/logs/dietpi-ramdisk.log cat: /etc/dietpi/logs/dietpi-ramdisk.log: No such file or directory dietpi@DietPi:~$ dmesg | grep mmc [ 0.000000] Kernel command line: root=/dev/mmcblk0p2 rootwait ro console=tty0 no_console_suspend hdmimode=720p60hz m_bpp=32 vout= fsck.repair=yes net.ifnames=0 elevator=noop disablehpd=true [ 0.483615] aml_sd_emmc_probe: line 2898 [ 0.483625] mmc driver version: 1.07, 2015-01-21: fix a bug in tuning which caused eMMC data CRC error [ 0.483983] aml_sd_emmc_reg_init 621 [ 0.543079] [aml_sd_emmc_probe] aml_sd_emmc_probe() success! [ 0.543111] aml_sd_emmc_probe: line 2898 [ 0.545943] aml_sd_emmc_reg_init 621 [ 0.546136] get property: pinname, str:emmc [ 0.601764] [aml_sd_emmc_probe] aml_sd_emmc_probe() success! [ 0.751809] sd_emmc_regs->gclock =0x100024c, sd_emmc_regs->gadjust =0x42000 [ 0.752151] mmcblk0: sd:aaaa SC128 119 GiB [ 0.754293] mmcblk0: p1 p2 [ 0.754587] aml_emmc_hw_reset 1356 [ 0.766771] [aml_sd_emmc_irq] emmc: resp_timeout,vstat:0x2800,virqc:3fff [ 0.766791] aml_sd_emmc_data_thread 2155 emmc: cmd:1 [ 0.766820] emmc: error -110 whilst initialising MMC card [ 5.952218] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: (null) [ 6.470710] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [ 6.564644] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. dietpi@DietPi:~$

[Fourdee]

@Fffrank

[ 0.766820] emmc: error -110 whilst initialising MMC card
[ 6.564644] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Looks like a corrupt SD filesystem. Any recent power cuts? If not, could be SD card failing, or PSU is insufficient (we highly recommend the official RPi PSU's).

You'll need to reinstall DietPi on the SD card.

[mzramna]

this also happends over btrfs filesystem,btrfs does not support swapfile like archives , it should be checked into the instalation script before starting the conversion

[MichaIng]

@mzramna
Many thanks for reporting. For reference: https://github.com/MichaIng/DietPi/issues/1285#issuecomment-484207090

All our images are shipped with ext4 root partition, however we do not check root fs type during DietPi-PREP. Either we need to check and disallow DietPi-PREP on non-ext4 root fs, or, which I like more, simply refuse swap creation and print error on script level. This then also includes manual script usage to create swap on external drive etc.

---

Btw we have an open request to allow swap on BTRFS via separate swap partition: https://github.com/MichaIng/DietPi/issues/1715
But this is nothing we can safely apply to drives with existing content, especially not root fs. And before doing huge efforts, we can simply wait for kernel 5.0 supporting swap files on BTRFS: https://kernelnewbies.org/LinuxChanges/#Linux_5.0.Btrfs_swap_file_support

• But yeah will take a while until that kernel is available for devices, and most (currently supported devices) will most properly never see it 😉.
• Allowing to use a whole partition for swap instead of a swap file is a dedicated reasonable request. So it is then up to the user to create a partition of desired space and the script will just toggle it for swap.

---

Fixed with: https://github.com/MichaIng/DietPi/pull/2720

• Swap creation aborts now if BTRFS is detected