Shane

Just out of curiosity, what version were you running when you initially encountered the problem? Huh. I'm not seeing anything mentioned in the changelog from 1663 to 1680 that would do that, and the screenshot of chatgpt mentions a problem that was fixed in 1345 which is before both of those builds. Glad the latest version worked for you anyway!

SyncThing does not rely at all on persistent FileID and does not rely solely on watcher notifications, thus it is not vulnerable to DrivePool's FileID collisions and is insulated against DrivePool's change notification bug. However, as MitchC mentioned, there is another DrivePool issue, the Read Striping bug. While that bug is apparently not omnipresent across installs (so you may just be one of the lucky ones) and requires Read Striping to be both enabled (warning this is currently the default on new installs) and active (because even if enabled it only affects pools that are using duplication) it is definitely something to be neutralised. TLDR as far as solely SyncThing + DrivePool is concerned, if you're not using duplication you're fine and if you are using duplication but not using Read Striping you're fine; if you have been using duplication and Read Striping then you should disable the latter and check for corrupted files (and the nature of the bug means a file corrupted on one pool could then be synced to the other pool in that corrupted state).

There is no such version of DrivePool, chatgpt is making stuff up. You can find all 2.x Releases at https://covecube.download/DrivePoolWindows/release/download and all 2.x Beta versions at https://covecube.download/DrivePoolWindows/beta/download - the latest build is currently StableBit.DrivePool_2.3.12.1680_x64_Release.exe which was uploaded 7th May 2025.

Hi, what version number is chatgpt claiming exists? And are you asking about StableBit Cloud (which provides centralised management of other StableBit products) or a different StableBit product such as CloudDrive, DrivePool or Scanner?

The short of it is that CloudDrive allows you to designate a supported storage provider (e.g. dropbox, a network share, even a local drive) and 'format' a specified amount of space in it to present that space as a cloud-based drive to Windows. If you're familiar at all with mounting disk image files over a network share (using tools like VirtualBox, HyperV, etc) that's basically what CloudDrive lets you do except the "image file" is a folder full of block files kept in your cloud account. E.g. if you had a Dropbox account and you reserved 1TB of space as a CloudDrive drive, Windows would see a SCSI drive of that size in File Explorer. Pro: you can treat your cloud storage just like it's a physical drive on your computer, and you can do things like encrypt it locally so it can't be read by anyone in the cloud without the password you set in CloudDrive. Con: just like a physical drive, it can only be "plugged into" and readable from one computer at any given time (unless you have a way to share it out - just like a physical drive). As far as syncing/storing Dropbox files locally, you could use a CloudDrive drive as a drive in a DrivePool pool and mirror via duplication or you could use a tool such as FreeFileSync or SyncThing to mirror between your dropbox folder and your pool drive. There are technical pros and cons to either approach. If you just want to mount your entire Dropbox as a network drive (basically just give it a drive letter instead of being a folder) there are other third-party apps that can do that.

Condolences on the data loss. Sounds like you got hit by something nasty. Yes, that's correct. DrivePool considers a file that is in the same folder tree (e.g. folder\subdolder\name.ext) on multiple poolparts inside a pool to be a duplicated file, because that's how it does duplication. However if you weren't using duplication then yes it is most likely due to balancing and the recovery software un-deleting the moved files: 1. If the "duplicated" file has different last-modified dates on those disks DrivePool will consider that an error and offer to keep only the newest file or let you resolve it manually. 2. If the "duplicated" file has the same last-modified dates on those disks but different sizes DrivePool will also consider that an error but leave it up to you to resolve manually. 3. If the "duplicated" file has the same dates and sizes on those disks DrivePool will presume there is no problem even if the files are not identical in content, and proceed normally - which if you have duplication turned off means it will delete one of the "duplicates" to free up space in the pool. In theory so long as the what happened to the old lost pool was only the deletion of its files, the recovery process restored the deleted files in full, and the files going into the new pool are only from the old lost pool, then you could simply seed the new pool and you should only run into issue #1. In practice it's possible that the recovery software may have only partially recovered some file contents, leading to issues #2 and #3. Another issue you'll run into is that recovery software can't tell the difference between deleted files you wanted deleted and deleted files you didn't want deleted - so you'll have to get rid of the former all over again. If possible make a back up of the recovered content before you do anything else with it (including recreating your pool). Then perhaps use something like DigitalVolcano's Duplicate Cleaner (I used this as an example because it's the one I know best) to identify duplicates and uniques by date, size, name and content so you can resolve the above issues in an interface that's designed for it, again before you recreate your pool. While there's a bit of a learning curve, as a dedicated tool it has a lot more capabilities (such as being able to detect files that look identical but have different content) than DrivePool's basic same-name-but-different-date detection. P.S. If you do plan to use duplication in the new pool, remember to turn off read-striping.

You can use Windows' Disk Management to remove (or change) a drive's associated letter entirely: open WDM, right-click the drive, choose "Change Drive Letter and Paths". Thanks for the registry tip though!

I've found it flaky too, never figured out why but it wasn't something I was worried about to more than poke at briefly.

Does Scanner or HDD Regenerator give the same warning if the test is run with the drive on a different computer? This'd be something you'd have to ask Seagate.

A few options that come to mind: You can right-click the column labels row in the Scanner GUI and enable display of drive letters if it isn't showing those. You can right-click a specific disk and select "Disk Settings" to (amongst other options) change the Name of it from the default (the latter usually being its model code) to something you can more easily match with DrivePool. If you don't use drive letters for your poolpart drives, you can mount them to a path in Windows Disk Manager (e.g. c:\disks\1, c:\disks\2, c:\disks\3, etc) and both Scanner and DrivePool will show that path instead of the drive letter.

