Your OMV3 is too old to expect much support. Normally there are two steps, first grow the array and then grow the filesystem. As you purchased an 8TB that was the opportunity to backup your 4TB data to it and install a fresh copy of OMV7.
Upgrade never occurred to me to upgrade. Works fine for what i do.
When I click upgrade nothing happens. Didn't/don't want to have to recreate all my users/groups/shares.
Do you still run Windows 95 or XP? Upgrade is meant to install updates. You have to run omv-release-upgrade from the command line to upgrade to the next version. But OMV 3 is so old, the upgrade is very broken. You will have to install OMV 7 fresh. guessing you won't do that but had to try. Your system is very vulnerable though.
So pretend it's OMV7, what would you do?
I don't even remember OMV 3 but Krisbee told you the steps. Resize the array in the raid section of the web interface and then resize the filesystem.
Hey, be nice, no I'm not running XP or 95.
I'm not being mean. Just pointing out in an extreme way that upgrading your NAS is just as important as upgrading your desktop OS.
If I have to run a CLI command why put a button in the GUI?
Updates are not major version upgrades. Upgrade in the GUI runs apt-get dist-upgrade from the command line. Hence why it says Upgrade on the button. In the Debian world, upgrade is an update of the current os version. release-upgrade is upgrading to the next Debian version. You can't put a button for a release-upgrade in the web interface because the system reboots and takes down the web interface.
For all I know it's working, but I don't know a way to verify. Has been running about 3 hours now.
Did the size of the array change? I don't remember if that is in the web interface. I know this is command line but take what you can get for such an old version. Post the output of:
cat /proc/mdstat
Array still says it's 4tb, although disks are recognized as 8
I, vaugely, remember doing the diskpart thing when I set it all up,
If you used partitions, that would explain why it isn't expanding. The output of cat /proc/mdstat would tell me more.
Question in my mind is what would changing to OMV7 do to
fix this situation?
Other than give you a supported version of OMV and secure/less vulnerable kernel and services? Probably not much if you never use the web interface.
Don’t have an account yet? Register yourself now and be a part of our community!
