locus123

Those folders only showed up as "shares" after I ran the WSS Troubleshooter and recreated the shares. Although they could have been there prior, I really don't know. They're empty however, and I've deleted them. I looked at the folders I had duplicated previously, and they won't account for the size mismatch (if it was their duplicated data that was lost). As for the logs, I'm running 1.3. It looks to me that unless I enable tracing, logs aren't captured. Is that correct? If so, any suggestions?

The ugly: - System Restore wouldn't work. Even when I restored the last backup, and a backup from a week ago, to a new hard drive, I still got the blue screen. It doesn't makes sense, but I didn't have time to figure it out. I gave up and reinstalled WHS2011. The good: - After WHS2011 install, then hours of updates, and Drivepool installation, it recognized all my drives and the pool was back. (except for not taking my license, which I've opened a support case for) The bad/unknown: - There are two "folders" that have crazy long names. e7ad45af09d7fc7db3283f942b724458 is one of them. They're empty. - When everything first came back, it looked perfect. Then Drivepool was "duplicating data" for a while. All of a sudden I went from 800Gb free (which is what I had before) to 3.6Tb free. I have no idea where the space came from, but I'm afraid something was lost. Is there any way to tell what happened? Logs or something? I've looked and I can't tell if anything is missing. There are hundreds of movies, and thousands of pictures (which is what I really care about).

Thanks for the empathy! Not pleasant at all - especially the words from my wife. Yes, the system and the data were on separate partitions. However, not ALL the data was duplicated. Only the stuff i deemed worthy (pics, music, docs, etc). I'm not sure why, but even a System Restore on the old drive doesn't work. It still blue screens. The drive itself might be toast. OK, it sounds like my plan should work then. I'm going to do a System Restore to a NEW drive and try to boot. If that works, I'll hook up the "bad" drive, and the other 4 working drives, and hopefully the entire original pool is recognized. If it is, then I'll ask Drivepool to remove the bad drive from the pool which should copy everything off of it, then format that drive and see if there was physical damage. Thanks Christopher!

I have Drivepool running on WHS2011. Pretty sure it's the latest 1.3 version. We had a power outage and my server died. Now I get a bluescreen as Windows boots up. I've tried a System Restore - same bluescreen. I've tried chkdsk /f - same bluescreen. If all I had on that drive was the System Image, then I'd just restore it to a new drive. Unfortunately, half of it was the System drive, and the other half was part of the pool. What is the best way to attempt to recover the drive pool piece of this drive? I'm thinking to System Restore to a new drive and attempt to boot. If successful, then bring online the "broken" drive, plus the other 4 drives, and check the pool status. Will that work? Will the pool be smart enough to just piece it all together?