Hi Expo, Where it says "Manage Pool" (about halfway down, left side), click that and then "File protection" and then "Folder duplication".

That's fine. The thing to avoid is any risk of recursion - e.g. if you've got a drive mounted as a path on another drive, never add the latter drive to a pool that includes the former drive. So in this case you should make sure you never add your C:\ drive as a disk to either pool.

Hi priyan, sorry for the late reply. If it keeps getting stuck on those same % for those same drives even after restarting or rebooting, I'd be suspecting those drives are faulty. If it gets stuck at changing % it might be bus or power related (e.g. if they're USB drives).

Hi Korok, I'll have a go at answering: There's no "one click"-style option built into DrivePool to do a direct swap between an old and new drive. If you remove a drive, files on that drive will be moved to the other drives according to any rules set for those drives or the pool in general. You'd have to either (a) update your location rules in advance of removing the drive or (b) update your location rules afterwards. If you have a rule that says files can ONLY go on a particular drive and you remove that drive it will revert to allowing ANY drive (otherwise it'd get stuck) so I'd recommend updating your rules in advance as it will ensure the files go where you want. If you right-click a disk in the GUI there should be the option "Disk Settings..." which will let you set change some settings just for that disk. Also, buried in the Advanced settings for Scanner is the option "ScanMaximumConcurrent" which lets you change how many drives Scanner scans at the same time - but unless it's been updated it may instead be the maximum per controller. E.g. if you set it to 2 and you have five disks on controller A and five disks on controller B it might scan 2 of each at the same time. Haven't tested this recently. Correct, there's no database of files kept in DrivePool. You'd need to find a third-party tool and run it on a regular basis. That's correct! Any given file simply exists on one (no duplication) or more (duplication) drives. Correct, and while I'm not sure whether it would "duplicate first and move second" or "move first and duplicate second" (I'd guess the former) the end result would be the duplicated files being on both Bay1 and Bay4 and no longer on Bay6.

DrivePool shouldn't be moving files out of a disk (whether or not Scanner is doing a full disk scan) unless Scanner is actually picking up a warning from that disk that triggers the plugin. There's no cli or api option; you could make a feature request here.

Glad it fixed itself! Each pool should be visible in Windows Disk Manager as a 2048.00 GB NTFS primary partition on a 2048.00 GB Basic disk. Opening the Properties of that partition should show the combined size (used, free, capacity) of the actual drives that form that pool. The unallocated disk COVECUBECoveFsDisk____ that showed up is the virtual disk failing to be initialised for some reason during boot, though it's (even) weird(er) that it also showed as an initialised version too.

Manage Pool -> File Protection -> Pool file duplication = lets you set the base pool-wide duplication level. Manage Pool -> File Protection -> Folder duplication = lets you view and set duplication level (including none) for specific folder(s) (trees) differently from the base pool-wide level. If you haven't enabled duplication for a pool it won't give you the option to disable it (because there's nothing for it to do). But if you have enabled duplication and it's still not giving you the option to disable it, that's sus. Close the GUI, run a command prompt as an Administrator and try the command dpcmd reset-duplication-cache p: where p: is the pool you want reset, then open the GUI again and check if it's working properly.

It's been a looong week. You could open a support ticket with StableBit or you could manually recreate the pool? The latter would involve stopping drivepool, renaming all of the hidden poolpart folders on the pool's drives (e.g. putting an x in front of the name), starting drivepool, adding the drives you want to a new pool, stopping drivepool, moving your content* from each drive's old hidden folder into its new hidden folder and starting drivepool again). *not the system volume information, $recycle.bin or .covefs folders

I'd suggest contacting StableBit directly (choose "An issue with licensing").

Hi! Any files that took up the last 2TB (1.82TB after formatting) of the 10TB drive couldn't be duplicated onto the 8TB drive because the latter wouldn't have enough space.

Writing/reading a pool should be close to as fast as doing so with the underlaying drives, so something's broken; ten minutes to open a folder is just flat nope. If you create a second, new pool on a new drive does it have the same problem?

Hi arizzi, please see this thread: https://community.covecube.com/index.php?/topic/12577-beware-of-drivepool-corruption-data-leakage-file-deletion-performance-degradation-scenarios-windows-1011/ TLDR, DrivePool's implementation of FileID is persistent across neither reboots nor moves, and increments from zero on the former so collisions are inevitable. Furthermore, for potential problems with checksums if read striping is not disabled on a duplicated pool see this thread: https://community.covecube.com/index.php?/topic/5414-pool-file-duplication-causing-file-corruption-under-certain-circumstances/ TLDR, to avoid potential checksum/data corruption you should disable Read Striping on any pool that uses duplication. There is no ETA on a fix.

I know Christopher (one of StableBit's staff) has mentioned on the forum that he'd like to see it but I don't know if it's progressed from "wishlist" to "roadmap".

(disclaimer: I'm very much an amateur at SnapRAID) As I understand it the "sync" command should have updated the parity record so the "diff" afterwards should only be showing differences since that "sync". So that should mean the missing files/folders went missing after the sync? The "fix -m" is supposed to restore any files deleted since the last sync, I think it would try to restore to the drives those files were deleted from. So depending on your balancer settings DrivePool may warn and/or try to rebalance afterwards.

Unfortunately there is still no Scanner support for reading SMART from SAS drives.