Shane

Licenses linked to stablebit cloud can be reassigned via the cloud portal without needing to deactivate a stablebit app manually (e.g. before a windows reinstall). Otherwise you need to manually deactivate the app first or - e.g. if windows falls over and can't get up - you may need to contact stablebit support to have them release the license.

I would suggest using the official plugin until the issue re-occurs and then follow the directions at https://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection to create a log of it happening to send to StableBit and open a support ticket.

Are you using the official SSD Optimizer plugin or the user-made All-In-One plugin? Does it make any difference trying the other one?

FWIW, digging through Microsoft's documentation, I found these two entries in the file system protocols specification: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/2d3333fe-fc98-4a6f-98a2-4bb805aff407 https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/98860416-1caf-4c80-a9ab-8d61e1ccf5a5 In short, if a file system cannot provide a file ID that is both unique within a given volume and stable until deleted, then it must set the field to either zero (indicating the file system does not support file IDs) or maxint (indicating the file system cannot given a particular file a unique ID) as per the specification.

I can see the "missing" disk in the list of non-pooled disks so I would normally guess the metadata that basically says "this disk has a poolpart X that belongs to pool Y" was somehow corrupted; seeing as the poolpart folder is also not showing up in Explorer with show hidden files activated and I notice there seems to be two $RECYCLE.BIN root folders being shown in WizTree my suspicion is the filesystem corruption on that disk is more extensive than just that. If the "missing" disk contains only fully backed/duplicated data, then given the other file system issues on that disk I would format that disk and if that completes okay then "Remove" the "missing" disk from the pool and re-add it from the list of non-pooled disks so that DrivePool can rebuild the poolpart from duplication / you can restore from backup. If however the "missing" disk contains non-duplicated non-backed data that you wish to recover, then I would see if you can use WizTree to copy your data out of the poolpart folder to a temporary location on a good disk before formatting/removing/adding as above, and then copying the saved data back into the pool after checking it's okay (maybe run a content comparison check between the pool and the saved data). Regarding the duplication warning, that would be referencing a different disk (as the "missing" disk isn't currently part of the pool) even if the problem may stem from the same original issue that made the disk go "missing", so would need to be tackled separately.

