Beta v7.0.1

[MichaIng]

Beta v7.0.1

(2021-02-27)

Changes since v7.0.0

• DietPi-Backup | A new feature has been added which allows to automatically restore a dietpi-backup on first boot. For this set the new dietpi.txt option AUTO_SETUP_BACKUP_RESTORE=1, to get a list of found backups to select from (this does not work in combination with AUTO_SETUP_AUTOMATED=1). All attached drives are mounted temporarily and seached automatically. Set AUTO_SETUP_BACKUP_RESTORE=2 to have the first found backup restored non-interactively (this works in combination with AUTO_SETUP_AUTOMATED=1). The restore runs after the initial update, hence works with older images as well and can be done via SSH connection. Credits go to @ravenclaw900 for implementing this feature: DietPi-Backup | Add Option to Automatically Restore on First Boot #4112
• DietPi-Config | RPi: An option has been added to toggle the SPI interface. Many thanks to @incanus for resurrecting this old feature request: DietPi-Config | Add i2c/spi and other hardware options for RPi's #98 (comment)

Fixes since v7.0.0

• DietPi-Software | SABnzbd: Resolved an issue on Stretch where the install failed due to raised minimum Python version with SABnzbd v3.2.0. If Python 3.5 is installed, SABnzbd v3.1.1 will be installed now to allow keeping the install option enabled for now. Many thanks to @19eighties for reporting this issue: DietPi-Software | SABnzbd: Install latest version via GitHub master branch #2762 (comment)

[StephanStS]

I checked the changed behaviour of the dietpi-autostart (also called within dietpi-software). This works fine.
Also the change that the login selection is done after all installations is a better choice. Love that.

All other issues I have not reviewed. So no global approve is possible.

[MichaIng]

Many thanks for testing those it. The merge yesterday night was an accident when I wanted to resolve branch conflicts 😅, so that PR deserved a dedicated review.

[Joulinar]

@MichaIng
I test the backup feature. In general the system is booting after restore. However there are still some error message

sent 468,346,991 bytes  received 178,318 bytes  9,863,690.72 bytes/sec
total size is 633,813,270  speedup is 1.35
hits    command
   1    /usr/bin/mkdir
   1    /usr/bin/dpkg-query
   1    /usr/bin/rsync
   1    /usr/bin/pgrep
   2    /usr/bin/grep
   1    /usr/bin/whiptail
   1    /usr/bin/apt-get
   2    /usr/bin/rm
   3    /usr/bin/cat
[ .... ] DietPi-Backup | sed -i \|[[:blank:]]/boot[[:blank:]]|s|^[[:blank:]]*UUID=[^[:blank:]]*|UUID=DC3E-E470| /etc/fstab
[  OK  ] DietPi-Backup | sed -i \|[[:blank:]]/boot[[:blank:]]|s|^[[:blank:]]*UUID=[^[:blank:]]*|UUID=DC3E-E470| /etc/fstab
/boot/dietpi/func/dietpi-globals: line 1059: /usr/bin/rm: No such file or directory
[ .... ] DietPi-Backup | sed -i \|[[:blank:]]/boot[[:blank:]]|s|^[[:blank:]]*PARTUUID=[^[:blank:]]*|PARTUUID=e8af6eb2-01| /etc/fstab
[  OK  ] DietPi-Backup | sed -i \|[[:blank:]]/boot[[:blank:]]|s|^[[:blank:]]*PARTUUID=[^[:blank:]]*|PARTUUID=e8af6eb2-01| /etc/fstab
/boot/dietpi/func/dietpi-globals: line 1059: /usr/bin/rm: No such file or directory
[ .... ] DietPi-Backup | sed -i \|[[:blank:]]/[[:blank:]]|s|^[[:blank:]]*UUID=[^[:blank:]]*|UUID=a7adb26a-8b87-4729-99c8-9f5ac069d51e| /etc/fstab
[  OK  ] DietPi-Backup | sed -i \|[[:blank:]]/[[:blank:]]|s|^[[:blank:]]*UUID=[^[:blank:]]*|UUID=a7adb26a-8b87-4729-99c8-9f5ac069d51e| /etc/fstab
/boot/dietpi/func/dietpi-globals: line 1059: /usr/bin/rm: No such file or directory
[ .... ] DietPi-Backup | sed -i \|[[:blank:]]/[[:blank:]]|s|^[[:blank:]]*PARTUUID=[^[:blank:]]*|PARTUUID=e8af6eb2-02| /etc/fstab
[  OK  ] DietPi-Backup | sed -i \|[[:blank:]]/[[:blank:]]|s|^[[:blank:]]*PARTUUID=[^[:blank:]]*|PARTUUID=e8af6eb2-02| /etc/fstab
/boot/dietpi/func/dietpi-globals: line 1059: /usr/bin/rm: No such file or directory
[  OK  ] DietPi-Backup | sed -Ei s/(^|[[:blank:]])root=[^[:blank:]]*/\1root=PARTUUID=e8af6eb2-02/ /boot/cmdline.txt
/boot/dietpi/func/dietpi-globals: line 1059: /usr/bin/rm: No such file or directory
[  OK  ] DietPi-Backup: Restore | Completed
/boot/dietpi/func/dietpi-globals: line 140: /usr/bin/rm: No such file or directory
[FAILED] DietPi-Backup | Failed to remove scripts working directory: /tmp/DietPi-Backup
[ INFO ] DietPi-Software | The system will now reboot into the restored system

As well it seems /mnt did not contain the same folder as before. I guess this is because dietpi-backup did not save them at all. Is this something we would need to inform users on? At least I'm not able to mount my USB stick without creating the mount point inside /mnt manually

[MichaIng]

I have no idea how after hash -d the rm still cannot be found and I have no idea how to tell the system in a different/effective way to forget cached executable paths. So I think we need to live with this as a temporary issue on RPi's when older backups are restored.

The problem with /mnt/dietpi_userdata is a different known issue and I'm not sure how to handle best. When userdata have been moved to an external drive, they are excluded, when they are on the root partition, they are included. And as all other /mnt/ content is excluded anyway, the mount point directories (required to mount) are excluded as well. So it's a bit similar like with the UUIDs: If the setup does not match the backup, it does not work perfectly fine, but at least currently it can never happen that data on the system can be removed, like an actual directory with content replaced with a dietpi_userdata symlink or such.

I collected some thoughts here: #2558

[Joulinar]

ok understood. As said, the system is working fine after restore. Good to go for this release.

Next I tested SABnzbd on Stretch. Python 3.5 as well as SABnzbd 3.1.1 are installed and working.