Shane

My Windows 7 test PC had no issue opening your website as "secure" in the URL via both Firefox and Chrome, so perhaps you've already fixed it. On the other hand it also blocked a lot of third-party objects (probably advertising trackers?).

Usually there'll be an "X" button to the right of the animated yellow bar that can be used to abort any active operation. Then you could restart the duplicating from the Cog icon -> Troubleshooting -> Recheck duplication. If you hover the mouse cursor over the "Duplicating... (17.2%)" does it display anything informative?

Yes, it'd be the Ordered File Placement balancer (or cjmanca's All In One balancer, which is what I'm currently using instead of multiple others). My programming ability (such as it is) would be enough that I could write a brute-force shell script to organise the pool as needed on a manual/scheduled basis, but an actual balancer plugin would obviously be far superior.

You should keep the parity drive completely separate. Using it for anything else risks the space usable for parity data becoming less than the space used for content data on one of the protected drives. Don't add it to the pool. EDIT: Though if you mean "can I mount the parity drive as a folder rather than using a drive letter", if SnapRAID lets you do that then sure. You just don't want to use the parity drive for anything except parity data.

I can see the advantages. It's not an available option in the current DrivePool version, though I'd imagine it should be possible to add as (or to) a balancer plugin. How does mergerfs/epmfs handle the situation where the file being written doesn't fit in the remaining space of the chosen drive (because you can't guarantee in advance the size of an incoming file)?

It might be possible, but it would get complicated fast if you made use of different levels of duplication in a pool (e.g. if you had a pool where you set duplication x3 for critical folders, x2 for most folders, and x1 (off) for trash folders).

According to your screenshot, there aren't any duplicated files. So yeah, that's odd? If duplication is actually turned off, then DrivePool GUI -> Manage Pool -> File Protection -> Pool file duplication... should be offering to enable it. If it is instead offering to Disable Duplication, then you should click that that to turn off duplication.

Hi, if you're not using drive letters I'd imagine you'd point SnapRAID at the individual hidden drive folders that make up the pool, and you'd want to dedicate (one of) the biggest drive(s) entirely to parity. You shouldn't need to shrink the partitions on the other drives. Remember to turn off automatic balancing on DrivePool to reduce SnapRAID's workload.

I'd imagine it'd depend on there being enough interest? Some of the existing language support has been done via community translations, so if you're willing to help out with that you could use the contact form to offer such to Stablebit?

A note of caution: if you're using caching software to defer writes, then in the event of a crash or power failure you WILL lose any data that hasn't yet been written to the disk. It's not likely to be a problem, at least if you've got a UPS and/or a stable setup, but it's still something you should take into consideration.

As you mentioned, the simplest method is to physically disconnect the drive or take it offline via Windows Disk Management; both will result in DrivePool noticing the disk is missing, allowing you to Remove it without affecting the files - however if you don't rename or remove the poolpart folder (a "hidden" folder on the drive) before reconnecting/onlining the drive again it may be rejoined to the pool. To pre-empt that issue, you can either rename the poolpart folder before disconnecting/offlining the drive (though this may not be possible if there are any open file handles*) or you can open a command prompt as an administrator and enter the following command: dpcmd ignore-poolpart pooldriveletter poolpartfoldername where pooldriveletter is the drive letter (including the colon) of the pool - not the poolpart - and poolpartfoldername is the name of the poolpart folder that is on the drive you wish to remove. This will "tag" the poolpart folder so that DrivePool will immediately disconnect the poolpart and also ignore it in future. For example: dpcmd ignore-poolpart k: PoolPart.9be9560f-2871-4c99-9722-7269f0250cfa * the commands dpcmd list-open-files and dpcmd force-close-open-files can be useful for dealing with this. Just a reminder that if you are using SnapRAID with a pool, generally you should turn off balancing for that pool (to prevent DrivePool moving files between volumes).

@srcrist @Thronic Both of you have made valid points concerning the pros/cons of CloudDrive, rClone and cloud storage. However, unless specific information is still needed, I suggest this topic has been "sufficiently covered".

It requires a separate SSD volume per pool. Note the use of the word "volume" - you could use the same physical SSD for multiple pools by partitioning it into multiple volumes and adding each volume to a different pool, although you'd then have less SSD space available for each individual pool.

