Christopher (Drashna)

StableBit CloudDrive could sort of do this. But not well.
However, it sounds more like you want to sync the contents between the two systems.  And in this case, StableBit CloudDrive wouldn't be great.
It sounds like you want syncing software.  Something like Free File Sync, GoodSync, or the like. 
Another option is to look into the DFS replication. As that may be closer to what you want. 

Awesome, I will do exactly that, as soon as I get a motherboard that works.  Stupid thing is getting RMA'd tomorrow.  I'll be getting my license later in the week

The removal of the 8TB 3ware drive from my MainStorage Pool completed sometime in the wee hours this morning. I removed the drives, and the 3ware card, then moved the replacement drives (2x4TB, 1x2TB, 1x1.5TB) into the slots emptied by the removal of the 2x2TB drives. So far, good.
Then, when I went to boot up, it wouldn't. After a few tries, I managed to get the system to enter the BIOS. I went to the Boot section. It showed one of the hard drives as the first boot device, and the DVD drive as the second. I pressed Enter to get a list of drives, so I could pick the Intel SSD that I installed Windows 10 on. It wasn't there. Hmmmm...
So, I went to the Disk Drives item and hit Enter. It showed 12 drives, none of them the Intel SSD. Double hmmmmmm.
I futzzed around with the connections and stuff and, finally, I managed to get the Intel SSD to show up. I picked it as the boot device and it worked. Not sure of all what I did, but I guess it's better to be lucky than good

Well, glad you found us! 
 
I do a full format (which writes 0s to the entire volume), and then let StableBit Scanner run a surface scan. That's it. 
Also, all of my data is duplicated
 
Caveat: I may be biased on the tools.
 

Only one?
 
That said, you want the "Drive Space Equalizer" balancer plugin.  That does what your expecting.
https://stablebit.com/DrivePool/Plugins
The "Volume Equalizer" only worries about data on the same disk, but different volumes/partitions.
 

Thanks Umfriend.  That was the last bit I needed to know before giving this a go.

Yeah there will definitely be some adjustment to the new forum software. 
there is a lot more functionality, but it is a lot more "under the hood" stuff, or will take a bit to get used to.
Also, there are probably settings on our end that will require tweaking, to get "just right", as well. 
 

After some research,I have decided, I am going to build a 24 disk JBOD connected to the host (Windows 10) via SAS Passthrough, if everything works, the host should see all 24 drives individually and i should be able to manage them in Drivepool. 
 
Hopefully? 

Chupa, my library is many thousands of titles and only takes a minute or two to update. Are you, maybe, referring to the initial adding of new media from a directory to your library? It does an analysis scan on the files during that addition that can take some time, but a normal scan where it simply looks for changes and additions should be a matter of minutes, no matter how large your library, even if you don't have the "run partial scan" option enabled. 

Wow! 
That's .... well, yeah, memory issues can cause all sorts of odd behavior! 
 
Hopefully, this does fix the issue for you.
 
Also, if you ever need the MSI file, we stores those separately, actually.  Check out the "Managed_Deployment" folder.  You'll find an MSI for almost every version. 

Hi
 
I just updated Windows and now DrivePool won't load one of my pools.  I have 4 drives assigned to two pools (two drive per pool), and one pool won't show up in DrivePool on my system. The data is on the drives, including the hidden DrivePool folders, but DrivePool won't recognize the pool data as being on either of the two drives.
 
When I open DrivePool I can see the two drives in the list, so it looks like I can create a new pool with the two drives, but the original pool can't be seen.
 
The interesting thing is that the disk management option in Windows shows a new partition as RAW (2TB), as well as a second unallocated partition (2TB) (CoveCubeFS - which I assume is related to DrivePool). I'm not sure where those come from as the missing pool drives are 3TB each, with about 1TB free (they are duplicated with each other in the pool). All drives are accounted for in Windows' disk management tool.
 
How can I go about getting the pool working again as well as preserving my data?
 
UPDATE: I just saw another post that had the same issue: http://community.covecube.com/index.php?/topic/3228-update-to-fall-creators-update-x64-win-10-all-pools-gone/. Uninstalled DrivePool, rebooted, and reinstalled DrivePool and everything is back to working fine.

Ok I was wrong about Nvidia drivers causing the remote control issue. But bear with me, I do have the definite answer.
 
 
From the beginning:  Prior to the FCU, both Drivepool and Scanner were able to remote control without any issues using beta versions up to 2.2.0.870.  So I updated all three devices to FCU, then Kaspersky Total Security intsalled a major update to itself I then installed Drivepool Beta 2.2.0.875.  As standard practise I then created images of all three systems using Macrium Reflect. 
 
