# OpenMediaVault, Round 2: Picking a NAS for Home

One year ago, I spent my Thanksgiving setting up OpenMediaVault on a computer I had just hanging around. It has served me faithfully through the years, but several things became clear, the most important thing being that external hard drives are not designed to be continuously powered.

I had two drives fail and a growing concerns about the remaining disks. I use CrashPlan to backup the data, so I wasn’t concern with losing the data, but I was concerned with having it available when I needed it.

I also had a huge increase in storage requirements, due mostly to my video archiving project from last Christmas (which I still need to write up).

I also got married this year, and Rachel had several external drives I was hoping to consolidate. Ironically, her computer also died last week…good thing we had a back up!

The need was clear: a more robust NAS with serious storage requirements.

# Requirements

Minimum Requirements:

• Multiple user access
• Simultaneous user access
• File sharing (prefer SMB)
• Media sharing (prefer iTunes DAAP and DLNA)
• Access Control List (ACL)
• High availability (99% up time ~ 3.5 days of downtime/year) for all local users
• Remote backup (prefer CrashPlan)
• 10TB of usable space
• Minumum 100MBit/s access rate
• Minimal single points of failture (e.g. RAID 5, ZFS, or BTRFS)
• Secure system
• Minimum of five years of viable usage
• Cost effective

I performed a trade study based on four major options:

1. Upgrading internal the drives with systems
2. Continuing to use external hard drives
3. Using cloud storage
4. Using a NAS
Internal External Cloud Network
Multiple User Access 2 3 3 3
Simultaneous User Access 2 2 3 3
File Sharing 3 3 3 3
Media Sharing 2 2 1 3
Access Control List 3 2 3 3
> 99% Up Time 0 0 3 3
Remote Backup 3 3 2 3
> 10TB Usable Space 1 1 3 3
> 100MBit/s bandwidth 3 3 1 3
Minimal Single Point of Failure 3 1 2 3
Secure System 3 3 1 3
> 5 Years of Usage 3 3 3 3
Total 28 26 28 36

From this trade study, the differentiations pop-out pretty quick: Accessibility and security.

## Accessibility

Accessibility covers multiple and simultaneous user access, as well as bandwidth of data.

### Single user storage

While increasing the internal local storage is often the best option for a single user, we are in a multi-user environment and the requirement for simultaneous access requires some sort of network connection. This requirement eliminates both per-user options of increasing either the internal or external disk space. Also, the feasibility of increasing the disk space would have been impossible give that Rachel and I both use laptops.

### Cloud Storage

Storing and sharing data in the Internet has become incredibly easy thanks to the likes of DropBox, Google Drive, Microsoft Spaces, Microsoft Azure, RackSpace Cloud Storage, Amazon S3, SpiderOak, and the like. In fact, many consumer Cloud storage solutions (such as DropBox) use enterprises systems (such as Amazon S3) to store their data. Because it’s provided as a network service, simultaneous data access with multiple users is possible.

The challenge of Cloud Storage is getting access to the data, which requires a working Internet connection and sufficient bandwidth to transport the data. Current bandwidth with Comcast typically limited to no more than ~48MBits/s, which is less than 50% of the 100MBit/s requirement. While higher data rates are possible, they are cost prohibitive at this time.

### NAS

Network Attached Storage Devices are not a new thing and have been around for decades. Within the last 10 years though, their popularity in home and home office environments has become greater as the costs of implementation and maintenance have decreased. At its core a NAS is a computer with lots of internal storage that is shared with users over the home network. While more costly than simply increasing internal/external local storage, it provides significantly better access to the data.

Because the NAS is primarily accessed over the home network, the speed of access is limited to the connection speed of the NAS to the network and the network to the end system. Directly connected systems (using an ethernet cable) can reach speeds of 1000 MBit/s and 300MBit/s over wireless. This is significantly slower than directly connected drives, but faster than externally connected USB 2.0 drives and Cloud Storage. Most files would open in less than one second and all video files would be able to stream immediately with no buffering.

