NAS @ home
Today I start my new NAS server project.
After several evaluations I decided today to build up the NAS following the recommendations of the NAS build (Technikaffe, German). The description is clear and I like to achieve WOL in 10 sec!
- Synology DS216play will have less CPU power, no custimization effort, just space for 2 HDDs
- HP ProLine Gen8 less expensive, double energy consumption, I’ve also the customization effort, but the drawback of WOL of 1-2 min
So I order the components as described, but decided to use the ASRock N3700-ITX board. I expect to keep same energy consumpts costs as the ASRock N3150-ITX, but more CPU power (check this post out).
Well I was surpised of the size of the minitower after I used several years my Synology NAS 209. Anyway it has enough space to carry 4 HDD, so it’s worth to free some room for this small beast:)
… Put the pieces together
Compilation of the server is not described, so I post here some pictures. The compilation is pretty straight forward, all cables are marked and it’s pretty obvious where to connect them to the board.
First the empty CoolMaster 120. Enought space add the components.
First put the mainboard, of cause 🙂
Then connect the cables as per plan. Not such difficult, just study the available handbooks and it’s pretty obvious where to put the right cables.
Put the HDDs in place and connect them.I used 2x 3.5 HDDs.
… Last step to drill a bit
Now all things are in place, just to drill a 8mm hole into the plate to put the external power connector plug.
… Installing OMV
I follow the instructions until I reboot the system and removed the boot USB. I hit the issue that the server didn’t start as I expect and hang with a blinking cursor.
After some investigations I found out that the boot partition on the installation USB SLC stick miss the boot mark.
So I login the system change with help of fdisk /dev/sdX (either on the console, or a ssh connection) command ‘a’ ‘1’ and toggle bootflag. Write the partiontable and reboot the system.
… The server disappear from the network?
Then you need to fixe the Kernel due to Gigabit lan issue in Kernel 3.2. Problem appears if you transfer more then 8GB to the server in one session by SMB/Windows share. The network disappear, but the server is still running (check the console is still operatable).
That’s the Gigabit lan problem. To solve I’ve to apply the Kernal Backport fix.
- Install -> Start
- Choose Kernel 3.16 and set as default
… then you are lucky and in my case I achieve 80mb/s upload to the server 🙂
… Wakeup the server
For do some rsync backup between my NAS I added a autowakeup at 9am. See the screen below which describes all what need to be setup for this.
.. if the server suport own wakeup in Bios
rtcwake -m no -l -t $(date +%s -d '08:00 tomorrow'
.. wakeup from remote machine
Another option is to wakeup the server by sending a WOL. In my case I do it from a Synology NAS or my PC.
Here the command I use from NAS triggered by a cron job:
ether-wake -i eth0 <eth0-address>
… Finally going to production
WOL is working great and this NAS solution is up within 10sec. The effort was worth I invest.
Finally a download speed form the server
Problem Server go off, can’t be started
29.01.2016 the server is not starting anylonger. First I thought is about the NAS, but the other NAS and the network is running propper.
I go for an exchange of the power supply and will order a BeQuit 7 300W let’s see if this will solve the issue.
Edit 12.01.2016: Close project
Edit 13.01.2016: Add wakeup server for rsync
Edit 26.01.2016: Add download screen shot
Edit 29.01.2016: Server lässt sich nicht mehr einschalten