By the grace of God, there is one and only one reason I'm logging on to Anandtech this afternoon.
First -- about my own server box, which is also mentioned in a couple other threads on this forum.
I wanted to completely kill the nFarce controller configuration I had on it. NOT -- because the controller or the drives were causing problems; ONLY because the DRIVERS for nFarce were interfering with other things and causing core 0 of the CPU to show 80% usage while the other cores were tripping along at below 3%. I had enough info from Win 7 and WHS users about old NVidia hardware to KNOW!! -- yes KNOW what was wrong there, even if the knowledge might seem "inconclusive." I could just let the server trip along with the newly-installed C2Q Q6600 I stuck in the motherboard the other day -- hoping at that time to find out if there was a hardware failure causing this to happen. there wasn't. It's a DRIVER problem.
And like I said, I could just let this server keep on trippin' and truckin'. To resolve the problem before throwing out the old hardware entirely, I found another intersection in my web queries. People who wanted to do the same thing -- get rid of the nFarce. And the solution was one which I had proposed here or in the storage forum also in recent days: a PCI-E SATA-III disk controller which offered "port-multiplier," default AHCI, RAID 0, 1, 1+0 and 0+1. The skinny on the street said it worked GREAT with win 7 and WHS. Linux and Ubuntu users were unhappy with it. But the Intel community thread touting the same Marvell chip was pretty darn clear.
Then there's StableBit. I've discovered that I can move these four data disks from here to there and back again, and even with a fresh install of WHS 2011, once Stablebit is added to the software mix, it simply goes out and finds those disks, organizes the pool array, and -- good to go. Doesn't matter if the drive labels are different, either. It just does it -- with complete reliability.
So. Here I am, waiting one more day before the little Startech [Marvell] controller arrives, getting all ready with backups of backups, and backups on top of 'em. I'm wondering about configuring the two Seagate NAS 2TB drives I bought. I'm researching MBR and GPT to refresh myself. I'm reviewing the "AF" disk issue.
And suddenly, my aging brain forgets that I had resolve this "AF" issue back in 2012 with an e-mail to Western Digital. I was worried that my boot disk on my flagship workstation wasn't "properly aligned." I found a test program somebody recommended.
I was in a hurry. I have an ISRT setup on that machine. And I ALWAYS fiddled with the ISRT config with some care, but never had a problem. I'd enable and disable the HDD acceleration with nary a problem. Perhaps, though, I always re-initialized the SSD for further use as the cache disk. Instead == I was in a hurry -- I rebooted the system. Suddenly, my flagship workstation cannot boot!
Tried the usual, which had worked before from another mishap of not turning the system off when I cloned the disk with the same drive signature: boot from the Windows Install CD, select repair. Didn't work this time. I had successfully cloned the HDD in middle of February, and thought I could chuck it in and just boot up. But I had "fixed things" since then that were not fixed at that time. I didn't want to go back through the entire log of troubleshoots and fixes. What to do?! What to do?!
The WHS server is still a "work in progress" as I move toward the controller changeover. BUT!! I DID re-enable the client computer backups for the WHOLE DAMN HOUSE!! And last night, between midnight and 6AM, WHS backup up all those machines from scratch (since I had erased all the old backups.)
Find a drive! I thought. The BIOS would show the original boot drive, but I couldn't get WHS's thumb-drive bootable repair program to see it. Finally I got the 1TB backup I'd made yesterday of the entire server. [As I say this, I pray that suddenly nothing goes wrong with that until I can back it up again!!] Reinitialized the 1TB Samsung F3. Started restoring: first, the stubby unlabeled "system" partition of ~100MB. Then, the C: drive.
Took four hours. And during that time, I was wondering "What if it won't boot because the cache disk is no longer connected?" I was searching the web on another computer, and found a blog by some a**h*** who was complaining that "WHS 2011 was seriously flawed" because it wouldn't "shrink" his backup to fit the new replacement boot drive. Even that seemed devastating to my confidence.
Went to the grocery on family errands, hurried hurried hurried to get back. Waited for what seemed like hours.
Finally, I get to the dialog box in the WHS client-restore screen that has the "finish" button. "Click finish and your computer will restart," it said.
REALLY?! I'm thinking. C'mon! REEE-ALLY?!! I was planning on more stations of the cross, litanies of pain, cycles of frustrated failure.
Went into BIOS, put the boot order to go to the Samsung drive after an empty optical drive was found.
We're back! We're bad!! Ba-bad! Bad, bad, bu-baaaa-ud! Those wingtip bozos don't have nuthin' on me! I thought.
So I'm happier . . . than a PIG . . . IN . . . . SH . . . --POOP!!