If you don't already have a backup of your pool, I'd recommend making one and then seeing if a chkdsk /scan /v reveals anything (if you haven't already tried that). Given it's not even working on a new empty folder I don't know what else to try; if you don't want to recreate the pool just yet (whether by manually moving the content in the poolparts or restoring from backup), I'd suggest contacting StableBit so they can troubleshoot it.

DrivePool itself doesn't care about the drive letters or mount paths of the volumes that make up a pool; if you do a bare metal reinstall of Windows and DrivePool then DrivePool should simply detect the poolparts from the previous install and recreate the pool drive. If you're using externally-powered bays for your pool, I would simply use mountvol to note which volumes are linked to which bay positions, shutdown, power the bays off, do the bare metal install of Windows 10, power them on, remove the drive letters that Windows creates for them, install DrivePool, it should recreate the pool, then you can give it the drive letter you want and recreate the mount paths for the individual volumes.

It could be the folder metadata (permissions, alternate streams, etc) have been corrupted on one or both of the drives; Windows won't necessarily pick that up. As a quick attempt at a workaround, I would try moving the folder's content into a new folder and if that works, see if you can turn on duplication for the new folder. If you can, the issue is with the old folder itself and you could just delete the old folder and rename the new one with the old one's name. If you can't, then the issue is likely a subfolder or file within the folder, which you could narrow down.

Yeah, I forgot robocopy has gotten some updates since 2011, that might be why? Disk Management's disk numbering does not have guaranteed persistence across OS or hardware changes (and references the physical storage devices, which can each contain zero or more volumes). Instead mountvol uses volume identifiers - in the format of \\?\Volume{dashed-alphanumeric-string}\ - that do have persistence even across different machines (as the volume identifiers are created with and stored in the volumes themselves). So if your current tracking method involves Disk # then I would suggest using Volume ID (and/or your own custom unique Volume Label) instead for the changeover.

I'm not aware of any way to upgrade (rather than replace) WHS2011 to W10. If you have a folder - e.g. C:\DM - in which you have junctions to various drives in your pool (e.g. due to using Disk Management to mount the paths to the volumes) and wish to copy those junctions to another drive - e.g. E:\DM - then one option is to use the following command to copy the junctions and anything else in the folder (bug: you may need to run it multiple times until all links appear) in an administrator prompt: robocopy C:\DM E:\DM /mir /sj /sl Note however that the above method will not update Disk Management with the copied junctions as mounted paths; if you want Disk Management to show the junctions as mounted paths then I suggest instead using the mountvol command to list all current volumes and their mounts, then use that output to create a batch file using mkdir and mountvol with the appropriate parameters to recreate those mount paths on the new system. You will need to run this as an Administrator.

Yes, if you're relying on Snapraid's ability to rebuild from a drive failure then you should disable Scanner evacuation in DrivePool.

One of the plugins might be responsible; does (temporarily) disabling all balancing plugins have any effect? If not, I'd suggest opening a support ticket with StableBit.

I'm... not sure? Having checked my own installs I still get the normal Notification settings but it seems like they might also be stuck in an expired trial of Cloud plus. But it wouldn't feel right that linking to the Cloud would reduce the individual functionality of the desktop app either. @Christopher (Drashna) is Bazzu85's issue "functioning as designed" or "not as planned"?

Try re-adding your email address in the app and using the Test button?

I was using Chrome when I checked. Interesting, Chrome is still good but I get your page when I try Firefox instead. Doing some digging... at least on mine, looks like ad blocking is tripping things up. Specifically, stablebit.cloud makes a call to https://stablebit.cloud/lib/sentry/bundle.min.js with a build number and "/sentry/bundle.min.js" is denied by default by uBlock origin (due to that script being in the EasyPrivacy filter list that ublock origin makes use of); permitting that script allows the page to load. stablebit.cloud also makes a call to q.stripe.com/csp-report that uBlock origin denies by default but stablebit.cloud still completes loading. So if you wish to access the site you could try disabling ad-blocking for stablebit.cloud or, if you're using ublock origin, you could use advanced filtering to specifically allow just 1st-party scripts or that script call in particular on stablebit.cloud. Pinging @Christopher (Drashna) regarding this.

Just tried, seems to be working here? You can also check https://status.stablebit.cloud/ if it happens again for you to see whether the problem is at StableBit's end.

Note that if "File placement rules respect real-time file placement limits set by the balancing plug-ins" is not checked then any file that triggers a File Placement rule - even if the rule just says "this can go to any disk" - will be ignored by OFP. Given your 2nd edit however, it looks like Ordered File Placement isn't working properly. I'd recommend opening a support ticket with StableBit.

Something to try #1: Ensure that Balance Immediately is selected, Automatic Balancing - Triggers is set to 100% / 1 GB and enable only the Duplication Space Optimizer balancer (plus Scanner is okay if you've got that). Re-balance; DSO having complete priority should get DP back on track and you can then return to your regular preferences. Something to try #2: In the GUI, from the Cog icon go to Troubleshooting then Reset all settings... and then set your preferred configuration and try #1 again. If that doesn't work, it's possible the balancing metadata for the pool might have somehow borked. At this point I'd recommend opening a support ticket with StableBit so that they can investigate/fix the problem. Alternatively, you could try replacing the pool. The following instructions presume that (1) you have a current backup in case something goes (more) wrong, (2) you don't have or don't want to use spare drives to copy your data from the problem pool to a new pool, and (3) you are not using any symlinks, junctions or third-party system-attribute content to/in the pool (if you are, you will have to resolve those appropriately): If disabled, enable hidden (but not system) folders viewing in Windows. Stop the DrivePool service and close any open programs/files in the pool. Rename the hidden poolpart.uidstring folder on each drive in the pool by prepending "old" or similar (e.g. rename "poolpart.1234" to "oldpoolpart.1234"). Start the DrivePool service. In the GUI, the drives should all show up as missing. Remove the "missing" drives until the pool is gone. Create a new replacement pool with those drives. Set up your preferred balancing, placement, duplication, etc. Stop the DrivePool service again. On each drive, move the contents of the xpoolpart folder to the newly created poolpart folder (do not move system folders - if it asks, skip them). Start the DrivePool service again. In the GUI, Manage Pool -> Re-measure and Cog Icon -> Recheck Duplication. Once you're happy that everything's showing up in the "new" pool, delete the "oldpoolpart" folders (do NOT delete the new "poolpart" folders) and optionally re-disable the hidden folders viewing in Windows. If you do that and it still didn't work, please lodge a support ticket with StableBit as something is messed up.

Checking the OFP plugin's notes, you've got the right settings. Has your DrivePool version updated between when OFP was working and when you noticed it isn't anymore?

If you've got a catch-all (i.e. "*") in your File Placement rules, remove that? Regarding SnapRAID, I don't recommend adding parity drives to a pool. Parity drives should be dedicated to providing parity.

There might be something else involved. If you open a Command Prompt as an Administrator, you can use dpcmd list-open-files with the appropriate parameters (e.g. "dpcmd list-open-files *") to see what is keeping it from being ejected. Open directories aren't usually an issue but any open files/streams can prevent ejecting. Note that this will only show files open inside the pool, not anything else that might be on the docked drives outside the pool. You could also try editing the "C:\ProgramData\StableBit DrivePool\Service\Settings.json" file to change the Override from null to true for "CoveFs_IsDiskRemovable" and reboot to see if that helps, but be aware this will affect all pools.

Yeah, to keep both read and write you'd have to go with RAID 1 (software or hardware based) to mirror a pair of drives. If your choice of RAID doesn't come with its own remote notifications but still allows per-drive SMART (e.g. Windows Pro software raid) you may wish to use StableBit's Scanner software so that if either drive dies or starts going bad it can send an email, app notification or SMS to let you/whoever know.

Just delete the old folders and remove the letters. Don't format the drives. DrivePool stores a pool's files inside a hidden "PoolPart.UID" folder (where each UID is a unique, dashed alphanumeric string) in each drive that's part of the pool, so formatting any such drive would erase that drive's hidden folder and any data in it.

No idea, sorry. If you're happy with just using the All-In-One plugin then I'd say keep going with it, otherwise you could try lodging a support ticket with StableBit regarding the weirdness with the SSD Optimizer plug in.

DrivePool works by creating hidden poolpart folders on one or more drives (e.g. in your case C and D) and pooling them as a single virtual drive (e.g. P), so if the DB needs to be kept on literally C drive you wouldn't be able to directly go "hey DrivePool duplicate C:\PointOfSale to D:\PointOfSale". You could however create a pool drive P from drives C and D, move the database to P:\PointOfSale and then in Windows create a directory symlink so the database still seems to be in C:\PointOfSale as far as your software is concerned. Potential gotchas: If you have to use a symlink because your database has to be in C:\something, some really old software doesn't work with symlinks. It's rare but something to test. You'll need to use DrivePool's real-time duplication and not its scheduled-time duplication as the latter won't duplicate in-use files, but I gather the former is what you're wanting anyway. Personally I would also make sure read striping is disabled, some old software doesn't play nice with that and I wouldn't risk it in a production environment without extensive testing first, but disabling it is as easy as unticking it in the Manage Pool -> Performance menu (if it's ticked in the first place). Note that DrivePool's response to "a drive that's part of the pool has failed" is for the affected pool to go read-only until the failed drive is replaced or at least removed , though that's easy to do. You might also want to look at backup software that supports VSS - i.e. able to take backups of files, folders or drives even when in use. Note that while VSS is not compatible with DrivePool directly it does work on poolpart folders, so if a 2x duplicated pool consisted of 2 poolpart drives then you'd only need to backup one of the poolparts.