on rebooting and leaving the devices running for a couple of hours I found that Drivepool would not remote control on any of the three devices. I posted here and worked through all of the fixes recommended by christopher and a few of my own, with no positive result.
 
I honestly thought it was Kaspersky to blame, but fully uninstalling this proved me wrong.
 
I had noticed problems with the start menu and taskbar as well by now and also sluggish performance with these systems.
 
So I restored all three images which I had taken just after the major update, I was now working from a known baseline.  I then noticed the problem with the video drivers and all the other Nvida stuff that Windows update had installed. I removed these and re-installed the correct driver and everything was fine.  Seemed very strange that this could be the cause, but hey it worked, drivepool and scanner were remote controlling fine again and the sluggishness had gone along with the taskbar and start menu problems.  Worked fine until next reboot, then same problems resurfaced.  
 
I then checked through installed updates and found that Windows had silently installed KB4043961 shortly after I had updated to FCU.  This update coming into force after each system was rebooted hence 
the systems working fine then the sudden problems.  Uninstalling KB4043961 and further hiding it, so it does not attempt installing again, totally solves the problems with remote control, taskbar etc. 
 
Obviously this update had sneaked in after I had created the original images of the three systems and again shortly after I had restored all systems, and incorrectly thought I had cured them with the correct video drivers.  
 
Just this morning I thought I would google and see if anyone else had issues with this update and found the following post.
 
http://www.tomshardware.co.uk/forum/id-3554170/fix-taskbar-start-button-clickable-windows-pro-v1709-build-16299.html
 
 
The poster had seen similar issues to me with the taskbar etc.  

Late this afternoon the 6TB HGST hard drive I ordered on sale from NewEgg arrived. I put it into my OffSite Lian-Li enclosure, added it to the OffSite A pool, and am in the process of removing the 4TB drive that was part of the pool. It's going slowly, but seems to be working. The 4TB drive that's coming out will then replace a 2 or 3 TB drive in the NearLine pool, giving both pools another terabyte or 2 of room.
 
Hopefully, with Christmas sales coming up, I will be able to get another couple of 6TB drives that I can use to replace the 4x2TB drives that make up most of the MainStorage pool (that's the one that's showing the sector errors). That, in turn, will free up another 4TB drive that can be used to expand the OffSite B pool. When it's all done, every pool should have no less that 1TB of free space, and most should have 2TB. That will last me a while.

Well, I ran chkdsk /r /scan /perf again, and this time it got to a Stage 5. I didn't see it do that last time. Anyway, apparently Stage 4 checks only sectors that are currently being used by files and Stage 5 checks the ones that are currently unused.
 
Stage 5 found 3 more areas (again, remember, this is over 4 drives, not just 1). It said it was flagging the areas for later repair. After it finally finished I ran chkdsk /spotfix. This took overnight to complete (well, I got tired of waiting for it to finish so I went to bed). It did complete though. I then went to Scanner and tried a Surface Scan. It sill said there are bad sectors and flagged the drive as Damaged. So, I went into the options for that drive and told it to Not do Surface Scans. At least, that way, I can still use the drive without Scanner preventing me from writing files. To be honest, despite what Scanner says, I haven't noticed any issues with the drive. And, since chkdsk has done its own scan of all the sectors, I'm hoping I'm fairly safe. And there's always the fact that I have quite a lot of backup. Between them all, I figure I'm not too bad off.
 
