All Activity

If you need both systems running at the same time, for more than 30 days, then you'd want a second license. If not, you can just use the trial period, at worst. But basically: deactivate the current license on the old system disconnect the drives move hardware to new hardware (or swap motherboard/etc, or whatnot) connect the drives to the new system install StableBit DrivePool activate your license And at step 5, it will automatically rebuild the pool with the available disks. The only caveat here is that you might run into permission issues, but this is normal when moving disks to a new system, in general. You may need to reset the permissions, but that depends. But that's really all you need to do.

dval14sb: Thanks for that quick and easy answer. I agree supporting by buying another license is the way to go for this great program. The fact that I can just EASILY reinstall in a new machine is Fantastic. Thank you stable-bit!!!!

In my experience you can just bring the disks to the new machine, install DrivePool and all the drives will be read and pooled again. You may need to set/change the drive letters to your liking in Disk Management. You can also move / reuse your license from one computer to another although supporting the developer by buying additional licenses will give you more licenses. It's nice that the developer embedded the config with the drive rather than having to backup configs from some obscure place. That said, I read that there's a settings JSON file somewhere but I have had no need for it since the drives are "plug and play".

Hi. Love this program. Can someone with lots more experience tell me the best way to upgrade a machine currently running drive-pool?? I would like the new machine to use the same data and info I currently have. I would like to simply plug my HD's into new machine and go from there. I am guessing: a) buy another license (most likely) [I know I could just use one for less than 30 days] -I'd support the developers for this!!! b) bring up new machine with old disks?? Am I missing something big Thanks in advance

Thanks for the reply. I may need to dig into this more to see how it can be prevented or avoided.

Yikes! You weren't kidding. Hopefully mine won't get that bad. Mostly static. So far. Would hate to have to do that for 200 accounts. May need to find an automatic or scripted way. Thanks!

The latest best version is 2.3.14.1756, and there are a few memory related issues addressed by it. https://covecube.download/Changes/DrivePool/beta https://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.3.14.1756_x64_BETA.exe If that doesn't help, then could you open a ticket at https://stablebit.com/contact

It only displays one system/pool/drive, at a time. Much like the normal, local UI.

Could you open a ticket at https://stablebit.com/contact ? There are some additional logs to collect (just in case it's a system specific issue), and that is the best place/way to do so.

No. Unfortunately, because we're following what is prescribed for how these types to be handled. The onus is on the other software to handle things correctly, not for us to implement workarounds for incorrect handling.

Sure - MS is very coy about their supposed "space" out there. And they say nothing anywhere about versioning until you hit a scenario like this. The versions are NOT visible anywhere (easily). The only way to see what is really going on is burrow deep inside thee MS Admin Center for Sharepoint until you hit Storage Metrics and you will eventually get to a view of a single "chunk" that CloudDrive writes out to your OneDrive space: AND then finally - click Version History to see the damage being inflicted.... The only way - you and I can clear this crap is by clicking "delete all versions" - above. But this deletes the versions for just this single chunk. Cloud Drive has created 500 folders - with 500 1MB chunks in each folder. (25000 chunks total). It would take you months to visit each 1Mb chunk and click Delete All Versions. Some files in my stash oddly have 1 version. Others have 89. Still others have 132. No rhyme no reason to any of it. The biggest joke is in what universe could ever somehow cobble use ANY of these "older" versions and have it makes sense. At any give time - all 25000 of these 1MB chunks (assuming the last and latest version) go together in a single unique puzzle to form the overall "data" that is backed up in our cloud drives. If there was ever a more useless backup option than this - I have never seen it. All I know is once I get this sorted by MS - I am moving to BackBlaze B2. OneDrive (Business OR personal) was never designed to be used how I want to use it (Third level offsite deep cold storage) that will most likely NEVER be used for restoration purposes ever outside of a complete global emergency that wipes house and home over here. Finally - versioning CANNOT be turned off by you or I regardless of admin access or what not. The best I could do is REDUCE versions from an unbelievable 500 to 100 AND have the system clip any versions older than 30 days. That is simply not an option that will work for 25000 1MB chunks. Hello Backblaze - goodbye OneDrive. S

