About MBL not going to sleep, log files filling system partition and getting a blank Dashboard UI

is it possible to get a step by step instruction for us noobies, on what to do to get this blinking light to stop?

thanks!

This thread or the 2 methods about the logs need to be in a “sticky”; same with the enabling ssh.  In fact, the “sticky” should be the 1st posting on the forum.

Don’t know if anyone is moderating; perhaps WDTom/WDtony(?) can do it?  Don’t remember his forum name…but have seen it.

norm43 wrote:

is it possible to get a step by step instruction for us noobies, on what to do to get this blinking light to stop?

 

thanks!

That and regaining access to the Dashboard UI would be killers! Regarding this issues, WD has left the building and is still continuing to sell and distribute the faulty units / firmwares! This was my first WD device and it will be my last! And, if this isn’t resolved in the next week, I will warn everybody I know about this!

Why don’t they develop a one-botton corrective app? Is a massive RMA campaign cheaper? 

Regarding “not going to sleep” (blue light?).

If the WD hard drive is a “green” drive implying that it goes to sleep when not accessed for a certain time, is the blue led light indication really needed?  And even if the led light is green, does the drive still do the sleep mode; if the blue led indicator isn’t really needed then we can just ignore the lack of the blue led display?  Asking because my MBL has stopped showing a blue led.

Using “top” in ssh mode, I see just about everything is in “sleep” mode; no idea if top just miss anything that is running because of the timings of checking & display.

I’ve just updated to the latest firmware. After the firmware was installed, the web UI never recogniced the reboot. And SSH stopped working (timeout). I unplugged the device (from the wall socket), when the reboot was completed and I tried to use the UI, a message came up stating the the device was initializing.

After waiting for 15 min or more I did another reset.

Once restarted the SSH started working. Using df -h I could see the that the /var/log/ was increasing. I stopped the apple talk that has been mentioned before in this thread. That did not help. The files messages and kernel.log was still increasing.

Finaly I got this error message:
MyBookLive:/var/log#
Message from syslogd@MyBookLive at Apr 28 00:38:22 …
kernel:Unrecoverable FP Unavailable Exception 801 at cfff7dd0

df -h gave this result:

Filesystem Size Used Avail Use% Mounted on
/dev/md1 1.9G 981M 845M 54% /
tmpfs 50M 0 50M 0% /lib/init/rw
udev 10M 6.7M 3.4M 67% /dev
tmpfs 50M 0 50M 0% /dev/shm
tmpfs 50M 3.0M 48M 6% /tmp
ramlog-tmpfs 20M 9.0M 11M 45% /var/log
/dev/sda4 1.9T 47G 1.8T 3% /DataVolume

After this error message, the log files stopped growing. I don’t know if this helps any of you, but seems like many like me are struggling with the MBL.

BTW I have a MBL 2 TB that I got 2 days ago.

What are the last 50(ish) lines of the /var/log/kernel.log file?  Can you post them on this thread?

Sorry did not record the information from the kern.log file. And the MBL has been restarted since I posted my thread. 

This morning it seems like everything is working fine. But I got the same message as I did yesterday:

Message from syslogd@MyBookLive at Apr 28 12:04:06 …
kernel:Unrecoverable FP Unavailable Exception 801 at cfff7dd0

Message from syslogd@MyBookLive at Apr 28 12:04:06 …
kernel:Unrecoverable FP Unavailable Exception 801 at cfff7dd0

 It seems like the log files are not growing anymore:

Filesystem Size Used Avail Use% Mounted on
/dev/md1 1.9G 982M 844M 54% /
tmpfs 50M 0 50M 0% /lib/init/rw
udev 10M 6.7M 3.4M 67% /dev
tmpfs 50M 0 50M 0% /dev/shm
tmpfs 50M 1.2M 49M 3% /tmp
ramlog-tmpfs 20M 2.6M 18M 13% /var/log
/dev/sda4 1.9T 47G 1.8T 3% /DataVolume

The kern.log file look like:

Apr 28 14:15:53 MyBookLive kernel: BUG: scheduling while atomic: monitorio.sh/2702/0x10000002
Apr 28 14:15:53 MyBookLive kernel: BUG: scheduling while atomic: monitorio.sh/2702/0x10000002
Apr 28 14:15:53 MyBookLive kernel: BUG: scheduling while atomic: monitorio.sh/2702/0x10000002
Apr 28 14:15:53 MyBookLive kernel: BUG: scheduling while atomic: monitorio.sh/2702/0x10000002
Apr 28 14:15:53 MyBookLive kernel: BUG: scheduling while atomic: monitorio.sh/2702/0x10000002
Apr 28 14:15:53 MyBookLive kernel: BUG: scheduling while atomic: monitorio.sh/2702/0x10000002

Thats more or less at least the last 200 lines of the file. 

You may have encountered a bug.  It’ll get noticed and investigated.