## System Security

Securing data is the other challenge.

### Cloud Storage

Because the data is stored by a third-party there are considerable concerns about data safety, as well as the right to data privacy from allegedly lawful (but arguably constitutionally illegal) search and seizures by government agencies.

I ran into similar issues with securing my Linode VPS, and ended up not taking any extraordinary steps because the bottom line is: without physical control of the data, the data is not secure.

The data that I’m looking to store for this project is certainly more sensitive than whatever I host on the web. There are many ways to implement asymmetric encryption to store files, but it would also require that each end-user have the decryption keys. Key management gets very complicated very quick (trust me) and also throws out any hope of streaming media.

### NAS

Since the NAS is local to the premise, physical control of data is maintained and also given the superior protection of the 4th Amendment for such items in your control.

Additionally, the system is behind several layers of security that would make remote extraction of data highly difficult and improbable.

# Designing a NAS

With a NAS selected, I had to figure out which one. But first, a short primer on the 10TB of usable space and what that means.

## Hard Drives

### Capacity

I arrived at the 10TB requirement by examining the amount of storage we were currently use and then extrapolating what we might need over the next five years, which is generally considered the useful-life period1:

While the “bathtub curve” has been widely used as a benchmark for life expectancy:

Changes in disk replacement rates during the first five years of the lifecycle were more dramatic than often assumed. While replacement rates are often expected to be in steady state in year 2-5 of operation (bottom of the “bathtub curve”), we observed a continuous increase in replacement rates, starting as early as in the second year of operation.2

Practically speaking, the data show that:

For drives less than five years old, field replacement rates were larger than what the datasheet MTTF suggested by a factor of 2-10. For five to eight year old drives, field replacement rates were a factor of 30 higher than what the datasheet MTTF suggested.3

Something to keep in mind if you’re building larger systems.

### Redundancy

Unfortunately, there is no physical 10TB drive one can buy, but a series of smaller drives can be logically arranged to appear as 10TB. However, the danger of logically arranging these drives is that typically if any single drive fails, you would lose all the data. To prevent this, a redundancy system is employed that allows at least one drive to fail, but still have access to all the data.

Using a RAID array is the de facto way to do this, and RAID 5 has been the preferred implementation because it has one of the best storage efficiencies and only “requires that all drives but one be present to operate. Upon failure of a single drive, subsequent reads can be calculated from the distributed parity such that no data is lost.”

#### Annualized Failure Rate

Failure rates of hard drives are generally given as a Mean Time Between Failures (MTBF), although Seagate has started to use Annualized Failure Rate (AFR), which is seen as a better measure.

A common MTBF for hard drives is about 1,000,000 hours, which can be converted to AFR:

$\textup{AFR}=1-e^{\left(\frac{-\textup{Annual Operating Hours}}{\textup{MTBF}}\right)}$

Assuming the drives are powered all the time, the Annual Operating Hours is 8760, which gives an AFR of 0.872%. Over five years, it can be expected that 4.36% of the drives will fail.

The AFR for the entire RAID array (not just a given disk) can be generally approximated as a Bernoulli trial.

For a RAID 5 array:
$\textup{AFR}_{RAID5} = 1-(1-r)^{n}-nr(1-r)^{n-1}$

For a RAID 6 array:
$\textup{AFR}_{RAID6} = 1-(1-r)^{n}-nr(1-r)^{n-1}-{n\choose 2}r^{2}(1-r)^{n-2}$

Using a five year failure rate of 4.36%, the data show that RAID 6 is significantly more tolerant to failure than RAID 5, which should not be a surprise: RAID 6 can lose two disks while RAID 5 can only lose one.

What was more impressive to me is how quickly RAID 5 failure rates grow (as a function of number of disks), especially when compared to RAID 6 failure rates.