Thanks for sharing. Would you be able to share too where this versioning is saved and how you're getting rid of them? My MS OD CloudDrives are set to 900GB thinking it will not go beyond that and hit the 1TB limit (nothing else on the OneDrive). So far it hasn't but dreading it doing so. Is there a way to limit this versioning or eliminate it altogether? Also, is the versioning done by CloudDrive or MS?

Was there an update after the pinned post? Fix? I seem to have lost files this way with the file names to be correct but the respective content is not. Thanks!

Hi! I don't have a question, but a solution to a problem I encounted. I encounted the following issue for a few files (10s out of a million files) 11:11:11.1: Warning: 0 : [FileDuplication] Error checking file for duplication consistency or duplicating file \\?\GLOBALROOT\Device\HarddiskVolumeXX\<...>. Zugriff verweigert "Zugriff verweigert" is "access denied" localized. It took me a while to figure out what caused it. In my case there are three conditions to trigger it: have 2 duplicated files with a different file modification time the difference in file mod time has to be greater than 60 seconds the file must be read-only (not by ACL, just the normal file system flag) To solve it I just temporarily removed the read-only flag. My suggestion for the drivepool software: Either improve the error message to include the real reason for the duplication error (in the UI and the log) Or ignore the read-only flag and temporarily remove it before aligning the modification dates

Nope. Turns out its "versioning". OneDrive thought it was a good idea to create 683 GB of "versions" - which are proving to be a pain in the balls to clear. Working with MS now and all the Powershell (and rClone) muscle I can exert to try and dump all this useless crap. Also doesn't help that Clouddrive wrotes 1MB chunks to Onedrive - which of course then turn into thousands of 1MB version files - which eventually eat all available space - with no way for the user to get it back - outside of completely torching the Clouddrive container, deleting all backed up data and starting over. Which makes me wonder why I would use Clouddrive at all - or maybe I simply need to find a better provider. S

Is it possible there are files in OneDrive's recycle bin online (checking via browser) that need to be deleted?

All Have had Clouddrive connected to my main server for two years now - and it backs up to OneDrive for Business. The OneDrive storage is a 1TB is size and my "CloudDrive" allocation for this 1TB is 600GB: I have Cloud used = 317GB. Unused is 283GB. But the real kicker is this - that I just received from MS: If Cloud drive is only allocating 600GB of space - how it is possible to be out of space? I have looked at every angle of this - and it all adds up correctly: 317 GB - exactly used by Clouddrive: Exactly nothing - in all the other folders: Yet - I am sitting on the cusp of running out of space What is taking up the other 683GBs here? S

Cloud Dashboard for Clouddrive (and DrivePool) Hi, Looking into stablebit.cloud as a dashboard. Can/Does it show the status of multiple CloudDrives at the same time, for individual instead of total for all drives? Particularly want to see the the "to upload" and upload/download status. Same info shown by CloudDrive except one at a time (unless I'm missing it somewhere). Currently I need to "scroll" left/right to see the status for each CloudDrive. Similarly, can/does it show the status of multiple DrivePools at the same time? Thanks!

Stopping all StableBit services then powering down the server, switching off the drive bay device is something I did to change the drive letter from Z: to X: and back again, didn't change anything. I think it's time to open an official support request. 😆

Hmm. Something does sound messed up there. If it helps, pools created by DrivePool show up as Volumes and Disks in Windows Disk Management (WDM). Clicking on the Pool volume in the volume list (default upper half) of WDM should highlight the related (virtual) disk in the graphical view (default bottom half) of WDM. So if everything was healthy you should have a number of Disks in WDM equal to the number of physical disks in your machine plus the number of active pools, starting from Disk 0. To start with I'd suggest powering off, pulling all three disks from the Orico, powering on, and checking WDM to see the results. Then repeat but with just the one suspicious disk put back in (D#1, not the others) and compare. The new disk in the second list should be that disk (though keep in mind that the number allocated to each disk may be different and the pool "disk" may also show up - it shouldn't, but it might). Then use DISKPART, LIST DISK, SELECT DISK # where # is the Disk number to select the suspicious disk and CLEAN to wipe that disk clean. Make sure you don't select the wrong disk! Then EXIT and use WDM (may need to use Action -> Rescan Disks first) to first initialise it as a GPT disk and second format it as a single NTFS volume. Then power down, put the other two good disks back in and see if that's sorted it.

