MCROMMERT2

Wondering if anyone had any ideas. I had implemented a symbolic link of a folder on my clouddrive to my drivepool. I use this so plex can easily just search one drive and i can do the initial metadata and analyzing on a local drive before it moves to the cloud drive. It worked fine till i had some issues with clouddrive slamming reads on my drives and i updated to the newest drivepool beta and also reset ntfs attributes. I have reowned the pool and set correct attributions but plex can play video fine from the symbolic links but scanning it doesn't see them at all Just wondering if anyone would have any ideas. Double post please delete

If this helps at all...definitely confirmed that the drives were running constantly and task manager was giving an accurate reading...I had two drives that had gotten to 114 on scanner because of the issue...after a day of being fixed (clouddrive is disabled for now) my hottest drive is 100.4 f

Okay unmounted my cloud drive after rebooting...doesn't stop the disk usage I then uninstalled clouddrive...after the service stopped and was removed the usage stopped Reinstalled clouddrive - immediately before any drive was mounted the usage started up again Any suggestion? Anyway to do a clean install so all settings are gone? EDIT: This issue on drivepool also affect clouddrive? I mean its a little strange how my issue is exactly the same...even the same 8.2/8.3 kb/s read on the drive at the same interval

The drives that were being kept alive were all 8 drives in my drivepool pool. In exactly the same way they were being read from for a half second every 3 seconds at 8.3 KB/s (it was always exactly the same in task manager). I realized looking at task manager that my cloud drive build with your stablebit clouddrive had exactly the same behavior in task manager. When i killed the service that drive dissapeared (of course) and all of the other 8 drives stopped their regular reads and started acting normal. I don't understand why cloud drive would be interacting with these drives at all...the cache for cloud drive is on my main ssd which is not one of the drives in question and the cloud drive is not a member of my drivepool. Detaching the drives did not help..when they were reattached they started the behavior again. I have not yet rebooted my computer since disabling cloud drive

Okay so this is going to sound weird, but its definitely the culprit...uninstalled scanner...no change Killed clouddrive's service...immediate stop to the accessing...cloud drive is storing no files on these harddrives so i'm at a loss...its only using my main ssd not any of the the 28tb in my storage pool (all spinning drives) Would love anyone's ideas on this

uninstalled Stablebit drivepool...no difference...scanner is next

In other interesting news...my d: drive (which is my clouddrive) is doing the exact same thing...8.3 KB/s blip every 2-3 seconds

Okay installed new update Checked the file and for the .default. file it didn't pull from what i had put...it was set to true changed the file...renamed back to non default...rebooted service Didn't even rewrite .default. - Still lots of 8.2 KB/s reads I'm having other issues with other programs...might be write time to reinstall windows

will do...where are these updates? main page still has old beta

Definitely doing that...the strange thing is when i restart the service...it never rebuilds the drivepool.service.exe.default.config from the config file...that file never returns...even after a reboot Perhaps an uninstall and reinstall could fix it?

Everything is on....queries are throttled to once an hour...everything checked on the S.M.A.R.T. page

Okay i'm using balancing like this Until today when i noticed the problem i had it on immediate rebalance I'm on windows 10 64bit...newest stable fully updated (creators update) The version is the newest beta 2.2.0.651 I also have stablebit scanner and cloud drive installed and running cloud drive is not being used in drivepool

Thanks for the quick response zipped up the logs for you. The drive is letter g:/

Made the change...rebooted system after rebooting the service didnt do anything Still hitting drive over and over and over again

How is this still an issue? I have the same problem and now wondering if this has been causing the high temperature issues i have had with my drives for a long time. What is causing this issue? Will try the config file change.