Disclaimer: This post assumes you’re comfortable with SSH’ng into your MyCloud and creating/editing files.
The info in this post doesn’t alter stock MyCloud functionality so I think it won’t void your warranty but I don’t really know.
I’m using a MyCloud as an offsite backup device.
It connects to the office via OpenVPN (as outlined in this post). It’s been great, steadfastly reconnecting no matter what.
After a couple of months, my custom OpenVPN connection stops trying to connect.
Rebooting puts things right again.
Until I solve that problem, I’m opting to reboot MyCloud on a schedule.
Scheduling a reboot is not hard to do. I just had to create a new cron job file in /etc/cron.d/
The following command will create a cron file to reboot the drive daily at 5:30a.
echo "30 5 * * * root /sbin/shutdown -r now" > /etc/cron.d/dailyreboot
The only hitch was I had to set the file permissons on the cron file to 644 before cron would run the job.
chmod 644 /etc/cron.d/dailyreboot
My other cron files run reliably with perms set to 754. I don’t know why this had to be 644.
It was another Debian user with the same issue that pointed me to the soluiton.
Thanks (for a place to post this stuff).