For some strange reason, my WDMC is so busy that nothing works and I can’t connect a drive to it or even access the admin panel. Well, not a very useful machine right there.
I could unplug the power and restart it - except I dislike a hard restart - I can hear the drives spinning…
It is possible to restart the machine via SSH when this is the only possibility of logging on.
Start a SSH session and then enter “reboot” or “shutdown -r”.
As benner writes below: “The proper command (when logged into SSH) to do an immediate shutdown and reboot is: “/sbin/shutdown -r now”. Or one can shutdown and power off by issuing the command “/sbin/shutdown -h -P now”, or by issuing the command “/sbin/poweroff”.”
Voila. This restarted the server and got the Web admin UI back in place.
One reason why the WD My Cloud UI becomes unresponsive or slow is scanning and cataloging media (pictures, video, music) files. If you have a large amount of media files it is not unheard of for the WD My Cloud to take hours (sometimes days) to scan and catalogue all the files. This media scanning/cataloging may potentially happen every time you boot or restart the WD My Cloud. One solution is to stop the “/etc/init.d/wdmcserverd” and “/etc/init.d/wdphotodbmergerd” services. See this link for more information on how to disable those two services.
On the issue of issuing SSH commands to reboot, shutdown and reboot, or simply shutdown, there are previous threads discussing various ways to issue commands via batch files and scripts via SSH to control WD My Cloud actions. I use a a batch file (.bat) and an app (the free SSH Button) on my Android smartphone to send SSH commands to the WD My Cloud to shut it down when I don’t plan on using it for a long period of time.
The proper command (when logged into SSH) to do an immediate shutdown and reboot is: “/sbin/shutdown -r now”. Or one can shutdown and power off by issuing the command “/sbin/shutdown -h -P now”, or by issuing the command “/sbin/poweroff”.
From eading various threads here and looking at the CPU usage it seemed that it was a scan that was rendering it unresponsive. As of yet, I will try to not stop those services and see if they complete their work. I did notice that the issue appeared right after the first connect to the server from an external point with an iPad - I’m guessing that kicked off the scan.
I’ll look into an SSH app for my phone, that sounds like a good idea.
Thanks for the details on the proper command - I’ll try to edit my op to reflect that.
I’m no expert by any means but it is my understanding, depending on the device, the “halt” command, the “shutdown” command and the “poweroff” command may perform essentially the same action of turning the device off. In the past the “shutdown” command would try to shutdown the system gracefully where as the “halt” command would simply stop the CPU cold and not shut down the system gracefully. On certain devices the “halt” command may not trigger the device to power off where as the “shutdown” command and “poweroff” command should.
