Blinking green light on my book live

i have a a 2Tb my book live and it was working well for 2 weeks,and just a day ago my PS3 wouldn’t find it, and then it was not appearing on my network on my PC. and ive tried hitting the reset button on the back of it and unplugging it and starting back up, and still been blinking green light for overnight and all day today. anyone have some ideas on whats happening, or how to fix it?

Turn it off for several hours to allow the drive and electroncs to cool down.  Turn it back on and see if it’s still not working.

Apart from that, contact Western Digital support.  I have no idea why it’s constantly blinkling green.

Have you done all the other checks?  Like is the router ok?  Are the cables ok?  Etc…

ok ya ill turn it off, but ya my router is good cause my pc has internet, and cables are brand new… it powering it off doesn’t do it, then ill contact Western Digital. thanks

I am having the exact same issue (only with my Sony Blu Ray player - which is a near identical set-up to the PS3) or at least it was…

No I only get the blue light and there would appear to be no communication between the router and the drive (my connection was ok to begin with)

My router and all other wired and wireless devices work fine apart from my WD Live Book, please help.

ok so i just talked to WD tech support, and i just held the reset button on the back of the my book live for 4 seconds, then immediately unplug the power to the my book live for 10 secs, then plug back in and now its showing up on my network… hope this helps you.

Hello – I’ve had my MyBook Live 3TB unit for just under a week now. I installed the 2.00.* firmware upgrade with no difficulty. I can access the drive just fine, and indeed copied about 800GB of data onto it. Then I attempted to use the “safepoint” backup feature to back up my other MBL drive – but got reports that the drive was overheating. Long story short, I rebooted the drive and I’ve been running the “full” diagnostic test for the past 24+ hours, it seems stuck at 7/8 finished. And in the meantime the drive is continuously flashing its green light. Through all of this the drive is visible on the network and accessible and I can access the dashboard.

So here’s my questions: in another thread

http://community.wdc.com/t5/My-Book-Live/MBL-does-not-go-to-sleep-anymore/td-p/138268/highlight/true

there is mention of a low priority process that transcodes photos into formats suitable for smartphones. My suspicion is that this processs is what’s causing my green light to blink.

Question 1: How can I kill this process and make sure it stays dead? I really have no use for it.

Question 2: What is the “miocrawler” process that’s been running for 885(!) minutes? (see ps aux output below). I have a feeling that this process (and maybe its friend mediacrawler, too) is up to no good. How can I kill *it* and

make it stay dead?

Thanks! Note that aside from sshing in to the command shell, I’ve made no mods or customizations to the Linus OS.

Craig8128

