So I upgraded to the 4.00 firmware, from whatever the last 3.x release was. The only reason I did this is because there were SOO many problems with the old firmware, resulting in me being unable to access content from my Android devices more often than not, along with connectivity issues that I actually had to write a script to work around, they were so bad. I had this silly hope that maybe this firmware would be better.
Well, it actually is. HOWEVER, it also **bleep**. I use Linux, and as such, with jack for WD support (even though they run their box on Linux, which rankles a bit) I explored other alternatives to keep things in sync between my two desktops, my laptop, and my new shiney magic box. I found Unison, and have been playing with that for a couple of weeks. Works well, although with the amount of data I have, it appears to be ungodly slow. I’m hoping that’s only for the initial runs to sync everything up, but I guess we’ll see.
Ever since updating the firmware, I’m unable to use unison via ssh. I have to physically mount the MyCloud to my computer (can’t use NFS either, since there’s no way to access password protected data, and Samba is just a mess of errors, so I’m down to using sshfs, which slows things up with encryption) and run unison from my local machine as if it’s just syncing two local files. This is doable, but annoying.
When I ssh into the MyCloud device and try to run Unison directly, even just unison -version, I get the message “Killed” almost instantly. I decided I’d try out btsync and see how it works. Found that it gets the same message. I’ve looked through dmesg, and various other system logs, and can find NO reason whatever why these processes are being killed. I also find no mention of the system killing them. I’m left to conclude, since this didn’t happen before, that Western Digital changed something on the system with the latest upgrade to actually force-kill application based on some sort of logic.
I need this to stop. Since Western Digital can’t be bothererd to provide software for use of their product with Linux systems, I would think at a minimum they would be nice enough to not actively screw people that are trying to use their stuff with a *nix environment, but I guess you’d be wrong. I’m about a minute away from just blowing away the software on the box entirely and creating my own install of everything I need to run it as a stand alone NAS Server without any WD funk. The only problem is the amount of time it might take me to hunt down drivers and such, assuming they used proprietary code, which I’m nearly certain of.
Anyone have some suggestions for me? I’m at a loss as far as where to look, and what to try to find, in order to kill whatever process it is that’s killing my processes, and right now, keeping things in sync is a bloody nightware for me. NOT what I wanted when I bought this thing, at all.