So my drive has been ticking for the last week or so making me think that it is still doing its scans and it seems that this slow ticking is just another unknown WD process but it made me do a final look over on how I can, once and for all, force a gen2 cloud to sleep.
I know that all of this is not new to everyone here but I found that if you do kill the scan processes after you turn on Cloud Access, you can effectively keep them off even with remote cloud access until you reboot the cloud or when you toggle Cloud access off and then on. You will still have remote cloud access without the scans that takes weeks to complete.
Thus after turning on Cloud Access… type or put them all in a script and run
With cron turned off your cloud won’t wake up at various hours during the day. You will need to redo the commands if you restart cloud access.
I’ve noticed that if you do copy new data over to the cloud, the cloud will wake up more frequently and if I remember correctly this is due to monitorio.sh noticing the change in your HD size and attempts to invoke the scans.
Anyways, the above 3 commands will provide your cloud a better night sleep even if your cloud has completed its scans. I’ve had the cron off for a better part of a year without any side effects and you can reboot the drive to restart the corn monthly to rotate the logs, clean out any tmp files and so on.
I’ll get to the bottom of this ticking as I’m fairly sure that it is a service that needs killing. Now that my backup non remote access cloud is exhibiting the same symptoms of clicking, I am just annoyed at WD for adding another level of unnecessary irritation.