ServeTheHome.com

The Big WHS was originally supposed to house approximately 30TB of storage when the plans were first detailed on an Excel spreadsheet BOM in December 2009. This was a big upgrade to my first DIY Windows Home Server box that had well under 20TB. About five months later, the storage capacity has crested 60TB, with further room to expand. The Big WHS now spans two 4U Norco cases (using a total of 8U of rackspace and another 4U chassis is in the works) has over 60TB of storage, and requires well over a dozen ports on the gigabit switch.

Read the full story

Things have been progressing on the Big WHS front. First off, my main PC is now is using the WHS Connector software and has back-ups scheduled on the new WHS. The old WHS is still assembled, but it is not powered on at this point, just in case something goes wrong with the current setup. I also decided to play around with some other popular NAS/SAN solutions while I was at it.

Here’s a quick screen shot of the Windows Server 2008 R2 hosting Hyper-V virtual machines with Windows Home Server, OpenFiler, and FreeNAS:

Windows Server 2008 R2 with WHS, FreeNAS, and Openfiler in Virtual Machines

Read the full story

This week the Big WHS underwent a major change and dropped the Asus motherboard in favor of a Supermicro one. Apparently the Asus P6T7 WS Supercomputer motherboard does not like the HP SAS Expander at all. I could not find a card that could see the SAS Expander. This all culminated when I finally took the working setup out of the Gigabyte H55 board and couldn’t get it to work in the Asus. For those wondering, yes, it was a $200 motherboard/ CPU with 36 raid ports + another 5 onboard and 1 esata. Windows Home Server v1 can only support 32 drives so that is a lot of connectivity at about $660!

Read the full story

Just as a quick update to those who are following this build. Some adjustments have been made ove the past week.

First, I finally decided that 32 ports from two Adaptec 31605′s would first off be slightly less than I had wanted. I realized that while the initial build would hold 19-20 1.5TB drives, 6x 2TB drives, and 4x 1TB drives, odds are that I would want to add another 6-7 2TB drives in the next six months if for no other reason just to spread the storage a bit more.

Read the full story

Just as an update. I installed the second Adaptec 31605 today, filling all 16 ports with 8x WD Greens, 6x Hitachi 2TB, and 2x Hitachi 1TB drives. There is an additional 1.5TB Seagate 7200.11 being used as an OS drive. That’s 27.5TiB raw capacity.

Here’s a view of all the drives currently in The Big WHS. Note, I may have killed yet another WD Green. A single SMART error so I’m making quadruple sure that something isn’t wrong.

17 Drives, 27.5TiB Raw installed for testing

Read the full story

Continuing to test the new WHS box, I was treated to yet another new Western Digital Green failure this week. Ridiculous!

This was the second (of 8 new) WD greens to fail in its first week.

Read the full story

At around 1:30AM I woke up to what I believed was the fire alarm. After about 30 seconds outside in the cold, I realized that it was not a fire alarm, but rather an Adaptec controller alarm. The first hard drive has failed.

Read the full story

After work today I got the server up and running doing a build/ verify Raid 6 array on the 8x new Western Digital Green 1.5TB drives. Since the current WHS is still in use, I used some spare hardware in the place of the legacy hardware including a 850w Coolermaster PSU, EVGA 8800 GTS 512MB, and an Adaptec 5805.

Something I should have known to do, but forgot to check, is that VMWare ESXi does not work with the Realtek onboard NICs of the Asus P6T7 Supercomputer, and apparently there is a further chipset conflict. Since I was between going Hyper-V and ESXi as a hypervisor, VMWare’s incompatibility made the decision easy.

Tomorrow after work (which sadly has been consuming 12+ hours a day lately) I will probably pick up Windows Server 2008 R2 as a Hyper-V platform. I like the idea of running WHS from the free Hyper-V server, however, since the goal of this box would be to run VM’s for other servers anyway, I’ll probably just go the Microsoft route.

First off, this is not a typical WHS build, and it was not meant to be. For the majority of users, a HP MediaSmart (by far the WHS to get if you do not DIY the build) is the way to go. For my purposes, I have seen a consistent, but increasing 500-600GB/mo of extra disk usage. Just for the record, unlike the opinion of certain Seagate executives, it is not for material of questionable moral value. Alas, I needed a solution that would allow me to have one box that could be upgraded and used for up to 24 months. As mentioned in Part 1, this project is an upgrade project and therefore I had some parts, and had a good idea of what I was doing before embarking on the project.

Read the full story

About 10 months ago I decided to enter the world of the Windows Home Server. My storage arrays had outstripped my Cosmos S’s capacity, and running multiple controllers for all of the SAS drives as well as SATA storage became too much. My decision to build a WHS v. buy one was made due to sub-$100 Seagate 1.5TB 7200.11 drives (at the time very inexpensive) so I bought another eight drives just to fill up an 8 port raid controller.

Read the full story