teddyboy16

I ordered the motherboard and CPU yesterday. I decided to bump up the CPU to a Xeon E5-2620V3 2.4ghz processor $430.00. It has hyper threading and a few other goodies that the 1.9ghz Xeon does not have. Stupid CPU costs more than the motherboard! Newegg was out of memory, so I'll have to get it elsewhere. While I'm at it I might as well get a SATA III SSD because I have a 256gig SATA II SSD for the OS drive now. What I paid for my current SSD I can get one with double the capacity and faster for a little less money then what I originally paid!
 
Sigh... :-)

Well, PCI-X is still pretty darn fast, so either way, you should be fine!
 
And to make sure, I recommend the IR (RAID) firmware over the IT (passthrough/HBA) firmware. Both can do passthrough, but the IR seems to behave better. Besides, extra options are great.
 
 
As for Intel SAS Expander card, great catch! And yeah, I've only been able to find them for $200 or so. So finding one for $60 is fantastic! (if you see another, link me!)
 
 
As for the BSOD, it indicates a CLOCK_WATCHDOG_TIMEOUT bug check. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
https://msdn.microsoft.com/en-us/library/ff557211(VS.85).aspx
As for the hotfix, it may be OS specific. And hotfixes aren't usually pushed through Windows Update. They're usually option installs offered to fix specific issues.
This is the hotfix you're referring to:
https://support2.microsoft.com/default.aspx?scid=kb;EN-US;975530
And if you check lower down on the page, there are a couple of registry tweaks that you can try, and see if it works.
 
 
 
If it happens again, set the dump to us:
http://wiki.covecube.com/StableBit_DrivePool_System_Crashes

Yes it is for WHS 2011. Thanks for the link. I'll save that for future refernce. Everything is back up and running now. I was able to recreate the shares through the dash board. All the shares are where they where before WHS freaked out. I also ordered some AOC-SAT2-MV8 cards for spares. I found a great deal on them on EBay. $35 each for two new cards.
 
Well I'm happy that things are back to normal. I need to pick up some more 6TB drives over the next couple of weeks. Gotta replace one 2TB drive that has a some bad blocks and a couple other 2TB drives that Scanner says I should consider replacing. Funny thing is I've had the most problems with WD 2TB drives. The WD 1TB drives I have installed in the pool I've never had a problem with and they are older drives.
 
At least I have access to my music and movies and performance is snappy.

Yes I'm aware of the hard coded ram limit. My Gigabyte socket 775 motherboard only allows 4gb on the motherboard. I'm going to get a couple a couple of sticks of DDR2 ram to bump it up to 4gb. I'm running on a wolfdale 6300 core2 duo. its more than enough for my purposes. One of the things that held me back from upgrading was signed 64 bit drivers for my Supermicro AOC-SAT2-MV8 cards. I managed to find signed drivers. Sonnet has the drivers because they have a card that is based on the same chipset, and they loaded without a problem.
 
The server is up running and it appears stable. Drivepool is still doing its thing, but even with that going on I'm able access my ripped movies. Yes the wiki for WHS DE migration needs a little cleanup. ;-) I followed it but when I created the shares I was expecting to see the Poolpart.{xxxxxx}/serverfolder/sharedolder on each pooled drive which is what i was expecting to see. It was confusing to me, so I just moved the folders out of the DE folder into the poolpart folder on each drive. They immediately started to show up along with the shares I created. After that I moved them into the actual shares, then I deleted what was in the drivpool store folder and started the service to restart the duplication and verification processes.
 
It's all working very smoothly now, and I like the fact that I can have the backups in the pool and duplicated. WHS v1 was so finicky about its backups. :-)

I'm glad to hear that you're switching. I think you'll be very happy that you did. 
 
As for DrivePool v2.x, it lacks full dashboard integration, but it does create a tab in the dashboard from which you can administer the pool from. It's just not as integrated into the dashboard.
 
As for the Wireframes, we don't currently support that, but it's been requested in the past. We are considering it for the future though (no promises).
 
And as for removing disks, well, both DrivePool and Scanner identify the volumes mounts (drive letter or folder path), as well as the volume labels. If that's not good enough, if you have both installed, DrivePool will add the model and serial number for the disks to the tool-tips in the GUI.
 
 
 
Though, for ease of identifying disks, I would recommend mounting them to folder paths (such as "C:\DrivePool\i##" and "C:\DrivePool\e##"). 
http://wiki.covecube.com/StableBit_DrivePool_Q4822624

Hi,
 
I'm finally getting to the point that I would like to upgrade my old WHS v1 to 2011. It's getting long in the tooth and there are some add-ins that I would like to use that are not available on v1. I'll be using the same hardware only I'll be using a SSD drive for the OS that I just bought. The home server is used basically for streaming movies using mymovies, music, file and photo storage. I have already purchased a license for drivepool and scanner. I'm going to follow the wiki on migrating WHS v1 to 2011 using drivepool. After reading it, It's a pretty straight forward process. I have the necessary signed 64 bit drivers for my HBA cards.
 
I want to use v2 of drivepool because I like the features it has, but the only niggle is that it doesn't have full dashboard integration as v1 does. I'd rather use the most current version, and I'm willing to sacrifice full dashboard integration for it. Am I really losing anything else?
 
One thing that I would really like to see is a wireframe view of my hard drives in the dashboard. That's the one thing I'm going to miss about using the disk management add-in for v1. It was nice to be able to easily identify a drive for removal. Will Alex every provide such a feature in the future? I'm not sure how I'm able to identify a drive for removal. How does that work? All my bays are hot swap, so I don't have to take the server down.
 
I've been watching this software for a very long time since he first started developing it.
 
Thanks! :-)