BYUSinger84

I didn't want to re-open this thread: https://community.covecube.com/index.php?/topic/1485-access-denied/ But my issue is similar. My pool is made up of 100 TB of total disk space. The entire pool is duplicated. I have two pieces of software that run on this pool. At some point, one of my disks went offline due to a bad power strip. When this happened the pool (or at least the duplicated files from that disk) were set to read only mode. Now, I understand the logic behind this but it caused my software to panic and create all sorts of other problems and issues. So my question is... Is there a way to set it so that if/when a disk goes missing in the pool as long as the data has been duplicated, the drive will continue to function and then sync the pool data with the drive that went missing? This would be my ideal solution. If that's not going to work, then the only other potential recourse would be to remove my software from the pool but that's the reason I have the pool in the first place. I tried to find the advanced option that was described in the above post to change that behavior but I can't find it. I know that post is from 2016 so it's a bit old at this point. Was this feature ever implemented? What are my options here if I want to continue to use the pool in the fashion I am choosing? In my specific case, I will always assume the data from the pool is more up to date than any files from a missing disk so I am ok with the pool files overwriting any changes that need to be made to the missing disk once it comes back. Thoughts?

By the way, it looks like the move down to the host level worked perfectly. I wonder if it has something to do with me passing a 3 TB drive through. I've heard that drives larger than 2 TB don't work quite well in Hyper-V/VMware.

I mean the client backups on WHS 2011. If I reinstall WHS 2011, patch everything, is there a way for WHS 2011 to detect the client backups again?

To answer your question though, Chris, there are no SMART errors. I've removed all the drives that were having issues.

I've pulled the drives out of the Hyper-V server and now are native on my Host. We'll see what happens. In the mean time, I do have backups that I CANNOT lose on the pool. If I rebuild the server with WHS 2011 as the primary OS and then attach my drive pool, is there a way to reattach my backups?

I've updated my drivers for my chipset to the latest trying to see if that helps, but no dice. Once I start the DrivePool service everything in Windows freezes.

Well, I kinda have to pass the disks through for everything to work, do I not? Since I don't have virtual hard disks. The NIC is Intel.

Yes. I have tried this already. Thanks for the suggestion though. It was a good one.

The only thing I can say for absolute certain is that it always freezes during measuring or calculating. Balancing ALWAYS works perfectly. Within minutes of getting to calculating/measuring, the GUI and the network shares hard lock and leaving it overnight does nothing yet the CPU is obviously working hard doing something as it bounces between 30-75%. Any other thoughts Alex? Would you like remote access at this point? I don't know what else to try. Thanks.

Ok, nevermind. Honestly I have no idea what the heck is going on. I thought things got back to normal once I uninstalled Scanner from both machines but now the problem has resurfaced again. I've also tried the latest version of the drivepool now. Same problem. What the heck is going on?!

I can now confirm that it's ONLY when the scanner is installed on the host machine. On the VM, it works. Once I install it on the Host and then reboot the VM, then the freezing begins again. Hope that helps.

Yes. I'll do some digging. Thanks.

If you uninstall DrivePool from the add-in tab (also check Add/Remove Programs afterwards), reboot, and then re-install everything should come back like normal. Because DrivePool isn't dependent on hardware or controllers or RAID setups etc, the minute you re-install, DrivePool will automatically add your pool back into the dashboard.

An update. So, I was going to try the other versions, but then, of course, everything broke again. I couldn't believe it. After working solidly for a few days, it reverted back to what it was doing before. In an attempt to further track down the problem, there was only one other common denominator: StableBit's Drive Scanner. I thought, "This can't possibly be it," but after thinking about what had happened leading up to the days, moments, before everything stopped working (after working fabulously for years, I might add) aside from the update to DrivePool at the time, I also bought and installed Drive Scanner not only on the VM, but on the host machine as well (the VM can't see the SMART status of drives). I thought, it's worth a shot, so I uninstalled it on both the VM and the host. And what do you know, everything is working like normal again. Obviously, I'd like to use the software I paid for, but if this was really the problem the whole time, I ask myself if the dynamic of having WHS 2011 on a Hyper-V is part of the issue as well. Thoughts? Comments?

I will try that version. I will post my findings. Thanks.