From what I can figure out from trawling the manual and changelogs: CoveFs_WaitForVolumesOnMountMs (Default: "10000") - How long to wait for all the volumes to arrive in MS. This is usually for older pools (pools that don't initially know how many poolparts they should be waiting for). DrivePool will wait at most this long between detecting the first poolpart folder and mounting the corresponding pool drive. CoveFs_WaitForKnownPoolPartsOnMountMs (Default: "10000") - (Newer pools may be aware of it's parts) If a pool is aware of how many pool parts it's made of, at mount time, it will wait for all of those pool parts to arrive before allowing the OS to finish mounting the pool. This is usually for newer pools (pools that do initially know how many poolparts they should be waiting for). DrivePool will wait at most this long for those poolparts to finish being detected before mounting the corresponding pool drive. CoveFs_WaitForPoolsAndPoolPartsAfterMountMs (Default: "10000") - How long the service will wait for all of the detected pools to finish mounting, and then for all of the known pool parts to get recognized on those pools. This is for all pools, and is how long DrivePool will wait at most for all pools to complete mounting and all known poolparts to be recognised before starting other DrivePool processes such as missing disk detection, file duplication, balancing, user notifications, etc. Appparently this also particularly helps with Bitlocker drives. So in your case I think maybe increase the first two to something a little larger and the last one to at least as large as the first two? E.g. 15000, 15000, 15000, or maybe 20000, 20000, 30000? The minimums will depend on your system.

I think I see what you're getting at; you need to take advantage of DrivePool's ability to nest pools. I.e. you would create a Pool A using your local drive(s), a Pool B using your cloud drive(s), create a third Pool C using Pools A and B as "drives" and turn on duplication for all of Pool C. The result is that anything stored in Pool C will always have at least one copy locally (kept in a hidden folder in Pool A) and one copy in the cloud (kept in a hidden folder in Pool B). If you also wanted to have multiple copies locally you would then turn on duplication for Pool A, or at least for the Pool C's hidden folder in Pool A. And so on and so forth.

Hmm. DrivePool reporting the wrong size (which it retrieves from Windows) shouldn't affect SnapRaid (which also gets it from Windows) unless Windows itself is giving the wrong size to both? In the Windows Disk Management utility, can you set View->Top->Disk and View->Bottom->Graphical then screenshot it so we can see all of the relevant data for those disks? Particularly the Disk Number, Capacity, Unallocated Space and Partition Style in the top section versus the Disk Number, Disk Size, Volume Label/Letter and Volume Size in the bottom section.

It's not due to DrivePool. Notice that the "Capacity" column in Windows Disk Management is still reporting 3071.98 GB; the volume's file system was not properly updated by the utility that resized the partition. Assuming that's all that it didn't do properly (if not, hopefully you have backups) you can try the following fix: Open a Command Prompt as an Administrator Enter the command "DISKPART" Enter the command "LIST VOLUME" Enter the command "SELECT VOLUME #" where "#" is replaced with the relevant volume number Enter the command "EXTEND FILESYSTEM" Enter the command "EXIT" Close the Command Prompt. You might then need to restart/remeasure DrivePool for it to see the corrected file system.

If the drive is still in the pool and it's just not recognising the new size, have you tried "Manage Pool" -> "Re-measure..." ?

