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 184.108.40.206 220.127.116.11
- 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 18.104.22.168, 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.