Technically a Bernoulli trial requires the disk failures to be statistically independent, however there is strong evidence4 for the existence of correlations between disk replacement interarrivals; in short, once a disk fails there is actually a higher chance that another disk will fail within a short period of time. However, I believe the Bernoulli trial is still helpful to illustrate the relative failure rate differences between RAID 5 and RAID 6.

#### Bit Error Rate

Even if you ignore the data behind AFR, single disk fault tolerance is still no longer good enough due to non-recoverable read errors – the bit error rate (BER). For most drives, the BER is <1 in 1014 “which means that once every 100,000,000,000,000 bits, the disk will very politely tell you that, so sorry, but I really, truly can’t read that sector back to you.”

One hundred trillion bits is about 12 terabytes (which is roughly the capacity of the planned system), and “when a disk fails in a RAID 5 array and it has to rebuild there is a significant chance of a non-recoverable read error during the rebuild (BER / UER). As there is no longer any redundancy the RAID array cannot rebuild, this is not dependent on whether you are running Windows or Linux, hardware or software RAID 5, it is simple mathematics.”

The answer is dual disk fault tolerance, such as RAID 6, with one to guard against a whole disk failure and the other to, essentially, guard against the inevitable bit error that will occur.

#### RAID or ZFS

I originally wanted to use ZFS RAID-Z2, which is a dual disk fault tolerant file system. While it offers similar features as RAID 6, RAID 6 still needs a file system (such as ext4) put on top of it. ZFS RAID-Z2 a combined system which is important because:

From blogs.oracle.com:

“RAID-5 (and other data/parity schemes such as RAID-4, RAID-6, even-odd, and Row Diagonal Parity) never quite delivered on the RAID promise — and can’t — due to a fatal flaw known as the RAID-5 write hole. Whenever you update the data in a RAID stripe you must also update the parity, so that all disks XOR to zero — it’s that equation that allows you to reconstruct data when a disk fails. The problem is that there’s no way to update two or more disks atomically, so RAID stripes can become damaged during a crash or power outage.

RAID-Z is a data/parity scheme like RAID-5, but it uses dynamic stripe width. Every block is its own RAID-Z stripe, regardless of blocksize. This means that every RAID-Z write is a full-stripe write. This, when combined with the copy-on-write transactional semantics of ZFS, completely eliminates the RAID write hole. RAID-Z is also faster than traditional RAID because it never has to do read-modify-write.

Whoa, whoa, whoa — that’s it? Variable stripe width? Geez, that seems pretty obvious. If it’s such a good idea, why doesn’t everybody do it?

Well, the tricky bit here is RAID-Z reconstruction. Because the stripes are all different sizes, there’s no simple formula like “all the disks XOR to zero.” You have to traverse the filesystem metadata to determine the RAID-Z geometry. Note that this would be impossible if the filesystem and the RAID array were separate products, which is why there’s nothing like RAID-Z in the storage market today. You really need an integrated view of the logical and physical structure of the data to pull it off.”

However it’s not quite ready for primetime, and more importantly OpenMediaVault does not support it yet5.

So RAID 6 it is.

### Cost

RAID 6 is pretty straight forward and provides (n-2)*capacity of storage. To provide at least 10 TB, I would need five 4 TB drives (or six 3 TB drives, or seven 2 TB drives, or twelve 1 TB drives, etc).

Western Digital’s Red NAS drives are designed for 24×7 operation (versus other drives which are geared toward 8 hours of daily operation) and are widely regarded as the best drives to use for a NAS.

Their cost structure breaks out as such:

Capacity Cost/Disk Cost/GB
1 TB $70$0.0700
2 TB $99$0.0495
3 TB $135$0.0450
4 TB $180$0.0450

At first glance, it appears that there’s no cost/GB difference between the 3 TB and 4 TB drives, but using smaller sized drives is more cost-effective because the amortization of the redundant disks is spread over more total disks and thus brings the cost/GB down faster for a given storage capacity