MyBookLive3TB:~# ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.3   4352   960 ?        Ss   Jul23   0:00 init [2]
root         2  0.0  0.0      0     0 ?        S    Jul23   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S    Jul23   0:00 [ksoftirqd/0]
root         4  0.0  0.0      0     0 ?        S    Jul23   0:00 [watchdog/0]
root         5  0.0  0.0      0     0 ?        S    Jul23   0:00 [events/0]
root         6  0.0  0.0      0     0 ?        S    Jul23   0:00 [khelper]
root         9  0.0  0.0      0     0 ?        S    Jul23   0:00 [async/mgr]
root       159  0.0  0.0      0     0 ?        S    Jul23   0:00 [sync_supers]
root       161  0.0  0.0      0     0 ?        S    Jul23   0:00 [bdi-default]
root       162  0.1  0.0      0     0 ?        S    Jul23   2:31 [kblockd/0]
root       167  0.0  0.0      0     0 ?        S    Jul23   0:00 [ata/0]
root       168  0.0  0.0      0     0 ?        S    Jul23   0:00 [ata_aux]
root       169  0.0  0.0      0     0 ?        S    Jul23   0:00 [ksuspend_usbd]
root       174  0.0  0.0      0     0 ?        S    Jul23   0:00 [khubd]
root       177  0.0  0.0      0     0 ?        S    Jul23   0:00 [kseriod]
root       197  0.0  0.0      0     0 ?        S    Jul23   0:00 [rpciod/0]
root       224  0.0  0.0      0     0 ?        S    Jul23   0:00 [khungtaskd]
root       225  0.1  0.0      0     0 ?        S    Jul23   2:39 [kswapd0]
root       226  0.0  0.0      0     0 ?        S    Jul23   0:00 [aio/0]
root       227  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsiod]
root       228  0.0  0.0      0     0 ?        S<   Jul23   0:00 [kslowd000]
root       229  0.0  0.0      0     0 ?        S<   Jul23   0:00 [kslowd001]
root       230  0.0  0.0      0     0 ?        S    Jul23   0:00 [xfs_mru_cache]
root       231  0.0  0.0      0     0 ?        S    Jul23   0:00 [xfslogd/0]
root       232  0.0  0.0      0     0 ?        S    Jul23   0:00 [xfsdatad/0]
root       233  0.0  0.0      0     0 ?        S    Jul23   0:00 [xfsconvertd/0]
root       234  0.0  0.0      0     0 ?        S    Jul23   0:00 [crypto/0]
root       333  0.0  0.0      0     0 ?        S    Jul23   0:00 [scsi_tgtd/0]
root       345  0.0  0.0      0     0 ?        S    Jul23   0:00 [scsi_eh_0]
root       375  0.0  0.0      0     0 ?        D    Jul23   0:00 [btn_t]
root       383  0.0  0.0      0     0 ?        D    Jul23   0:00 [a3gblink_t]
root       442  0.0  0.0      0     0 ?        S    Jul23   0:10 [md0_raid1]
root       444  0.0  0.0      0     0 ?        S    Jul23   0:02 [kjournald]
root       509  0.0  0.4   4608  1024 ?        S<s  Jul23   0:00 udevd --daemon
root       687  0.0  0.0      0     0 ?        S    Jul23   0:00 [flush-9:0]
root       906  0.0  0.3   3584   768 ?        Ss   Jul23   0:03 logsave -s /var/log/fsck/checkfs fsck -C -R -A -a
root      1131  0.0  0.6   4160  1664 ?        Ss   Jul23   0:00 dhclient3 -pf /var/run/dhclient.eth0.pid -lf /var/l
root      1267  0.0  1.1  70848  2816 ?        Sl   Jul23   0:37 /usr/local/bin/upnp_nas_device -webdir /var/local/u
daemon    1279  0.0  0.0   3968   192 ?        Ss   Jul23   0:00 /sbin/portmap
root      1429  0.0  1.3  31616  3392 ?        Sl   Jul23   1:23 /usr/sbin/rsyslogd -c3
root      1452  0.0  4.5  66560 11456 ?        S<s  Jul23   0:07 /usr/sbin/apache2 -k start
root      1468  0.0  0.0      0     0 ?        S    Jul23   0:35 [jbd2/sda4-8]
root      1469  0.0  0.0      0     0 ?        S    Jul23   0:00 [ext4-dio-unwrit]
root      1666  0.0  1.5   9920  3904 ?        Ss   Jul23   0:00 /usr/sbin/sshd
root      1682  0.0  0.9   5632  2304 ?        SN   Jul23   0:12 /bin/sh /usr/local/sbin/monitorio.sh
root      1698  0.0  0.2   3712   640 ?        Ss   Jul23   0:01 /usr/sbin/ifplugd -i eth0 -q -f -u0 -d5 -w -I
root      1724  0.0  0.1   4032   320 ?        Ss   Jul23   0:00 /sbin/rpc.statd
root      1733  0.0  0.1   7808   320 ?        Ss   Jul23   0:00 /usr/sbin/rpc.idmapd
root      1752  0.0  0.0      0     0 ?        S    Jul23   0:00 [lockd]
root      1753  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsd]
root      1754  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsd]
root      1755  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsd]
root      1756  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsd]
root      1757  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsd]
root      1758  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsd]
root      1759  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsd]
root      1760  0.0  0.0      0     0 ?        S    Jul23   0:00 [nfsd]
root      1764  0.0  0.0   4480   192 ?        Ss   Jul23   0:00 /usr/sbin/rpc.mountd --manage-gids
root      1775  0.0  1.2  12032  3136 ?        Ss   Jul23   0:04 /usr/sbin/nmbd -D
root      1778  0.0  0.7  20096  1984 ?        S<s  Jul23   0:00 /usr/sbin/smbd -D
root      1793  0.0  0.0  20096   192 ?        S<   Jul23   0:00 /usr/sbin/smbd -D
root      1844  0.0  0.1   8256   256 ?        S<   Jul23   0:00 /usr/sbin/afpd -U uams_dhx2.so,uams_clrtxt.so -g no
root      1872  0.0  0.3   3776   960 ?        Ss   Jul23   0:00 /usr/local/bin/mDNSResponderPosix -b -f //etc/mDNSR
103       1886  0.0  0.1   5312   320 ?        Ss   Jul23   0:00 /usr/bin/dbus-daemon --system
root      1941 54.6  8.6  31104 21952 ?        SNl  Jul23 885:26 ./miocrawler
root      1960  0.0  0.1  13952   320 ?        SNl  Jul23   1:19 ./bin/mediacrawler
root      1981  0.0  0.1   3584   256 ?        S    Jul23   0:00 /usr/local/bin/resetbtnd /dev/input/event0 4 /usr/l
root      2000  0.0  0.5   5120  1408 ?        SNs  Jul23   0:01 /usr/sbin/cron
root      2041  0.0  0.3   3840   896 ?        S    Jul23   0:00 /usr/local/bin/lld2d eth0
root      2428  0.0  1.5   7936  3904 ?        SN   Jul23   0:04 openvpn /CacheVolume/.orion/client.ovpn
root      2481  0.0  0.1   3776   256 ttyS0    Ss+  Jul23   0:00 /sbin/getty -L ttyS0 115200 vt100
www-data 16459  1.9 12.4  72384 31552 ?        S<   12:51   0:21 /usr/sbin/apache2 -k start
root     17553  0.0  0.0      0     0 ?        S    07:49   0:00 [flush-8:0]
root     25324  0.3  0.7   3776  1792 ?        SN   13:08   0:00 /usr/local/bin/tally
root     25325  1.0  1.1   4672  2944 ?        RN   13:08   0:00 ls -s1NRA --block-size=1 /shares
root     25326  0.4  0.7   4480  1984 ?        SN   13:08   0:00 awk ??{???if ($1 ~ /^[0-9]+$/) {?#???printf("#4:%s:
www-data 25743  1.3 11.7  68864 29760 ?        S<   13:09   0:00 /usr/sbin/apache2 -k start
www-data 25870  0.0  2.5  66560  6592 ?        S<   13:09   0:00 /usr/sbin/apache2 -k start
root     26063  0.7  3.4  13696  8704 ?        Ss   13:09   0:00 sshd: root@pts/0
www-data 26121  0.0  2.5  66560  6592 ?        S<   13:09   0:00 /usr/sbin/apache2 -k start
root     26170  0.1  1.5   5696  4032 pts/0    Ss   13:10   0:00 -bash
root     26279  0.0  1.2   4928  3072 pts/0    R+   13:10   0:00 ps aux
MyBookLive3TB:~#

Question 1: How can I kill this process and make sure it stays dead? I really have no use for it.

Not sure - you might be able to within the linux shell, but we can’t give you help with that.

Question 2: What is the “miocrawler” process that’s been running for 885(!) minutes? (see ps aux output below). I have a feeling that this process (and maybe its friend mediacrawler, too) is up to no good. How can I kill *it* and

make it stay dead?

That is the transcoder that converts your photos to appropriate sie for your mobile device.

The only way to avoid this is to not copy any photos in the public/share photos directory.

Tony -

It seems that I am in the same boat.  My NAS keeps with the green light on, but all my computers are turned off.  I only use the public folder, and have a tone of pictures and videos under the shared folders. What do you suggest me doing?  Also how can I see what processed is being run?

Thanks

As mentioned before, if you have photos under the Public/Shared Pictures folder, the miocrawler process will transcode these photos. The only way to get “around” this is to turn off remote access. Otherwise, just wait a few days (depends on how many photos you have).

Two questions:

  1. What does the Transcode do to my photos?  I don’t want the photos to be altered at all (I want them to keep the same quality)

  2. I turned remove acess off but is still blinking.  I shutted down, and turn it on again but seems that the process is still running.

We do not touch the original photo… don’t worry! These are kept in a hidden cache file within the drive for access only by WD Photos.

Are you on the new firmware? Did you set a sleep timer on the drive? Only other thing is the Media server - that could be indexing your files.

Thanks.  Yes, I am using the new firmware and I have energy saver set at ten minutes. Let me monitor in the next couple of days and will let you know.

Just one last question: I have everything in the ‘Public’ folder.  It’s only me in the house, and I using a linksys router with wireless security.   Is it possible that anyone can be accesing the information?  I understand that the Public folder has no password, but someone still need to have the WAP/WEP password of my wirless network. Is this correct?

I have the same problem with the blinkin green light.  It started after I loaded a video and my iphoto library.  I understand that the crawler is transcoding the pics for my smartphone but I never loaded the mobile app for WD Photo.  I only loaded WD 2 GO.  Does make any difference or does the crawler/transcoder work regardless of whether you’ve loaded the mobile photo app?

Any way to turn it off as I don’t want to view the photos on my phone?

Adding one other thing.  My drive is accessable while the green light blinks but the dashboard no longer works.  What’s up with that?

I just updated my MyBook Live for Lion support and I am also getting the blinking green light. It would be fantastic if the release notes would say something like “After the update, the status LED on your drive will blink green until blah blah blah”.  At least my data seems to be intact and accessible.

   Now I just wish WD would get their stuff together and get a solid update for my MyBook World Edition so I can access the year of TimeMachine backups I have on that drive.

Hi , 

I have the same problem. The green light keeps biinking with no stop , and I don’t have access in to the dashboard anymore.

Tried the “http://IPaddress/UI/” and also “http://MybookLive/UI/”,  all I get is a error 500 on iexplorer or  a blank page in all other browsers.

Cab anybody help? How can I get access to dashboard again??

Does anyone have any further ideas. My green light has been flashing for 6 days down, and access speed is right down.

I have unplugged and reset, change cables, changed network swith and it is still going???

Any help appreciated

NIck

I believe I know what has gone wrong. Read the referenced discussion thread and the associated references to other discussion threads.

http://community.wdc.com/t5/My-Book-Live/About-MBL-not-going-to-sleep-log-files-filling-system-partition/td-p/322457

The problem is that some interaction between the MyBook Live and the Apple MAC is causing the daemon.log file on the MyBook Live to expand at a stupidly rapid rate, exceeding the ramlog’s 20Mb allocation limit which then disables that so log files are written directly to disk (the green LED always blinks and the MBL does not go to sleep) of which the NAS’s system partition fills to 100% which prevents the internal programs changing configuration files here there and everywhere, which caused the Dashboard UI to malfunction as described.

If you have SSH enabled then you can recover your MyBook Live from its malfunctioning state.

How to turn on SSH if you still have a functioning Dashboard IU:

  1. Sign-on to the Dashboard UI.
  2. Assuming that you didn’t change the name of your MBL, goto the URL:  http://MyBookLive.local/UI/ssh
  3. Enable it before your Dashboard UI is rendered inoperative.

This gives you the route to the NAS’s Linux operating system to fix things.

Do NOT forward port 22 from the MyBook Live to the WAN interface on your router !!!

If you can not turn on SSH then you will have to contact W.D. technical support as you might have to exchange your MyBook Live.

1 Like

Hi

I had the same problem. After some days, the disk activity went crazy, and the green light was flashing constantly. Secondly the Web UI was very slow, and sometimes impossible to use. In the first days, I didn’t have that problem, and since the problem pointed in the direction of some kind of indexing, I thought I probably had turned on some unwanted service: I then turned off “MioNET Service”, “Twinky Service” and “iTunes Server”. Since I don’t use any of these services no harm is done. And the problem is solved. No crazy disk activity and the Web UI works.

Best Regards

Jacob Mondrup

Vivant IT Services