Fanless Mini ITX Atom based build

    • Bitfenix Phenom Mini ITX Case
    • Asrock Q2900-itx – Atom based J2900 (Pentium) Quad Core CPU Fanless
    • 8GB G.Skill DDR3 1600 1.35V RAM
    • 2 X Seagate NAS 4TB 3.5” Drives Raid 1.
    • 1 X Fujitsu 60GB 2.5” OMV System drive
    • 1 X Samsung 960GB 2.5” Deluge/Torrent drive.
    • PicoPSU 120w
    • 90w Power supply (fanless laptop style brick)
    • Openmediavault 1.8 Kralizec.

    Hi all, my first NAS build here. I started with a Raspberry Pi two years ago as lower power 24/7 seedbox and network attached file store. In that time it served faithfully and enabled me to learn a bit about Debian. Increasingly I became frustrated with the slow transfer speeds from the Pi so I began looking into an off the shelf NAS, possibly QNAP or Synology.


    I planned to run Plex on my new NAS and prices rise quickly when wanting something with a decently capable CPU. I’ve built plenty of system in the past so I thought I’d turn my attention to a custom NAS build.


    Number one consideration for me was low power usage and a virtually noiseless system.


    The Intel Atom based J2900 (Pentium branded) CPU stood out for me for having a passmark score over 2000 for Plex transcoding and a TDP of only 10 watt.Asrock manufacture a nice J2900 mobo with a fanless heat sink, so that was the obvious choice coupled with low voltage RAM.


    I did a fair bit of research on the various OS options available including FreeNAS, Amahi and Ubuntu Server, but OMV stood out as clear favourite being Debian based (in my comfort zone) and support of both Deluge and Plex.


    I liked the look of Bitfenix Phenom case in white, and it has plenty of drive bays for future expansion. As I wanted to run system without any fans inside the case, I searched for an external power supply, a web search turned up the PicoPSU, perfect for a low power build.


    Drive wise I opted for the Seagate NAS drives due to their slightly higher RPM than WD Red, and also they were significantly cheaper. I opted to mirror the drives for redundancy, backup of important data is made to an external drive I keep at work. In future when I need more space I’ll add more drives and move to Raid 5.


    To allow for maximum spindown time of the 3.5” drives I opted to add a separate 2.5” drive for Deluge purposes. The mirrored 3.5” drives store all my media as accessed by Plex.I played with booting OMV from USB stick but decided to use an optical drive I had laying around from an old laptop as I could not find a USB stick with the write balancing feature that is recommended.


    In the case I have spread the drives out as much as possible, its summer in Australia here, and so far drive temps do not exceed 46C on a hot day, they sit at 36C overnight.


    Power consumption at idle is 32W, on boot and under load maximum is 65W.


    Download speeds in Deluge is crazy as compared to the Pi, and Plex works brilliantly, I had two 1080p stream going last night and there was no stuttering which really surprised me.All in all very happy with the build.


    I had no issues with NUC drivers as I see others have had with Asrock Mobo’s in fact the whole thing just worked right out of the box with OMV.


    Any feedback would be appreciated, I’m new to the custom NAS scene so any constructive criticism would be appreciated.


    One question I have, I’m currently running SAMBA/CIFS for windows shares, is there any advantage to changing to NTFS?



    Some pictures I took earlier today when I took it outside to blow out glitter a Christmas ornament had dropped in it,


    Look away if you're into cable management:



    Back view, custom cardboard power supply ;)


  • OK, doing some reading here regarding Raid1, I came across KM0201's comments regarding returning to JBOD and ditching raid1 in favor of using a Rsync job to sync the drives every so often. Makes perfect sense to me, data is still redundant whilst having the advantage of recovery from accidental deletes and reducing usage of one of the drives.


    What's the best method to ditch raid now my drives are established? Will I need to backup and reload my data on to each drive?

  • If you remove the RAID 1 mirror, you no longer have live redundancy. The RAID 1 provides you with the ability to lose a data drive without skipping a beat. Breaking off the drives into their own separate independent instances and rsyncing the data does indeed provide more of a 'backup' scenario than the drives would provide you in a RAID 1, but like I said, it's not something that I would consider to be "redundant" since if you lose drive A, you're down. Sure, you have your data on drive B (that's what matters, right?) but I just wanted to clarify that point.


    RAID is not a backup, however independent drives are not necessarily "redundant".


    I run RAID 1 in my server and swear by it as my server does quite a lot. I stream a lot of shows to my HTPC from it and a multitude of other services. OwnCloud in a VM, video surveillance, etc. I have a secondary server that kicks on at 3 AM every night (wake on LAN) and has all of my data rsync'd to it, then shuts down until 3 AM the following morning. Likewise, I utilize the USBbackup plugin on a bi-weekly basis (love that darn plugin) and store my external drive in my office at work.


    I don't want to "scare" you into building beyond your existing setup, which is admittedly quite a nice setup, but the point behind the above paragraph where I shared more of my setup is because I was hesitant to have all of my eggs in one basket. Sure, having split drives with rsync jobs does provide a sense of a backup, but if my rig gets hit by a surge and the board shocks the drives, I very well may still lose everything then since the drives are in the same box. Far from a guarantee, but ya know... That's why I value something like USBbackup and an external hard drive as an irreplaceable insurance policy, as it puts my data in another location altogether. ;)


    So what I would do is weigh your options. Do you want the ability to lose a drive and still run without skipping a beat? Or do you want more of a backup related scenario? Independent drives with rsync jobs is a very, very smart move, but just understand that it really needs to come down to your specific priorities that will dictate a RAID setup or an rsync job setup with split drives. If you care about your data far more than the server staying up and running, rsync makes perfect sense. If you *do* want redundancy and have some sort of external hard drive for syncing your data to a 2nd location, OR if you're as crazy as I am with a second backup server, then suddenly running RAID doesn't seem like such a bad thing after all.


    I have never tore down a RAID setup, but it's my understanding that the drives need to be removed from the array and formatted in order to work in an independent fashion again. Otherwise they will continue to operate thinking they are in a RAID array. I'm sure somebody else here can clarify this point since I'm far from 100% certain.

  • Thanks for the response and input. Yes fair call, it would be somewhat foolish to lose the redundancy afforded by raid 1, and my original intention has been to to use it since from the beginning.


    At this point I'm thinking my retired Pi would make a fine backup up server connected to a spare 4GB external drive I have hanging around. I'll setup it up with a Wemo switch to come on at a particular time of night several times a week and use Rsync to backup. And continue to use another external drive with USBbackup to periodically to backup critical data such as documents, pics, home movies etc and keep offsite. Or look into spending a bit on getting a decent amount of cloud storage for the same purpose.


    Incidentally it hit 44 degrees C where I live yesterday and with no one home and no air con on my house temps were not far below the ambient temps. I have a critical drive temp warning set at 50C and this was not reached so I'm feeling ok at this point with continuing with a fan free system.

  • That sounds like a good idea to me. There's pros and cons to each scenario, but if you really dive through what your priorities are, in the end it'll be a pretty clear answer.


    Only thing to keep in mind about the R-Pi is the ethernet and USB being wired to the same bus, so rsync speeds may seem a bit sluggish. That being said, given that the R-Pi eats all but 5 watts, it's hard to argue with that. I used a R-Pi with a 500 GB USB drive plugged in in the exact same manner you described. It worked extremely well.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!