However, the actual cost per a GB is the same (between 3TB and 4TB) for a given number of disks, you just get more usable space when using five 4 TB drivers versus five 3 TB drives.

Given that I was trying to keep things small, and some reviews indicated there are some possible manufacturing issues with the 3 TB WD Red drives, I decided to splurge a bit6 and go for the 4 TB drives.

Also, the cost per GB has, for the last 30+ years, decreased by half every 14 months. This corresponds to an order of magnitude every 5 years (i.e. if it costs $0.045/GB today, five years ago it would have cost about$0.45/GB and ten years ago it would have cost about $4.50/GB). If we wait 14 months, presumably it would cost$450 to purchase five new 4TB drives. If we wait 28 months, the cost should half again and it would presumably cost about $225 to purchase five new 4TB drives. However, since we need drives now, whatever we spend becomes a sunk cost. The difference between buying five 2TB drives or five 4TB drives now is$181. However, if we buy them in 28 months, we would have to spend close to $225…or 24% more than we would have to pay now. Since we will need the additional space sooner than 2.3 years from now, it actually makes financial sense to buy the 4TB drives now. ## The Rest of the System With the hard drives figured out, it’s time to figure out the rest of the system. There are basically two routes: build your own or buy an appliance. ### Build your own NAS My preliminary research quickly pointing to HP’s ProLiant MicroServer as an ideal candidate: it was small, reasonably powerful, a great price. Since I’ve built up computers before, I also wanted to price out what it would cost to build a system from scratch. I was able to design a pretty slick system: ### Buy an Appliance After careful review, Synology is the only company that I believe builds an appliance worth considering. Their DiskStation Manager operating system seemed solid when I tried it, there was an easy and known method to get CrashPlan working on their x86-based system, and their system stability has garnered lots of praise. Initially, I was looking at: • DS412+ • DS414 • DS1513+ • DS1813+ However, the DS41x units only hold 4 drives and that was not going to be enough to have at least 10TB of RAID6 usable storage. ### System Trade Study HP G7 HP G8 DS1513+ DS1813+ Homebuilt x86-based Yes Yes Yes Yes Yes > 2GB RAM 2GB 2GB 2GB 2GB 4GB — Max RAM 16GB 16GB 4GB 4GB 16GB > 10TB Usable Space 12 TB 12 TB 12 TB 24 TB 12 TB > 100MBit/s NIC 1GBit 1GBit 1GBit 1GBit 1GBit Cost7$415 $515$800 $1000$449

The main differences between the G7 and the G8 are:

• G8 uses an Intel Celeron G1610T Dual Core 2.3 GHz instead of the AMD Turion II Model Neo N54L 2.2GHz…no real benefit
• G8 has a second ethernet plug, however this no real benefit since our configuration would not use it
• G8 has USB 3.0, which would be nice but can be added to the G7 for $30. • G8 has only one PCI Express slot which is downgrade since the G7 version has two slots. • G8 has an updated RAID controller, however this is no real benefit since it would not be used in our configuration • G8 has the iLO Management Engine, however this no real benefit for our configuration • The G8 HP BIOS is digitally signed, “reducing accidental programming and preventing malicious efforts to corrupt system ROM.” It’s also means I cannot use a modified BIOS…which is bad. • The G8 supports SATA III, which is faster than than the G7 SATA II…but probably not a differentiator for our configuration. # Conclusion Perhaps the most important element is getting buy-in from your wife. All of this analysis is fun, but at the end of the day can I convince my wife to spend over$1000 on a data storage system that will sit in the closet – my side of the closet.

We selected the HP ProLiant MicroServer G7, which I think is a good choice.

I really wanted to build a server from scratch, but it can be a risky endeavour. I tried to pick good quality parts (those with good ratings, lots of reviews, and from vendors I know), but it can be a crapshoot.

