Watching this thread... I've been happy with WHS v 1, and have been running a Minecfraft server on it for my sons. However they recently wanted to run a special modded version of the server that requires 3GB if RAM, and the 32-built OS just couldn't handle it. I was thinking about using Windows 8, but I would prefer WHS. I have 2 2TB drives, following by a hodge- podge of drives of various sizes (including several laptop drives) that adds another 2+ GB. I really like being able to randomly add and remove drives, and at least 10 drives have been in-and-out of the system since I first built it. I'm cheap, so I upgrade the drives whenver I get a new one for free. Sounds like stable-bit Drivepool is a good way to go. I'm not sure want to pay the big buck for Server 2012.
Nor do I . . .
I'm not out of the woods yet on this, only for the uncertainties. I must explain. I'm even tempted to start another thread, and it dovetails with the "Memory and Storage" forum.
First, maybe it was Binky -- yes it was -- who mentioned drive-letter assignment for new drives to be added to the storage pool. I took the chance of omitting a drive letter assignment to the first 1TB drive I added, and it seems to work fine: The remainder of the boot drive was "D :" and had that assignment, but the 1TB drive has no drive letter. They both contribute to the storage pool, which thus far is about 1.14TB.
Second. Here's where I think I'm in the woods, so to speak. When I ordered these WD Blue 1TB drives ("EZEX"), I had been specifically looking for disks that wouldn't raise any hardware issues on this old-tech Striker Extreme motherboard and its nVidia nForce controller. I quickly discovered that the drive manufacturers were throwing a curve-ball at us with "Advanced Format." This means that the sector-size of drives will no longer be 512 bytes, but 4,096. And it requires that the OS can deal with it in either of two ways: either with "512E" emulation, or simple accommodation of the 4K-byte sectors. Otherwise, with older OS'es and specifically WHS v.1, these drives will slow down and eventually begin experiencing corruption.
NewEgg should have noted that the WD Blues were AF drives, and you would have expected it to show in the "Overview" and "Details" tab. But it was nowhere to be found, and I assumed they were not AF drives when I ordered them.
There are fixes you can find in various blogs and forum posts for the older software (specifically OS software), and I read where you can actually disable the AF feature with a jumper, but couldn't find the documentation pertaining to the jumper and its pins.
In any case, WHS 2011 (Server 2008 R2 and Windows 7) are capable of handling these drives. Even so, when I hooked up one of the Blues to the system, opened Server Manager and Storage Management to create a Basic partition and Simple volume, one is given the choice with a drop-down list between "Default," 512, . . .. 4096 . . . etc. and I assumed that this was the sector size. So I picked 4096.
So now that the remainder of the system boot disk and the new 1TB Blue drive are in the storage pool, I need to put the original folders (on the boot-drive's DATA volume) into the pool so they are duplicated.
I just really feel edgy about these AF drives, or whether I prepared them properly. And also, the Striker's BIOS doesn't offer "AHCI" versus "RAID" for the SATA disks. Only "non-RAID" or "RAID" settings. I have a newer BIOS on order -- custom-flashed to PLCC chips that I can just exchange in the mobo to avoid the risk of a flash failure -- something that the Striker had shown when I first started using it 5 years ago.
Third -- as I put it in another new thread posted today -- It seems a bit puzzling that I'd have two "connector" software programs on my main workstation: One for the WHS v.1 server (which is still "up"), and another for this WHS 2011 -- which I'm trying to configure. So far, I shared a server "Software" folder to my workstation account, and the connectivity is there. But I'm still accessing the server by switching to it from my KVM switch.