Okay, after running an apt upgrade -y the system suggested I run ovm-confdbadm populate, and then after logging out and in again, the admin user is an administrator again.
I'm building a new NAS on my old NUC and it's installed from ISO okay, I can login using the root password no problem, but when I log in with the admin account in the GUI it's not set up as an administrator, but as a basic user and so I can't configure OMV with the GUI. What can I do on the ssh or console side to fix this?
No you don't.
I'm not sure why you don't like systemd-resolved but that is what OMV uses.
It's not that I don't like it, it didn't work for me. I've realised it was my own fault! Tired eyes and not restarting the router after changing the DNS broadcast over DHCP can be a problem.
I'm still not sure why it booted okay on Armbian, but then lost the network after OMV installed and it was rebooted, but setting up static IP made it work for me.
Yes, the install script removes network manager but it replaces it with netplan (systemd-networkd). And systemd-resolved works just fine. I'm not sure why your system is having a problem with it unless your dhcp server isn't supplying a dns server. DNS isn't required to get the web interface working.
So, a lot of your steps shouldn't be necessary (yes, I installed on armbian with the script A LOT). Switching from network-manager to netplan/networkd does make most routers give out a different IP address but that isn't that hard to deal with.
I think I've figured out why DNS didn't work, I set the router to send the Pi Hole IP address as the DNS server, it was odd that for both NetworkManager and netplan didn't set a resolv.conf though.
You need to make sure you set up the /etc/network/interfaces for the network card to static before you install OVM5, or it loses the network card and never comes back. It took me a few goes at reflashing before I realised what was going on.
You also need to delete and replace the /etc/resolv.conf before and after you install, the first time for getting the installer, then when the installer removes NetworkManager, systemd-resolverd takes over, so you have to delete the symlink and recreate the /etc/resolv.conf file.
I have an Odroid HC2 that I needed to upgrade to OMV5, but the upgrader broke Docker so here are the steps I went through to clean install:
- Download Buster_Legacy from https://dl.armbian.com/odroidxu4/Buster_legacy
- Use the guide here to page 13: https://github.com/OpenMediaVa…lling_OMV5_on_Armbian.pdf
- Type ip addr and see what is the network card name for your Odroid, you will need this next. For example eth0
- run armbian-config and go into Network and Advanced and add the following, changing the IP range to your network range:
- auto eth0
- iface eth0 inet static
- address 192.168.0.10
- netmask 255.255.255.0
- network 192.168.0.0
- broadcast 192.168.0.255
- gateway 192.168.0.1
- dns-nameservers 18.104.22.168 22.214.171.124
- dns-domain mydomain
- dns-search mydomain
- Hit Tab and choose Save, then Back.
- Now go to Personal and set up your Time Zone, locale, keyboard and hostname, etc.
- Finally go to System, Firmware to update the firmware, then System DTB and change to Odroid HC1/HC2. Your machine will reboot.
- You should now be able to login to 192.168.0.10 on your network. Type systemctl stop NetworkManager and apt purge NetworkManager.
- Create a /root/resolv.conf with a single line of nameserver 126.96.36.199, delete the /etc/resolv.conf then cp /root/resolv.conf /etc to replace it.
- Now your Odroid will be able to resolve properly, proceed to the installation of OMV5 (page 14)
- Before you reboot, remove the /etc/resolv.conf and copy it from /root to ensure you have DNS set up when your machine comes back. Then reboot.
- You can now log into your web interface on 192.168.0.10
Once you have added your drive, shared it and added users to share with Samba, go to the terminal and type smbpasswd -a username for each user you have added, this will create the Samba users that Windows 10 needs to share, for without this step, you will be going round in circles wondering what to do, like I did.
Since the Odroid HC1 and HC2 are headless, and the OMV5 installer removes NetworkManager and dhcpd, the interface won't come back after a reboot unless you set it static. Once NetworkManager is no longer controlling the DNS, systemd-resolverd takes over and makes an even more of a hatchet job of DNS, so you need to delete the resolv.conf and replace it to break the symlink to systemd-resolverd or it will simply replace it whenever it feels like it and nothing will install or update.
I was using the OpenmediaVault login and suddenly it had stopped working telling me my username and password were wrong.
I had set everything up, and I've been transferring files to the drive but it wouldn't let me in.
I SSH'd in and noticed a full /var/log with nothing visibly in it.
I fired up a lsof |grep /var/log and there were a list of files marked as deleted that something had deleted but not disconnected the inodes, so a quick /etc/init.d/rsyslog restart cured the issue.
So if anyone cannot log into the web gui in the future, check the /var/log and if its 100%, restart rsyslog and see if that fixes the problem.
Once the rsyslog had restarted, login was fine.