Viktor

I changed the pool service to delayed start some time ago (wanted to separate the starts of CloudDrive and DrivePool). Works fine, no problems so far.

The current Windows Version has automount disabled per default. This means drives without assigned drive letters are not mounted at system start and DrivePool will not recognize them. But you can fix that by enabling automount: http://wiki.covecube.com/StableBit_DrivePool_F3540.

Check the Autostart tab of the Task-Manager. It should have an activated entry “StableBit DrivePool Notifications”.
If its status is deactivated, then you need to toggle it to activated.
If the entry is completely missing, you should repair the DrivePool installation or reinstall.
If the entry is there and active, but no process is running, then something is preventing it from running, most likely a virus protection software, or it’s crashing for some other reason. In that case you maybe find some details in the event logs or the virus protection logs.

The root folder is called "StableBit CloudDrive". If you only renamed that folder, just give it that default name again.
 
The entire (Google Drive) StableBit folder structure looks like this:
\StableBit CloudDrive\CloudPart-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx\xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-CONTENT(-ATTACHMENT,-METADATA)
The "xxxx..." string is a placeholder for the global unique id in hex code (e.g. abcdef01-abc1-def2-1234-12345abcd67f).
All files inside the folders on Google Drive have that id in their name and you will find it also in the cache folder's name on your local machine (e.g. \CloudPart-abcdef01-abc1-def2-1234-12345abcd67f).

 

That’s exactly what I see too with Google drives – frequent “pinning data” phases with extreme CPU loads. Unclear, why pinning needs to be performed at all. Neither directories nor metadata are being changed on any drive. One drive is only downloading (being scanned for Crashplan backup). The pinned data volume suddenly gets reduced by a certain amount (e.g. 200 MB), what then triggers such a pinning phase and lets the entire system freeze almost completely for a couple of minutes – that happens multiple times a day.

I installed the latest version 3 days ago and haven’t seen this notification anymore so far.

You don't even need folder mount points for drives in a pool. DP can handle completely unmounted drives. You can also add, remove or change a drive's letter or mount folder any time before or after having it added to a pool. 

When I recently saw this issue, I created a ticket and provided a couple of affected chunk files. Now I did some further investigations and identified what these files have in common:

It’s the first two characters. All my affected files start with “P1â€, “P2â€, “P3â€, “P4â€, “P5â€, “P6†or “P7â€. The rest of the file does not matter and the issue is not restricted to chunk files. It applies to any file, even to ordinary text files, which start with such a header (when I upload a .txt file to ACD with something like “P1 bla bla …â€, it shows up under “Photos & Videos†with “Could not Displayâ€).

I finally found the reason, why ACD identifies these seven two-byte strings as picture headers: These strings (P1, P2, … P7) are the seven magic numbers of the Netbpm format (portable anymap format).
Maybe this help to develop a solution.