I'm doing dist-upgrade to 5.x (I think?) and I was wondering how long it takes? It's already been at it a couple of hours. I stupidly purged php because I was trying to install 7.2 and got fed up that I couldn't install it, so I purged it not knowing it would mess up the whole system. I lost access to my webgui where it said 404 not found nginx. So I figured that maybe if I did a dist-upgrade that I wouldn't need to reinstall OMV. But if it's not going to help, then I just want to cancel the upgrade because it's taking foreverrrrrrr and I'll just reinstall OMV 4 (I have an Odroid HC2/XU4).
How long for dist-upgrade?
-
- OMV 4.x
- threehappypenguins
-
-
You could try running:
apt-get install --reinstall openmediavault
But it's likely your installation is toast. Restore from backup and try again.
-
If you want to go from OMV4 to OMV5 have a look at
Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5)
-
-
You could try running:
apt-get install --reinstall openmediavault
But it's likely your installation is toast. Restore from backup and try again.
If it's likely toast, can I just halt the upgrade? Do I just press Ctrl + C (I'm using PuTTY)? Then just pop out the micro SD card, load OMV 4 and start again?
-
I got impatient and press Ctrl + C. Nothing is happening and it keeps upgrading. I'm just going to unplug it and take the SD card out and start over, hoping the rest of it isn't toast (kernel, etc). I don't have time to be waiting this long.
-
I nuked the whole thing. Unplugged my Odroid HC2, pulled out the SD card, and started over. I can now log in the GUI. All is well.
-
-
If it's likely toast, can I just halt the upgrade? Do I just press Ctrl + C (I'm using PuTTY)? Then just pop out the micro SD card, load OMV 4 and start again?
You should do things like dist-upgrades in a screen session. So anything happening to the SSH session (like hanging up or getting stalled) won't affect the ongoing upgrade and you can re-enter the screen session at any point.
My scripts ran through in around 10 minutes in a VM with 2 cores and 4 GB RAM.
JFTR: Your upgrade attempt probably hang because it was expecting some input at some point. If you don't tell apt explicitly that there is no graphical nor text frontend for debconf (export DEBIAN_FRONTEND=noninteractive) and how to deal with changed configuration files (dpkg's --force-conf* option group) you will likely being asked back by apt. And if you don't have a console at this point the whole process will stall forever.
-
My scripts ran through in around 10 minutes in a VM with 2 cores and 4 GB RAM.
SBC boards are going to very dependent on their SD card speed. These upgrades are very hard on the sd card for writes.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!