Oh, and I did something today that I think is pretty geeky: I set up OpenVPN on my (Dad's) Untangle box, something even he hadn't done. I had some missteps, and had to get help from the Untangle forums, but I was able connect up my Surface tablet to my phone's Internet Sharing and then use
Windows Explorer to get to the files on my new Windows 10 server. And, thanks to an article by a guy named pcdoc, I found out what Full
Tunnel means and got it to work. Now, when I'm away from home, I can surf the net as safely as if I was still at home. Pretty cool. Sorry, I know this is off topic: I hope that's OK.

Great News. Like to see that Feature too! 

So right now i have it setup as a pool.
 
Got about 21.8TB of space.
 
Have no enabled File Duplication yet.  Running 2.1.1.561.
 
So far everything is running great with the new case and new added stuff i have put in this system.  Just wanted to know if there was a way to hide the drives that are in the pool in the My Computer area?
 
Also am i enabling Pool File or Folder Duplication?

The "Advanced: Manage DrivePool" worked to bring it up.  I also found it in the apps section when I was looking for my UPS icon.
 
I'm Rockin N' Rollin now, thanks for the replies.

Methanoid,
 
We do weigh the accounts to determine who wins. It's not entirely random. 
 
So "spam accounts" like this are much less likely to win. But accounts that are used and engage on twitter are favored more to win.

The "cloud used" amount refers to the space used on your provider, not the amount of data stored on the drive. When you delete something on your CloudDrive drive, it doesn't remove the drive architecture that has already been uploaded from from the provider. So, if it's a 500GB drive and you've already created and uploaded 500GB worth of chunks to the provider, those will remain, just like a real drive, to be used (overwritten) later. This is why you can use recovery software to recover data on your CloudDrive drive just like a physical hard drive. If you want to remove the additional space, you'll need to shrink the drive, which you can do from the "manage drive" options. 

Had the same issue. My unable / other have gone away after a couple of days (2-3) of balancing.

Supermicro cases are the best! 
 
Yes, the 45 drive bay cases are only drives, no actual motherboard. 
 
However, you buy one of these: 
https://www.newegg.com/Product/Product.aspx?Item=9SIAD5G5N06260&cm_re=9207-8e-_-2AS-008U-00003-_-Product
Then hook up the enclosure.
 
Or you pick up something like this:
http://www.supermicro.com/products/chassis/4U/847/SC847E26-R1K28LPB(which is what I have) 
 
 
 
But honestly, my best suggestion would be to contact SuperMicro directly and talk to a representative.  they may be able to help you out.
 
 
 
 
As for RAID cards, you want HBA stuff, unless you plan on doing RAID.  
As for RAID caching, that's done "on controller", IIRC, and much more expensive. 

So I managed to flush the MetaFile back to a few 100K using my mem util and rebooting (several times).  DP is now "checking" all the files and as it is doing that the MetaFile is growing steadily.  At the Checking 20% mark I've lost 6GB to the MetaFile so far.....and at:
- 25%, 8.5GB
- 50%, 24GB
- it then seemed to "stopped" growing when it hits 26GB!

I'd recommend something like the CyberPower CP1500PFCLCD.  I have one of these, and it's been fantastic. And it's Active PFC (True Sinewave).  matters if your power supply is as well. 
 
Otherwise, UPS's are expensive across the board. Even on EBay and the like.

OK, first, just in case any one here knows of Ikon, let me say, I'm not him. Ikon was my father. I say 'was' because he passed away in 2012. I inherited all his tech, including his forum and social media accounts, software licences, etc. Anyway, I am not the techie he was but, for the past 5 years, I've been learning. His notes, emails, forum posts, and just things we talked about over the years have been invaluable in getting me more up to speed.
 
That said, in the past couple of days I've picked up a couple of things about DrivePool that I thought might be helpful to another newbie at some point.
 
I had a 3-drive pool set up, and it was working fine until Scanner found some unreadable sectors on 1 of the drives and labelled it as Damaged. I tried Removing the drive from the pool, but it wouldn't work. The pool's whole page was kind of grayed out: I couldn't do anything on it.
 
I shut down the computer, removed the 'damaged' drive, then booted up. DrivePool said the drive was missing (yup, it was; good of you to notice), but I still couldn't Remove it.
 
I moved all of the data folders from the PoolPartGUID folder on each of the 3 drives to the root of each drive. Then I deleted the PoolPartGUID folders.... all except for one that simply would not delete. I got an error every time. This particular PoolPartGUID folder had a .covefs folder in it. It always seems to be that specific PoolPartGUID folder that won't delete.
    I finally got around this issue by getting Properties on the PoolPartGUID folder, going to Security, then Advanced, and giving Ownership of the folder to my account. After messing around with it a few times I was able to delete the folder.
 
However, deleting the folder didn't completely solve the problem. Even though none of the drives had a PoolPartGUID folder on it any longer, DrivePool refused to list the drives in the list of non-pooled drives. Somehow, it thought the drives were still part of a pool, even though it no longer would display a page for that pool. I could have gotten around the issue by use Disk Manager to delete & recreate the partitions from all the drives, but I had almost 4TB of data on them. That's a lot of recopying. It was a Catch-22.
 
Thanks to this forum, and Courtney (who is the most awesome tech support rep I've ever dealt with), I found out about the Reset All Settings feature, although it took me a couple of minutes to find it (it's in the Troubleshooting section in the tiny gear icon in the top right area of the DrivePool window). After resetting the settings, the 3 drives showed up in the list of non-pooled drives, and I was able to build a new pool with them.
 
Many thanks to the posters in this forum, and many, many, many thanks to Courtney. Stablebit/CoveCube is very lucky to have him.
 
 

Not a problem. And yeah, that's the mentality that Windows encourages/forces upon you. 
 
And odd on Everything.