Shane

C:\Windows\System32\dpcmd.exe You should access it by opening a Command Prompt, run as Administrator, and simply entering "dpcmd" or "dpcmd [command] [parameter1 [parameter2 ...]]" where "[command] [parameter1 [parameter2 ...]]" are what you're wanting it to do (and you'll get the list of those options by entering "dpcmd" by itself).

Yes, a volume needs to be Simple and its disk needs to be Basic to be usable by DrivePool. Windows Disk Management unfortunately does NOT support converting an in-use disk from Dynamic back to Basic without erasing it first. To perform the conversion without data loss you would need to use a third-party partition manager with that capability, and there is still a risk; I would strongly advise having a backup first.

Just confirming, you've tried GUI -> Cog icon -> Troubleshooting -> Recheck Duplication...?

I've only seen the "unable to enumerate folder" error be caused by an invalid/corrupt ownership or permission setting on a poolpart or subfolder, but I can't say there aren't other possibilities.

I don't know if it has been resolved (and, if the cause is the use of "virtual-unfriendly" function calls by the third party tools, it would not be possible to resolve except by the makers of those tools). If read striping is enabled and the CRC errors are reported by hashing/verification utilities you rely on, I would turn off read striping. If read striping is not enabled, then there may be issues with your hardware.

It shouldn't cause problems (on the other hand, I don't know why DP is having this problem!). Recreating the pool (assumes you only have the one): Make note of your settings (performance, balancing plugins, file placement, etc) if you wish to keep them. Uninstall DrivePool. Optionally, delete the following folders if they remain: "C:\Program Files\StableBit\DrivePool\" "C:\ProgramData\StableBit DrivePool\" On each drive in the pool rename the prefix of the hidden poolpart folder (e.g. from "d:\poolpart.xyz\" to "d:\oldpart.xyz\"). Reinstall DrivePool. Create your new pool and add the drives. Optionally, restart the computer after adding each individual drive to see if the problem returns even with a new, empty pool, in case a particular drive is involved. Disable the Automatic balancing (if used). Stop the main DrivePool service. On each drive, move your content from the old oldpart.xxxx folder to the new poolpart.xxxx folder. Leave behind - do not move - the "System Volume Information" and "$RECYCLE.BIN" and ".covefs" folders. Optionally, restart the computer after moving each drive's content to see if the problem returns, in case particular content is involved. If you're doing this, remember to stop the service before each move. Start the main DrivePool service. Perform a Re-measure if DrivePool has not initiated one. Put your preferred settings back and re-enable the Automatic balancing (if used). If everything is behaving and where it should be, delete the oldpart.xxxx folders.

Hi SteveMc, you could try the steps I describe in this post: https://community.covecube.com/index.php?/topic/5810-ntfs-permissions-and-drivepool/&do=findComment&comment=34550

1) Adding a disk to a pool only makes its free space available to the pool, via creating and using a hidden PoolPart folder on the disk; it does not automatically add that disk's existing content to the pool so any existing files stay where they are. If you want to quickly move those files into the pool rather than copying them "between" disks (because Windows treats the pool drive just like any other drive) then you can "seed" the pool as per this article - except that in step 4, where it says "For example, find the "G:\Files\" folder, and move the "Files" folder to "G:\PoolPart.xxxx\" you should first ensure that no other disk you plan to seed contains a folder or file at the same level with the same name. Otherwise, DrivePool will think they are duplicates rather than unique files. To avoid that risk, if you are seeding I suggest instead creating unique subfolders in the poolparts, e.g. moving "G:\Files\" into "G:\PoolPart.xxxx\G\" and moving "H:\Files\" folder into "H:\PoolPart.xxxx\H\", etcetera, so that you see "P:\G\Files" and "P:\H\Files" in the pool and can rearrange them at your leasire once they're in the pool. 2) DrivePool's File Placement rules let you assign folders to prefer or exclusively use specific disks, e.g. you might decide that the "Piano" folder can only be stored on disk A while the "Violin" folder can only be stored on disk B. However, there is no way to "automate" this for new folders (although any subfolders of an assigned folder will default to inheriting the assigned folder's placement). On that note, DrivePool does not save its own separate record of which files are on which disk in a pool; it simply queries Windows' own file tables in memory for each disk. This means if a disk should fail then you cannot ask DrivePool "what files were on that missing disk", so if you want to keep a record then you will have to do so via some other utility.

I'd suggest opening a support ticket to ask for help. Please let us know if there's a general fix?

If you're rotating a set of drives (e.g. maybe you've got 4 backup drives, one for each week of the month) then normally Windows should assign the same letter to a given drive once it re-encounters it in the rotation (unless for some reason that letter is already in use - or was in use but Windows decided for whatever reason that it won't free the letter). You may need to manually assign each drive the letter via Windows Disk Management (pick one that is unlikely to be used by other drives connected at the same time, e.g. if your usual drives occupy "C" to "K", pick "U") before this will stick. If it's always a brand new drive that you're using in the cradle* then normally Windows will assign the first free letter it has available to it (e.g. if you have drives C, D, E and plug it in it should get F) but if that's not happening (because Windows) and you don't want to do it manually then you'd need a program/script that assigns a letter or path based on the cradle's port number or device ID or similar fixed identifier. ... and I've just found this program: https://www.uwe-sieber.de/usbdlm_e.html which may be what you're looking for, I haven't tried it myself. *(I've also seen it called a dock or caddy, or hub if it can take multiple drives)

As I understand it, SnapRAID requires that the usable space for each of its parity disk(s) must all remain equal to or larger than the largest used space of each of its data disks to avoid running out of disk space for parity calculations. How does that work with your setup?

The only way I know of to stop an active remeasure is to stop the StableBit DrivePool service; any pools will continue to function but balancing won't occur until the service is started again. You can set DrivePool to remeasure somewhat quicker by clicking the little ">>" icon to the right of the organizational bar in the GUI. You can also adjust the settings.json file (CoveFs_MeasureBackgroundTaskPriority and DrivePool_BackgroundTasksPriority - be sure to read this link first) if you wish to change the priority further. There is an option in settings.json that is only described in the changelog - "Added PoolPartUpdates_AlwaysConsistent config option to disable the remeasure and duplication check passes after a missing disk comes back online" - but I do not know if it would apply to remeasuring after a forced reset.

No idea why it happened but I'd suggest removing it from the pool and recreating the partition at full size yourself, with a full (not quick) format, just to ensure there's nothing off with the drive.

As DrivePool relies on the file system as to which drives contain which files, if you didn't have duplication enabled then you'd have to compare with a recent backup or saved listing you've made if any to see what files are missing.

A faulty disk could interefere, yes. Best wishes.