Shane

Anything over zero isn't good. What does it display when you click on the underlined warning for each disk?

The default DrivePool balancing setting when Scanner is also installed is to evacuate any drive that Scanner detects as damaged, as a precaution to prevent possible/further loss of data. Scanner may be providing information about the reason for the damage, e.g. SMART warnings, and/or it may offer to attempt a fix, e.g. for file system issues. If it's not offering a SMART warning and it's not offering a fix, you could indeed try removing, formatting, scanning and re-adding the drives. You may find that DrivePool encounters problems removing the drives from the pool depending on the type of damage, at which point it'll tell you and you can decide how to proceed. If the problem is fixed and the drives are viewed as healthy again according to Scanner, they will be used again by DrivePool.

You can just use the pool as you normally would while DrivePool takes care of things in the background (e.g. balancing). DrivePool will "lock" (make read-only) the pool if it detects a problem (e.g. if one of the drives in the pool goes missing).

Likely very little difference versus plugged directly into the motherboard. It is possible to evacuate/move files much faster if you don't mind stopping the DrivePool service while you manually move them yourself (from hidden poolpart to hidden poolpart) then restarting the service and requesting a re-measure. Basically a tradeoff between speed and comfort, if that makes sense.

I think I'd suggest making a support request.

For requesting the developers add a feature, you can use the Contact form.

My initial suspicions to check would be: faulty USB device, faulty or overloaded USB port/chip, faulty or underpowered PSU.

Honestly don't know; I was hoping to find some time to create a testbed and experiment using Local Disk providers as a stand-in (since I can toggle the VM volume read-only and see what happens) but this past week has been hectic and I needed sleep more - and I still couldn't be sure that Local Disk == Google Drive in terms of provider behaviour. If I had to guess the potential outcomes it would be similar to unexpectedly losing the connection? Frankly I'd suggest finishing moving away before the deadline arrives or ensuring you have duplication/backups elsewhere; at the very least I'd suggest don't have anything in the upload queue when the date arrives and mark the drive read-only yourself beforehand.

