I also got a little brave/creative/foolish and had the thought that maybe I could kick off the duplication process on P manually via command line since the GUI wouldn't come up and it wasn't duplicating on it's own from the nightly job.
So I did a dpcmd check-pool-fileparts P:\ 1 which completed successfully. When I checked F in clouddrive, the usage has increased and there's 1TB+ queued. So it looks like it's duplicating. That's one good thing so far!
The detach was successful. I had to do a reboot between the detach and the re-attach. However when I re-attached F, the configuration screen came up, I selected another physical drive on which to put the cache. That was some time ago and it has not yet appeared in the GUI. I believe it's adding it, but maybe very slowly, as the Clouddrive app is using about 40% of the CPU. The other detached clouddrives (formerly M & K) are visible in the GUI but have lost their drive letters. Also the Drivepool GUI will not come up, though I have access to all the lettered drives via windows explorer and command prompt.
I guess I'll give it overnight and hope that F: gets re-attached and that is the cause of the Drivepool GUI not responding.
dan66215 got a reaction from Shane in Unable to remove clouddrive(s) from a drivepool because I lost write access