Helios 4 NAS
This past week (actually past two weeks) I worked on building a compact NAS storage system using the Helios 4 kit I had received a few weeks ago. The expected end result is a 4-drive RAID5 storage available to Windows, Linux and Mac backup clients via native file transfer protocols.
Helios 4 looks pretty great: it’s a system-on-the-chip with 4 SATA ports and a gigabit network interface, supplied with additional hardware functionality for speeding up RAID operations.
I got my Helios 4 as part of the 3rd wave on the campaign, it seems to be available for pre-order now.
The kit arrives as a batch of parts that are practically ready to be assembled:
Helios 4 box
Helios 4 motherboard
Let’s peel the packaging paper off:
Helios 4 case
… now attach the disks:
Disks in Helios 4
Helios 4 - NAS disks
… install motherboard:
Installing motherboard for Helios 4
… and add the fans:
Helios 4 fans
And that’s it! We have a brand new shiny network storage, ready for software install and configuration:
Helios 4 fully assembled
You can download the latest Armbian version here: Kobol.io – Helios 4 images.
Let’s burn the IMG of Armbian onto a microSD card:
Cool! Now we just put this into the Helios 4 system and power it on. Now would also be the time to connect the USB to microUSB cable into my XPS Laptop and use the picocom to connect over it to the Helios 4 console (I had to apt install picocom). Since I use the Dell XPS 13 2019 model, there are no USB ports – only USB-C. So in my case the console connection is: USB-C adapter -> USB cable -> micro-USB connector plugged into Helios 4.
this will eventually show the fully booted OS and progress with Helios 4 setup:
Helios 4 first boot
I have configured my account greys and then progresses with post configuration.
When you boot, you get a fully working Debian Stretch based system, ready for post-configuration.
Once you login, it’s probably best to set the static IP address and then continue setup using SSH connection instead of USB serial.
As root, edit the /etc/network/interfaces file and add eth0 settings similar to these:
IMPORTANT: don’t forget to replace 192.168.1.XXX with a correct IP address in your network, like 192.168.1.123. Same goes for the gateway IP address.
Once changes are made, reboot using shutdown -r now and reconnect using ssh.
Run the armbian-config command as root and select Software
… then select Softy:
Installing Softy in Armbian
… and then select OMV:
that’s it: we can now open the IP address in our browser and login using default admin user (username: admin, password: openmediavault):
This is admin/openmediavault initially, so change the password as soon as you can using General Settings and Web Administrator Password section:
Changing password in Open Media Vault
VERY IMPORTANT: one rather annoying feature of OpenMediaVault is that you have to apply all of your changes. You can create new users or configure shares or even build RAID arrays, but that’s all happening in the OMV interface. You have to click the Apply in the yellow status prompt at the top part of your browser window with OMV to actually commit changes and restart relevant services. The reason this is annoying is because this yellow prompt doesn’t show up immediately, so when you move to a different section of OpenMediaVault administration you may forget about it and not apply changes until much later.
Here’s an example of this thing:
Helios 4 - OpenMediaVault
From the main menu of the OMV, I created a RAID5 array using the 4 disks I have available.
I contemplated getting a 2-disk parity setup, but decided against it because this NAS server is a secondary storage device in my home office – I have a Synology system running 2-disk parity with larger disks.
The plan for Helios 4 system is therefore to be about 8.5TB of NAS storage for immediate backups and temporary projects. Critical data will be backed up to the Synology NAS system in parallel (definitely NOT from Helios 4 to Synology, but directly from backup clients).
Check which disks you have:
OpenMediaVault NAS disks
Now erase (wipe) each one of them: Erasing disks in OpenMediaVault
Here’s how RAID5 is created:
Creating RAID5 in OpenMediaVault
And here you can see how it looks from the command line:
The performance is pretty impressive: initial RAID5 re-sync is happening with the average speed of 80MB/sec (default non-prioritised sync on my 2-disk parity Synology system was around 20MB/sec last time I checked):
Even before this re-syncing completes, you can create filesystem on the RAID5 array that was just created:
Creating filesystems in Helios 4
Creating BTRFS filesystem in OpenMediaVault
Once filesystem is created, it’s possible to progress to shared folders and network shares setup.
After wasting quite a few days trying to access basic network shares using my primary user on the new NAS system, I realised that it was a mistake: that user was for administrative purposes, and not a member of the users group. Turns out, I either need to add users group membership for greys or create another user specifically for network share access.
After brief consideration I decided to go with a separate user called nas: passwords have to be in clear text form in some of my automation scripts, and so it makes sense to use specific user instead of risking password of an admin user to be leaked.
Add shared folder:
Sharing a folder in OpenMediaVault
Now you need to enable sharing service, select the ones you need from the menu and tick Enable option like this:
Enabling sharing in OpenMediaVault
You can always select the Dashboard in the menu to see which services are enabled:
Dashboard in OpenMediaVault
For every shared folder you create, be sure to set the privileges:
Shared folder privileges
So far I only accessed storage from Windows and MacOS.
Here are the commands I used for mounting APF (Apple Filing Protocol) share and CIFS (Windows/Samba) share – they both point to the same folder on the Helios 4 storage, actually.
First, create mountpoints:
Now, let’s try Windows share access:
And now, MacOS style via AFP:
Note: I replaced the last octet in the helios4 IP with XXX and also swapped my real nas user password with the SECRETPASSWORD word – these need to be set to the real values of your NAS storage and user if you want to try the same setup.
Things achieved with this project or scheduled for the nearest future:
That’s it for now! I’m glad I completed this project at last – Helios 4 seems like a fun system to use and a great option for exploring ways of configuring and presenting NAS storage using latest software solutions available.