Page 1 of 1

DietPi-ramlog and ramdisk fail ( RPI3 :-( )

Posted: Tue Feb 26, 2019 11:25 am
by Meins321
Hello currently i can NOT boot my dietpi but all the tools are missing from diet-pi :-(

I do have a 3A 5V powersupply from meanwell with a cut MicroUSB cable on it.
No i didn't overclock it! I would like to use it with
MicroSD is a Kingston Industrial 16GB 1U which should be not considered cheap :?

Two Services fail to boot:
RamLog
Ramdisk

Is there any way to repair them in software?

Re: DietPi-ramlog and ramdisk fail ( RPI3 :-( )

Posted: Tue Feb 26, 2019 7:00 pm
by midnightwatcher
I've been having similar problem also recently (Native PC x86-64) on my Z83, latest 6.21.1 version installed. Something is changing/corrupting fstab, so a reboot results in a broken system if fstab is bad. I did a complete re-install yesterday and within an hour after setting everything back up noticed that fstab was changed again after the attached USB drive for my FTP server was unmounted. I saved a backup of fstab just prior, so I overwrote the bad one and then made fstab read-only. Hopefully this temporary fix works until the root cause is found.

viewtopic.php?f=11&t=5618

Re: DietPi-ramlog and ramdisk fail ( RPI3 :-( )

Posted: Wed Feb 27, 2019 8:46 am
by Meins321
Is there a repair method if you don't have a fstab backup?

can i take the files from someone else and just overwrite mine if the install is standard dietpi on my rbpi3 with xfce? :(


Is it maybe related to this topic:
Dietpi Services not starting
viewtopic.php?f=11&t=5591


cat /etc/debian_version
returns debian 9.6

Re: DietPi-ramlog and ramdisk fail ( RPI3 :-( )

Posted: Wed Feb 27, 2019 9:07 am
by midnightwatcher
Don't think so, UUIDs will be different on each device.

Re: DietPi-ramlog and ramdisk fail ( RPI3 :-( )

Posted: Wed Feb 27, 2019 9:45 am
by Meins321
So i can only reinstall including all my software? aww thats bad my gtk development enviroment with ggc is then broken :(

Re: DietPi-ramlog and ramdisk fail ( RPI3 :-( )

Posted: Wed Feb 27, 2019 3:15 pm
by MichaIng
@Meins321
Use dietpi-drive_manager 4 to re-create the fstab file based on current mounts. I will as well identify and add the correct UUIDs. But as RAMdisk failed to start, I guess the above fails.

But actually the df you posted looks fine.

Lets check:

Code: Select all

cat /etc/fstab
systemctl status dietpi-ramdisk
cat /var/tmp/dietpi/logs/dietpi-ramdisk.log
And try the following to manually move DietPi code from disk to RAM:
/boot/dietpi/func/dietpi-ramdisk 0