For a first time major NAS system like this, I wanted something more reliable. I believe the HP ProLiant MicroServer G7 will be a reliable system and will meet our needs; lots of NAS enthusiasts use it, which is a big plus because it means that it works well and there are lots of people to ask questions of.

For next time (in five years or so), I want to do some more analysis of our data storage over time, which I will be able to track.

I’m also curious what the bottlenecks will be. We currently use a mix of 802.11n over 2.4 GHz and 5 GHz, but I’ve thought about putting in a GigE CAT5 cable.

RAID 6 still has has the write hole issue, and I hope it doesn’t cause an issue.

I’m not terribly thrilled with the efficiency of 3+2 (three storage disks plus two parity disks), but there’s not really a better way to slice it unless I add more disks. And it may be that more disks that are each smaller does actually make a difference.

# Resources

1. J. Yang and F.-B. Sun. A comprehensive review of hard-disk drive reliability. In Proc. of the Annual Reliability and Maintainability Symposium, 1999.

2. Bianca Schroeder and Garth A. Gibson. 2007. Disk failures in the real world: what does an MTTF of 1,000,000 hours mean to you?. In Proceedings of the 5th USENIX conference on File and Storage Technologies (FAST ’07)

3. Bianca Schroeder and Garth A. Gibson. 2007. Disk failures in the real world: what does an MTTF of 1,000,000 hours mean to you?. In Proceedings of the 5th USENIX conference on File and Storage Technologies (FAST ’07)

4. Bianca Schroeder and Garth A. Gibson. 2007. Disk failures in the real world: what does an MTTF of 1,000,000 hours mean to you?. In Proceedings of the 5th USENIX conference on File and Storage Technologies (FAST ’07)

5. NAS4Free and FreeNAS both support ZFS RAID-Z, but they run FreeBSD which does not have native support for CrashPlan

6. for the capacity, it’s an 11% increase in per GB cost

7. Not including hard drives

## 17 Replies to “OpenMediaVault, Round 2: Picking a NAS for Home”

One of the best analysis regarding NAS choosing…I’ve searched exactly like this! Well done!

2. Hi Andrew,
I want through this exersize a 8 years ago and went RAID 5 with a (unfortunately too rare) back-up to store offsite. One of the additional concerns was that this is for a smal industrial design firm and the data is worth everything to us, and loss by fire or theft also had to be accounted for.

The end of the story is that the RAID corrupted and we lost everything. The back-up that we stored off site had a lot of the data but not all, and most of the workstations had the CAD system set to store a backup on the workstation, with the main file stored on the server, and that saved us.

We threw the RAID away and figured out how to back the server up to dropbox (which was difficult, dropbox doesn’t want to that) and accepted all other limitations that solution presented. This turned out to have a lot of nice features.

My point is that data corruption across multiple drives is a downside of RAID systems that should be considered.

Brian

1. @Brian Hood:

Dropbox is certainly a reasonable approach and I have several sysadmin buddies who’ve used it with great success. One of my primary concerns was the legality of data security which, in my opinion, is significantly enhanced by keeping the data onsite. You are correct though that there are some data integrity concerns with RAID and I hope to switch to ZFS in the future to help avoid those issues in the future.

3. kristof says:

Hi from France 🙂
Excellent and complete revue, bravo and thanks for sharing.
One question about raid conf you’ve choosed : software or hardware raid 6 with an independant controller ?
Finally, did you install OMV as OS ? If yes, are you satisfied with it ?
I received my N54L yesterday but I’m waiting to be sure about my hdd config.
In complement for a Crashplan, I think to replicate my very sensitive datas on a space located to a friend’s server over a vpn. My friend will do the same thing on my Proliant …

Regards,

Kris

1. Andrew says:

Software RAID…always.

The issue with using a hardware RAID controller is that it’s a single point of failure, if the card fails your only hope of recovery is to find the exact same type of card.

