A quick run through of setting up Open Media Vault on an Odroid HC-1 single board computer.

Getting things ready

Items Needed:

  • Odroid HC-1 or HC-2 (although other single board computers will work)
  • Hard Drive of you choosing (I used a 2.5″ 1 TB WD blue drive)
  • A USB to SD card adapter.
  • An SD card for the operating system (I used an 8 GB Sandisk)
  • Open Media Vault image for your single board computer.
  • USB imaging program to burn the image to your SD card. (I used Etcher)

To start you’ll need to download the latest Open Media Vault image suitable for you single board computer.  These can be found here: Open Media Vault 4.X SBC Images

Also, if you don’t already have one, a program to write the image to the SD card.  As mentioned I used Etcher, but others such as Rufus, for windows should work as well.

Once you’ve downloaded both the OMV image for your specific single board computer and a means of writing it to the SD card, go ahead an burn it.  As I used Etcher I’ll go through that process.

Initial Start-up

Now that we have the image written to the SD card, time to boot up the image for the first time!  These images are based on Armbian and system will prompt for new passwords on initial login.  The initial passwords are:

Web interface:  
- username = admin
- password = openmediavault
Console/SSH:
- username = root
- password = openmediavault

     Finding our device

Once powered up and connected to your network we need to find out what IP address our router has assigned the device.  There are several ways of doing so, many routers have a GUI that will allow you to see the DHCP leases assigned on your network, but here I usually find it easiest just to use nmap on my desktop computer in a Linux terminal.  To install nmap on Ubuntu:

sudo apt install nmap

Then we just need to run the appropriate command for your network.  As my network uses the 10.0.31.0/24 ranges (many default to something like 192.168.1.0/24) the command for me looks like:

sudo nmap -sP 10.0.13.0/24

Depending on how many systems are currently on your network this output may be quite long.  The hostname that nmap picks up with vary by which single board computer you’re using, however, if you’re using an Ordoid HC-1, like me, we’ll be looking for (Wibrain) and will look similar to this:

From this, we can see that the IP address my router has assigned to the device is 10.0.13.105.

Open Media Vault Set-up

By default our image doesn’t permit root log-in over SSH (a solid choice) so we won’t be able to SSH to our device just yet.  However, the web interface is ready to go!  Simply open the browser on our desktop, enter the IP address as we found above, and we’ll be greeted with a login screen for Open Media Vault:

Using the aforementioned initial log in credentials as found above, Username = admin and Password =  openmediavault, we’ll see the configuration page for our new device:

Open Media Vault is hugely adaptable for whatever your needs may be.  From a simple NAS, to docker host, to even packages that can function as a router.  Given our rather lightweight hardware, we’ll simply set up our system to be a single user, somewhat secure system, that will provide a Samba/CIFS network share, and have a torrent client.

     Securing the new install

First we need to set a new password for the web interface.  On the left hand side there’s a column of tabs, select the “General Settings” options and at the top, in the blue bar, “Web Administrator Password.”

At this point I’d suggest logging out and back in with the new password to verify it’s working appropriately.

Next, again in the left hand column, navigate to the “User” tab, within the “Access Rights Management” section.  He we can add a new user.  

Next navigate to the “SSH” tab, within the “Services” section.  The default options here won’t allow root login (which is fine), however I’d suggest allowing it so that we can update the root password.  Here I’ve changed the default port as well to 2222 and allowed root login.  Again, save changes and apply the changes once prompted.

Next we’ll SSH into the device as root.  To do this, open up a Linux terminal (or use PuTTY if you’re on windows).  Again, the default password is “openmediavault”.  Make sure you’re using the right IP address (and port if you changed it from 22) for your device.

ssh root@10.0.13.106 -p 2222

We’ll be welcomed with a screen similar to this:

Ensure you use “openmediavault” as the (current) password and a secure new password for root that’ll you use going forward.  We can now log out of SSH, and return to the web interface, once again, changing the config to not allow root login via ssh.

At this point we have changed all the default passwords and changed the default port for SSH connections.  You can further harden the install to your own liking via /etc/ssh/sshd_config file and even install fail2ban or the link.  I won’t go into more detail on those here, but will provide a follow-up with some information on hardening your defenses.

      Setting up the hard drive

Again, using the web interface, head to the “Disks” tab under the “Storage Section.”  Here we want to ensure that Open Media Vault is seeing the attached hard drive.  It should look something like this:

Notice, there are two entries here.  “/dev/mmcblk1” and “/dev/sda”.  The first entry there pertains to our SD card, to which our operating system is installed.  The later is what we want to see.  Here it’s showing that my 1TB HDD is being seen by the system.  I chose to “Wipe” the HDD here, given that it had previously been used in a laptop.

Leave a comment

Your email address will not be published. Required fields are marked *