I installed DietPi on Odroid HC1 in order to replace my former ArchLinuxArm installation on Odroid HC1 because ALARM seems to be abadonware for armv7h now.
The Odroid HC1 is supposed to work as PiHole with unbound, local package mirror for linux distro, nfs shares, ntp-server and radicale-server.
All went surprisingly smooth, only some minor issues were encountered.
DietPi is so unbelievable small with just about 900MB and these dietpi-helpers are great!
Even a noob could be able to install and run it.
When installing PiHole with unbound from optimized packages google DNS is selected during install automatically. This was confusing.
Fortunately after all is installed the right DNS-Server (unbound 127:0:0:1:5335) is choosen automatically.
Only some settings are missing / suboptimal (double caching PiHole/unbound, DNSSEC validation forwarding to clients missing, resolv.conf issues)
But all is nothing worth without a working and relieable way to backup and recover your installation!
DietPi offers dietpi-backup - but that does not really work:
I set the AUTO_SETUP_BACKUP_RESTORE to ‘2’ => non-interactive restore (restore first found backup which lies on the connected SSD) but that will not work as the backup process still ‘warns’ about UUIDs and requires confimation to continue.
So no simple headless restore possible. Also it seems that the attached SSD to Odroid HC1 is not triggered when the backup-process searches for backups.
So I tried it on an Odroid XU4 I had fortunately available. There the backup was recovered from USB-stick - but the ownership of system directories were not adopted:
On the rercovered installation unbound did not start as /var/lib/unbound ownership was reset to ‘root’ but ‘unbound’, same for lighttpd in /var/lib/ and complete pi-hole logging.
Practically all ownerships and permissions in system directories were reset to defaults (root:root)! As far as I’ve read this is a known issue also rsync option ‘-p’ is set in the backup-script.
Usually I’am used to backup my former linux installations on SBCs using tar archives - but I found no way to flash the diet-pi bootloader to the SD-card by myself.
The last idea I have is to do a full install (which installs the bootloder too), delete all files and recover my DietPi installation from my tar archive. Not tested if it works till now.
Of course this is not very elegant, costs a lot of time and will not be very good for the sd-card.
If someone knows a way how to flash the DietPi bootloader I would be very thankful. Perhaps some little tool like sd-fusing.sh together with the needed files.
So I could just partition and format the sd-card, flash the bootloader and recover my backup from tar.