Bear in mind this is a work-around. Me and you don’t yet know what is causing that log file to explode in size so you will need to keep an eye on it. Maybe every day you may have to erase it. The RAMLOG only has 20Mb allocated to it. Once that fills it disables itself so the log files get written directly to disc. This is where the MBL will stop going into standby mode with the green LED constantly flashing as the log file grows. Finally the system partition gets full-up and other services will begin to malfunction.
I don’t have this problem because of two reasons. I do not have any equipment manufactured by Apple on my network ans also I have stopped the AppleTalk networking service on my MyBook Live because I simply do not need it.
Western Digital sort of disagree with what I’ve done but to me stopping AppleTalk (netatalk) make things simpler. Why have a protocol handler turned on when it’ll won’t be used? If I want and need to use it I’ll simply turn that service on.
If RAMLOG fills up past 20Mb then you need to clear-up the log files and restart the ramlog and/or reboot your MyBook Live.
Best way to find out is using the . . .
df -h
. . . command.
Mine is currently showing 57% full. I keep an eye on it and if it gets to about 90% full then I’m manually clearing out the log files. What I’ll do is use W.D.'s own facility to download all the log files to my computer and then I’ll do some log file pruning.
Another option is to adjust the cron configuration to perform log files clean-up procedure more than once every 24 hours.
I don’t want to start changing stuff within the NAS’s system partition in case it breaks any future firmware upgrade so right now I’m happy just to keep an eye on things and manually make adjustments as and how necessary.
Here lies a problem. Is SSH is enabled then one has full access to the MyBook Live’s internals and problems can either be fixed or a temporary workaround implemented until W.D. release a more permanent fix.
If SSH is disabled and the Dashboard UI is bricked then I really don’t have an easy solution for you.
One solution is to open-up the MBL to attach the MBL’s disk to another computer to diagnose the problems, but then you wave bye-bye to your warranty and if it’s out of warranty W.D. might not wish to touch it because it’s been opened. (The repair may cost.)
Second option is that you return your MBL back to W.D. for repair or replacement.
Really, and in all fairness, if the internal Linux operating system has not been messed with and faulty firmware has bricked something or the entire MBL then it should be repaired or replaced F.O.C. Not my call. Call W.D. technical support and get help from them.
When you get the new one, turn on SSH before you do anything else with it and DO NOT forward the MyBook Live’s port 22 to the Internet. You’ll have a chance to fix things if things go wrong with the replacement.
The instructions are to sort out an issue with the Twonky media server. Used by loads of media players. Especially the media players that only understand the DNLA protocol
I took the rather unorthodox method of turning the power to the unit on and off when I could no longer access the device via dashboard and this seems to have fixed it. Have now enabled SSH.
My MBL is on firmware 01.02.12 with MioNet 4.3.1.13 and I cannot get it to auto update to 2.0+ as it just says ‘firmware is up to date’
Manual update via firefox or IE also doesn’t work as it will not upload the file ‘apnc-021009-124-20111113’ it just returns to the browse/upload screen.
Does anyone know why this is? Is my MBL too old? It’s a 1TB white light version.
Any help appreciated
EDIT: Think this may be my error; looks like I must have a WD World Edition, not Live, hence I cannot get all the cool features of 2.0
Tim84, you write that you have the white light version. I’ve only known there be a black MyBook Live. Are you posting in the right forum? (Going to have to check W.D.'s web site to remind myself what NASs W.D. sell.)