Short answer is that - so long as you're disconnecting ALL of the drives in a pool - yes you can and it shouldn't cause any problems as far as DrivePool itself is concerned. Slightly longer answer is that you would stop the StableBit DrivePool Service* while disconnecting/reconnecting, to avoid DrivePool briefly** complaining about missing drives and to avoid it potentially re-scanning the entire pool when the drives are reconnected, but the software is designed to "fail safely" so even that wouldn't be strictly necessary if you were ever in a rush. Do make sure that all drives in the pool are set for "Quick removal": this should be the default for USB HDDs, and can be found in Windows Disk Management; right-click each disk in the pool - e.g. you'd click where it says "Disk 9" and not where it says "volume label xyz (drive letter)" - and then select Properties and then select the Policies tab. *DrivePool basically operates on three layers: the file system driver (handles the low-level code that makes the pool visible as a drive to Windows), the drivepool service (handles all the balancing and maintenance), and the drivepool gui (lets the user see what's going on and create/configure/remove pools). **if you disconnect all drives that form a pool, DrivePool will no longer know that pool exists until you reconnect at least one of those drives.

If you hover the mouse curse over the Pool Organization bar, does it show a tooltip indicating what is currently doing? E.g. moving files or building bucket lists? (and yes, sometimes when it decides to build bucket lists it can take AGES to finish and get back to moving files; you can either let it do its thing, try fiddling with the balancing settings and restarting the balancing, or move the files yourself manually)

The intended purpose of the "SSD" drives in both balancers is use as a temporary cache, not as a permanent storage area; when the "Automatic balancing" is triggered for this cache, it WILL attempt to move ALL files off the "SSD" drives to the "Archive" drives to free up space for the caching of new incoming files. If what you actually want is to keep duplicated files on specific drives and unduplicated files on specific other drives, then I'd suggest you should be marking all of those drives as "Archive" and then using the following: the "Folders" tab under the "File Placement" tab to select which drives each folder should be using (since duplication can be set per-folder) OR "Ordered placement options" to assign priority to the drives accordingly (un-ticking "Same order as duplicated" and telling it which drives you want prioritised for un-duplicated vs which drives for duplicated files). You could even use both if you wanted especially fine-grained control, e.g. if you wanted folder A to use drives X, Y and Z in that priority, but it could end up being fiddly to manage.

Good to hear. Once everything else is sorted out, if you still can't find the source of the "Other" files then feel free to post here and we'll follow up.

Hi, yes, x1 means no duplication. Welcome to DrivePool, hope you enjoy using it!

A1: I'm not familiar with the Pace 5268A (or any other AT&T routers), sorry. Different country! In theory, generally, it should be possible to have router "A" handling internet traffic while router "B" handles local traffic without them fighting about it; in practice some routers are (much) less capable than others and some ISPs also lock down the functionality of routers they provide / mandate. For whatever it's worth, here's an example very basic setup: Internet <-> [WAN port] Router A [LAN port] <-> [LAN port] Router B [LAN port(s) and Wifi] <-> Local devices Router A (WAN DHCP on + LAN DHCP off) is configured to receive the necessary WAN addresses from the ISP but to not manage the local devices. Router B (WAN DHCP off + LAN DHCP on) is configured to deliver the necessary IP configurations so local devices use Router A as the internet gateway. Obviously this is a simplified summary and you'd need to get all the fiddly parts lined up, but that's my day job not my forum job. A2: As a general rule of thumb you want to minimise the number of wifi devices (including stations) operating in any given area, and another is that you want all devices operating on any given channel to support the same wifi standards (e.g. if a gen 1 device and a gen 2 device are sharing the same channel, you may end up with the gen 2 device limited to gen 1 capability). That said, if your plan is to have Router A handling wired traffic while Router B handles wireless traffic, that might work for you. A3: The new Beta functionality mostly relates to supporting Stablebit Cloud connectivity, but the changelog indicates there was work done on DrivePool functionality too. The great thing is you can install the Beta and if it doesn't help you can uninstall it and reinstall the Stable release without losing anything. Resource Manager is built into Windows and can be used to monitor a variety of metrics including file access/throughput.

I'd just happened to check the forum and saw your post before going to bed, that's all. 1. Your screenshot indicates that DrivePool is stating the following about the folder you've named "Duplicated": Its files may be placed on E, F or G drives. E currently has 698 GB free. F currently has 856 GB free. G currently has 856 GB free. 18.7 GB of files are currently placed on E. 18.7 GB of files are currently placed on F. Nothing in the folder is placed on G (when nothing relevant is placed on a drive, that drive won't be shown in the "how much is placed where" section of File placement) If the size of your Duplicated folder is also 18.7 GB according to Windows Explorer, then I'd presume DrivePool is correctly measuring the size (since 18.7 x 2 = default x2 duplication). With the amount of free space it is reporting on all drives being so much larger than the amount of duplicated content, I would believe DrivePool simply hasn't seen a need to use G yet. However, you might also want to check the settings in the Drive Usage Limiter balancer (since you have it enabled) to ensure that it is allowing use of G for duplicated content. 2. That's the Manage Pool triangle, not the Pool Organization bar triangle. There's a screenshot and further information in the manual here (link).