ServeTheHome.com

Recently I have been testing several AMD G34 and Intel 5520 series platforms. Each AMD G34 CPU requires four sticks of memory for full quad channel operation, and each Intel CPU requires at least three DIMMs for triple channel operation. With fourteen G34 sockets and dodeca core Magny cours CPUs in various stages of testing, the G34 platforms alone require a minimum of 56 DIMMs. Needless to say, recently I have found myself scrambling to find sets of matching DIMMs and purchased Amazon.com’s entire inventory of 2x 1GB ECC 1333 DIMM kits one week (over a dozen pairs.) This led me to alternative sources, which turned out to be perilous. Read the full story

Regular readers of my site know that I am a fan of the Kingston KVR1333D3E9SK2/4G 4GB (2x2GB) ECC Unbuffered DIMM kit. It works in Intel 3400 chipset motherboards that are picky about memory. Two major changes have been happening with regard to this memory. Read the full story

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

The Supermicro X8SIL-F motherboard is an excellent board for home and small business servers. When building a file server built upon Windows Home Server (V1 or V2 Vail) or another open source NAS project such as FreeNAS, Openfiler, EON ZFS storage, the Supermicro has a feature set that differentiates itself from both AMD and Intel based consumer-level motherboards. Compatibility with those operating systems and virtualization platforms such as Microsoft’s Hyper-V make the X8SIL-F a strong contender for a DIY storage or virtual machine server.

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

Since there are some requests here are the servers side by-side. The New WHS is on burn-in duty while the old WHS has had 9.5TB removed thus far. I moved the cases to somewhere that is more comfortable for me to work from in anticipation of the “final” build this week. Also placing them next to each other made it really easy to segment the two servers on a dedicated switch for doing the file transfer.

Old WHS Being dismantled on the left, new WHS doing burn-in on right, IBM power supply in middle.

Read the full story

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

Recently I received a question regarding how much memory (RAM) is supported in Windows Home Server.

The answer is fairly straightforward. Microsoft built WHS upon the Windows Server 2003 32-bit kernal. Practically speaking, this means that WHS does not have support for RAM amounts greater than 4 gigabytes (GB) thanks to Physical Address Extension (PAE). Read the full story