Yes, hardware RAID is a bit faster, but the extra speed is not a deal breaker for me and not worth the extra risk.

I did install OMV as the OS, and I am very satisfied with it. It’s build on Debian, which I also use on my VPS.

4. Question about your comment about ZFS. Why don’t you think it’s ready for primetime? I’m not asking because I disagree…I’m trying to build a large NAS for a friend and I’m trying to decide on OMV or FreeNAS. I really like OMV in terms of stability but research had indicated that ZFS was superior to RAID6, so that’s where I’m getting my OMV or FreeNAS issue.

Any thoughts would be appreciated.

Thanks!

1. Also any thoughts about SnapRAID?

1. Andrew says:

Not really…I let CrashPlan handle at the backups and versioning.

2. Andrew says:

Good question:

Yes, while ZFS is technically better, RAID 6 still met the requirements I had and was cheaper and easier to implement.

ZFS had its first stable release in May 2013 and one of my goals for this system was to minimize the amount of sysadmin work I would have to do.

FreeBSD does not easily support CrashPlan, which is the off-site backup service I use. Since FreeNAS is based on FreeBSD, that drove me to use OMV (Debian does support CrashPlan). Unfortunately, while Debian did support ZFS, OMV did not support ZFS (although I believe the pending 0.6 release will).

I did play around a bit with trying to get CrashPlan to work with FreeBSD and to integrate ZFS with OMV, but it ended up being too “hacky” and ultimately was not inline with wanting to minimize future sysadmin work.

Had a stable release of ZFS been around a year earlier, OMV would have probably had better support, either officially or through a plugin.

Thus, even though a stable release was available at the time I built my NAS, it was still a bit too much on the bleeding edge for the all the other components I was also trying to integrate.

I would also add the ZFS takes a lot of memory. FreeNAS says, “FreeNAS® with ZFS requires a minimum of 8 GB of RAM in order to provide good stability regardless of the number of users or size of the pool… For systems with large disk capacity (greater than 8 TB), a general rule of thumb is 1 GB of RAM for every 1 TB of storage.” (http://doc.freenas.org/index.php/Hardware_Recommendations)

So, minimum of 8GB and I would need at least 12 GB. The N54L officially only supports 8GB, but many have used 16GB successfully…but that still runs \$200 or so, which would have increased the budget by 50%.

1. Stephan says:

Hi

Again as many other have stated this is a very solid review of pro’s and con’s and risk assessment.

I am in a similar situation. I have Qnap NAS (SS.439) which will eventually run out of space and it wants to be be fed with expensive 2,5″ drive which do not hold enough data in the long run. It has served me nicely with no errors in almost 6 years including 3 rebuilds (online RAID extension) – pretty good I think.

So in other words I need a new NAS :-).

I do considers FreeNAS and RAIDz but I am still not sure…..

As for the RAID problems mentioned above:

1) The write hole can be “solved” with an USV
2) “good” hardware RAID controllers can, if the fail, bew replaced by new one from the same company – the high end companys are always downward compatible – so no need / fear to buy the exact same card

1. Andrew says:

Stephan:

The English equivalent of USV (“unterbrechungsfreie Stromversorgung” is UPS (“Uninterruptible Power Supply”), and yes, that is a pretty easy way to solve the write hole issue.

The issue I have with hardware RAID controllers is that if the company goes out of business or stops offering the exact same model, then what? I think it’s easier to just use software RAID, especially since software RAID still met my requirements.

5. Darryl says:

Andrew, were you able to implement RAID 6 with the HP G7? In your analysis you indicated you would need five 4 TB drives to achieve 10+ TB of space, but it looks to me like the HP G7 (and G8) only has 4 drive bays.

1. Darryl says:

I wondered if you had modified the internal 4 bay cage to hold 2.5″ drives, but your solution is better — allows the use of cheaper 3.5″ drives for data and provides room for a boot device. Nice. Lots to think about here. Thanks for the excellent write up.