OK… I thought I’d just make a couple of comments since I’ve dug into this device for a while.
I immediately updated the firmware when I got the 2TB MyCloud and started fiddling via SSH and sure enough I ran into this Bug From **bleep**, where you can’t log into the control panel. The only thing that fixed it was a total, hard reset (power down, hold the reset button down, power back up). I was really grateful for this forum when it happened.
It’'s a bug, and it looks like a REALLY nasty one and I’m not a bit surprised WD hasn’t been able to fix it yet. From what little observation I was able to make I think there may even be a << shudder… >> timing problem. If somebody could come up with a reproducible test case that will cause it I bet WD would give them a free NAS for a reward.
I haven’t had it again (fingering a crucifix here) and it didn’t cause any data loss.
Something else is… I wouldn’t dream of trying to use this thing on a LAN, without a static IP address. It just isn’t the type of device for which that’s safe *because* there are *other devices* on the LAN that are counting on it being somewhere predictable. Dynamic IP addresses are fine for laptops or stuff which just comes and goes anyway, but NOT for something like this device. (IMNTBHO…)
I turned off the “sleep” function for similar reasons - other stuff on the nutwork is counting on it being there and is going to get its feelings hurt when it can’t find it. YMMV but I’m leaving it on, and if that means a few polar bears have to learn to swim, so be it… (There’s a reliability issue there too… in most cases electronic devices will fail sooner if they’re constantly powered up and down than if they’re left on.)
Finally… in general I think I would turn OFF everything you can, to start with, and then selectively turn stuff back ON and get the various “Features” working one at a time. I learned that the hard way when I built my first Debian system and selected everything from the kitchen sink driver to the girlfriend stimulator for the build, and it’s a lot harder going back in and disabling things to find out who interacting with what is causing which crash, than it is to just gradually install or turn stuff on. But YMMV…