Leaderboard

StableBit have very promply got back to me and said you can do it via Powershell and specifically this command: Set-Disk -Number X -isReadOnly $true They will also pass on my RFE to the developer for consideration.

No worries! Sometimes, internet stuff .... But glad that we got it sorted.

Issue Resolved Steps Taken (for anyone else who may run into this issue) Uninstalled DrivePool (*backup License key if needed) Rebooted System Reinstall DrivePool Removed drive from pool (*backup or move data from pool directory on drive to root if needed) Recreated Pool The last two steps maybe all that is needed, but I wanted to list all the steps that I took. Note: Uninstalling DrivePool does not destroy the data in the Pool and the Pool will automatically detected on reinstall, making this process non-destructive. Interesting observation: An alternative method, not recommended, would have been to create a second pool using the first pool as a drive. Even though the drive was detected incorrectly on the first pool, the storage space matched the drive size correctly when added to the second pool. Unfortunately, and obviously, this is not an ideal solution as it creates unneeded layers of complexity and points of possible failure going forward.

I've done this before without issue. Here's a post that describes the process;

Thanks for answering @shane. Turns out I had a disk that was failing and needed to pull it from the pool and replace it. Support helped me through the process and the software worked exactly as it should have. Victory!