If you're simply wanting to keep the data that's already in your pool, just Add the new drive first then Remove the old drive second; DrivePool will automatically move the data to whatever drive(s) has the most free space (so most likely your new drive) as part of the process. If it turns out there isn't enough room on the remaining drive(s) it'll just stop at that point, you won't lose anything. VapechiK's method above is for if you want to move files from outside your pool to inside your pool as absolutely quickly as possible when the drive(s) those files are on are going to be added to the pool, and can also be used (with some changes) if you want to move data from an old pool drive to a new pool drive for the same reason (the Remove function is slower since it has to keep all of the pool's features going while moving the data in the background). TLDR: if you're not in a rush, Add the new drive first then Remove the old drive second, DrivePool will take care of moving your pooled data and you can keep using your pool for other things while it does it.

Does uninstalling then reinstalling DrivePool help at all? If it doesn't, I'd suggest requesting help via the Contact form if you haven't already.

No info, sorry. Someone mentioned a similar problem though, are you also using Windows 11? And is it happening every time your PC restarts? If I'm remembering correctly, their's seemed to be related to a Windows update.

Are you using Microsoft Remote Desktop? If so, have you tried changing the color depth or performance options? Are you using latest graphics driver? Any change if you close and re-open the DrivePool GUI?

While a SATA cable plugged directly into a SATA controller can in theory support a 6 Gb/s transfer rate (before overhead), the transfer rate on a mechanical drive isn't likely to come even close - e.g. a 16TB WD Red Pro's ideal sequential read rate benches a little over 2 Gb/s - and that can drop way down if the drive is being asked to pull many small files non-sequentially (as little as 0.1 Gb/s or less in certain scenarios). If you've an external enclosure doing SATA to USB, the USB connection can be a bottleneck as well. That said, DrivePool is sluggish in evacuating drives; AFAICT it methodically removes each file before starting the next with no queueing optimisation, so it taking noticeably longer than it would take for you to do a bulk move of the contents yourself wouldn't surprise me.

Could it be a lack of contiguous free space? You may have 800GB free total, but the limit for any single incoming file still can't be bigger than the largest amount of free space on any single given volume in the pool (e.g. if you had eight drives in the pool that 800GB might be made up of 50+50+50+50+100+100+100+300GB). Could it be running into the error because it's attempting to pre-allocate space for multiple incoming files at the same time? E.g. if this Sonarr is telling DrivePool to allocate room for twenty incoming files of 7GB each simultaneously and the largest contiguous free space available is less than 140GB then there'd be an error because DrivePool defaults to choosing the poolpart with the most free space at the time but it won't be able to simultaneously fit all twenty there. Could the Sonarr software be mistakenly doing some sort of percentage checking? 800GB of 83TB is less than 1% free... (note too that if you're using duplication, 800GB free is more like 400GB free or less)

That would explain it; DrivePool creates pools with default security settings that prevent guest/anonymous access.

Hmm. I've just installed Solid Explorer on my android phone and tested adding a LAN/SMB cloud connection with username/password access to my pool machine; I was able to access the pool and non-pool shares on it (including a share of the pool drive itself) without issues. Do you have a Windows PC you can use to test re accessing the pool and non-pool shares to see if that has the same problem?

I'd suggest comparing the share permissions and security permissions of the pool and non-pool folders to see if there's any difference?

Maybe check in Windows Disk Management just to make sure (if you haven't already)? Also, what do you see when expanding the drive's entry in Scanner (via the plus sign and then via the drop arrow for File system health)?

I'd expect it to (eventually) have all duplicated files have one of the duplicates on the new drive, yes. Though I'd still recommend putting the Scanner balancer as highest priority.

You can plug a Storage Spaces array into a DrivePool pool as if the array were a normal drive, no problem. It's trying to convert a Storage Spaces array back into separate drives that can't be done non-destructively (nor non-painfully, in my experience):

Unless you can get a direct answer from Google, I'd err on the side of caution that when Google says "read only" they are including disabling edits to existing files (e.g. CloudDrive containers).

Does the drive contain any non-Windows partitions?

You'd only need it to move it if there's an active balancer between it and Scanner. Inactive (greyed out) balancers don't count.

It can be fiddly but as long as they're on the same subnet then yes; see https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Remote Control Details - Scanner has the same file in C:\Program Files (x86)\StableBit\Scanner\Service instead. TLDR: Your user account that is connecting must also be a user on the remote computer, and that user must be part of the built-in Administrators group. Make sure both machines are running the same version of DrivePool/Scanner. Make sure the Remote Control option is ticked in the Cog icon settings menu of DrivePool on both machines, and in the Settings->Scanner settings for Scanner likewise. Make a copy of the RemoteControl.default.xml file in the relevant folders to Remotecontrol.xml in the same folder (it shouldn't matter but don't mix Scanner and DrivePool). You'll need Administrator access to do this. Restart the DrivePool and Scanner services on both machines and launch the relevant GUI. You should see your machine's name up the top of the GUI, click it to see if the other one has shown up. You may have to wait a little while and try again. If the remote machine doesn't get discovered even after waiting, you can try editing the RemoteControl.xml file in the local folder to manually add the hostname or IPv4 address of the remote machine then restart the services again (note: a machine may then show up multiple times in the connection box, I think because once it's manually visible it can become discoverable as well). It can be tricky editing the file in its usual folder; alternatively move the file to your Desktop, edit/save it there, then move it back.

When intending to remove multiple drives I strongly recommend using the Drive Usage Limiter balancer (make sure it has priority over everything else except optionally the StableBit Scanner balancer if the latter is present) to empty all of the drives you wish to get rid of before you proceed to Remove them. While the latter is able to queue multiple drives for removal that function currently operates dumbly and may evacuate each drive to other drives waiting in the queue - so it can potentially waste enormous amounts of time and bandwidth. As far as speeding up the automatic balancing itself, there's not really a way to make that go faster other than clicking on the Increase priority double-arrows adjacent to the Pool Organization bar if they're present (IMO it makes little difference if the pool is otherwise not in use but YMMV); for quicker results you'd have to turn balancing off and manually copy/move the data between the hidden poolparts in parallel yourself (being careful to avoid "crossing the streams" so to speak - it's safe if you know what you're doing but you're still proceeding at your own risk) and then perform a Re-measure afterwards.