Changing the drive letter for 'Use_Drivepool Z:' to 'X:' hasn't fundamentally changed anything. 😥

Okay, I'm feeling a right Muppet, but still can't see how to correct this. Disk Management does see 3 physical drives, but one of them appears to have taken the identity of the virtual drive in my previous setup??? So now I have a physical drive labelled 'Use_Drivepool (Z:) in Disk Management but this doesn't appear as a drive to add to my pool. Instead StableBit lists it in the gui under the name of my PC (in my case, 'SERVER'). But I've no idea how to get the physical drive listed as available to the pool, or see a virtual drive made up of the 3 physical ones? Do I have a clash between the drive letter and path for the physical drive and the virtual pool drive? If so, how do I fix that?

Perfectly correct. 👍🏻 The only thing I'd add is that I had to use some command line diskpart instructions to get rid of the hidden partitions on D#1 and create the primary partition for the whole volume of that disk. I'm assuming that creating that primary partition also formats it as NTFS? Even if it doesn't, I'd still expect Disk Management to see it?

Just to make sure I have this right, rephrased: For the old server: You had an old Win 10 machine with (at least) three physical disks, I'm going to call them D#1, D#2 and D#3. D#1 was the boot disk for the machine; it had the usual boot partitions/volumes (including one formatted as a NTFS volume, C drive) and either the C drive volume was part of the pool or there was a separate partition that was also formatted as a NTFS volume that was part of the pool; either way I'll call that volume V#1. D#2 and D#3 were each formatted as a single NTFS volume, which I'll call V#2 and V#3 respectively, and those volumes were also part of the above pool. During the upgrade: You first removed V#1 from the pool, then balanced the pool, then shut everything down. For the new server: The new machine is running Win 11 Pro (and presumably DrivePool is installed). You've connected the physical disks D#1, D#2 and D#3 from the old server to the new server via an Oricon external drive bay. You've then redone D#1 to just have a single, new, NTFS volume which I'll call V#1a. Is that all correct? At this point DrivePool should be able to see a pool consisting of V#2 and V#3 (on D#2 and D#3) as well as an available non-pooled spare to add, V#1a (on D#1), since you don't mention adding the new volume to the pool yet. However instead DrivePool can only see V#2 and V#3, and even Windows Disk Management cannot see V#1a (or even D#1?), and if you pull any one of D#1 thru D#3 the whole pool vanishes from the DrivePool GUI (when, I agree, the remaining disks should still be showing up)?

Hi I had an old server with two physical drives and a partition of that PC's C drive in a drivepool under windows 10. All worked well for years. I now have a new server using Windows 11 Pro. In the upgrade I removed the partition section of the old PC from the pool, rebalanced and then shut everything down. The new Windows 11 Pro mini PC uses an Oricon 4 drive bay external unit to house the three drives from the old PC. I reformatted the old PC's physical C drive to have one primary volume. So got rid of two hidden partitions and what was the old C drive NTFS partition. Now, neither Stablebit Drivepool nor Windows Disk Management can 'see' that drive. And yet, if I remove any one of the three physical drives in the external drive bay, the whole pool goes down and all pooled drives disappear from the Stablebit DP GUI. I thought that if you pulled just one of the shared drives, only that drive would show as missing, but all the drives show as missing. Why? And how to get the old C drive to be detected by Windows? TIA