Upgrade problem.
I just did a dietpi-update. I am now in a “menu-loop”
Dietpi has not been fully installed…
I did go to “Install”, but there is no additional software i want to install (i went on as a pure minimal install) , i get the questions if i want to change unix password/dietpi/root password. After that it goes back to the menu (i can’t go to the shell/prompt)
What should i do?
ps: i am connected via ssh / vpn
OdroidC2
sorry, couldn’t wait.
Did a dietpi-backup -1
ps: dietpi-backup is awesome!!
pakikje
So your system is actually already installed, right?
Can you verify the expected install stage is 1: cat /DietPi/dietpi/.install_stage
And the expected .update_stage file is in place: cat /DietPi/dietpi/.update_stage
Please retry dietpi-update, if the above is correct. When it asks if you want to reboot, please cancel.
First recheck cat /DietPi/dietpi/.install_stage which should be 2 now.
If this is the case, then please reboot to sync RAMdisk to disk, load new login scripts, globals and such.
Same problem here…
katastrofa
Please go through/check the same as mentioned above.
I opened an issue on GitHub: https://github.com/Fourdee/DietPi/issues/2466
I changed /DietPi/dietpi/.update_stage to 1 and no problems now. Thanks a lot 
katastrofa
What was the files content before? Actually when updating to v6.20.5 it should be removed, it’s info merged into /DietPi/dietpi/.install_stage, which is for this set to 2.
/DietPi/dietpi/.update_stage should not be read/nor required by any DietPi script after successful update to v6.20.5, if it still is, then something went wrong.
In my case the content of the file was:
0
Hope that helps.
Hmm, and this was not fresh install right? Strange, since when you install the DietPi image and you boot it the first time, an automated dietpi-update should be done and lift /DietPi/dietpi/.update_stage to one. Patch to v6.20.5 should remove the file then, as mentioned above.
So does the file still exist now after update to v6.20.5?
In both cases, the same thing has happened to me. I have made an update and a clean installation. In both cases I ended up with a “menu-loop” when trying to update using “dietpi-update”.
And yes, the file still exists.
Something with the update must have gone wrong. If you fixed by re-setting the file, what does the login banner show about the DietPi version?
Can you please paste the content of: cat /DietPi/dietpi/.version
cat /var/tmp/dietpi/logs/dietpi-ramdisk.log
Please also read this post and follow the steps to rerun the update and check RAMdisk state before rebooting: https://github.com/Fourdee/DietPi/issues/2465#issuecomment-458582329
Of course:
cat /DietPi/dietpi/.version
#!/bin/bash
G_DIETPI_VERSION_CORE=6
G_DIETPI_VERSION_SUB=20
G_DIETPI_VERSION_RC=5
G_GITBRANCH=master
G_GITOWNER=Fourdee
cat /var/tmp/dietpi/logs/dietpi-ramdisk.log
Sun 28 Oct 14:51:12 GMT 2018 | DietPi-RAMdisk: Starting…
Sun 28 Oct 14:51:12 GMT 2018 | DietPi-RAMdisk: Completed
Tue 29 Jan 13:50:19 GMT 2019 | DietPi-RAMdisk: Stopping…
cp: failed to access ‘/boot/’: Host is down
Tue 29 Jan 13:50:20 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 13:50:19 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 13:50:19 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 13:53:13 GMT 2019 | DietPi-RAMdisk: Stopping…
cp: failed to access ‘/boot/’: Host is down
Tue 29 Jan 13:53:13 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 13:53:14 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 13:53:14 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 13:55:02 GMT 2019 | DietPi-RAMdisk: Stopping…
cp: failed to access ‘/boot/’: Host is down
Tue 29 Jan 13:55:02 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 13:55:03 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 13:55:03 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 14:44:31 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 14:44:32 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 14:44:33 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 14:44:33 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 14:45:18 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 14:45:18 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 14:45:19 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 14:45:19 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 14:47:35 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 14:47:35 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 14:47:36 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 14:47:36 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 14:49:07 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 14:49:07 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 14:49:08 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 14:49:08 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:03:34 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 15:03:34 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:03:35 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 15:03:35 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:09:46 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 15:09:47 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:09:48 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 15:09:48 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:12:57 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 15:12:57 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:12:58 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 15:12:58 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:15:44 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 15:15:44 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:15:45 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 15:15:45 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:26:51 GMT 2019 | DietPi-RAMdisk: Stopping…
Tue 29 Jan 15:26:51 GMT 2019 | DietPi-RAMdisk: Completed
Tue 29 Jan 15:26:52 GMT 2019 | DietPi-RAMdisk: Starting…
Tue 29 Jan 15:26:53 GMT 2019 | DietPi-RAMdisk: Completed
Jep ramdisk issue. It stopped after boot mount already unmounted it seems. Not sure how this can happen, will investigate.
Solution is to run update and before rebooting stop the ramdisk manually:
systemctl stop dietpi-ramdisk
Then reboot.
Thnx MichaIng, the above mentioned tip worked!