Thanks for your report.
The setup is done on the regular boot partition, whether to start into first run setup or not is decided based on a flag file:
/DietPi/dietpi/.install_stage (RAMdisk) and on offline image it's on the first partition in
/dietpi/.install_stage.
There seems to be an issue that when having the first run setup done, the flag file is not correctly set or does not survive reboot. We had an issue where this was possible due to a RAMdisk service change, but that was actually solved with v6.20.6.
Just to be sure, your loop happened just today, so DietPi was updating to v6.20.6, right?
At least, that you end up in
dietpi-software means that the
.install_stage file already was successfully set to
1 after first run update (to v6.20.6).
In the following code snipped, the value should be set to
2 after having first run setup done before rebooting:
https://github.com/Fourdee/DietPi/blob/ ... 898-L14900
The next login should not open
dietpi-software anymore then.
Please try the following, when
dietpi-software prompts:
- Exit it (ignore some warning that first run setup should be done or such)
- Run:
dietpi-software list
- Check the software ID/index of the one (or ones) that you want to install
- Then run e.g.:
dietpi-software install 83 114, changing the numbers according to the software IDs you want to install (those two are Apache webserver and Nextcloud).
This disables the automated reboot after the setup is done.
When this has finished, can you please paste the following output:
Code: Select all
cat /etc/systemd/system/dietpi-ramdisk
cat /DietPi/dietpi/.install_stage
cat /DietPi/dietpi/.update_stage
If you want to reboot, to be failsafe, run first:
Code: Select all
dietpi-services stop
systemctl restart dietpi-ramdisk
cat /boot/dietpi/.install_stage # Verify that is is really 2 now...
reboot
