MybookLive inaccessible: Flashing Green Light

Marvin_Fuqua · June 16, 2016, 11:11pm

Setup: MyBookLive 2TB wired via a DLink FastEthernet Switch to a WRT-54G router (hard wire connection). Running the latest firmware.

Problem: With Ethernet cable connected, the Green light flashes constantly. With the Ethernet cable disconnected the Yellow light flashes constantly. The data on the hard drive is inaccessible to any computer on the local network. Able to access http://mybooklive.local/UI/# via Win10 Edge browser. The simple Diagnostic Test locks up at 90%, the advanced Diagnostic Test locks up at 10%.

Failed Solution 1: Restart HD by unplugging, pausing and replugging.

Failed Solution 2: Reset the HD using the reset switch on the back of the unit while the HD is running.

Failed Solution 3: Reset the HD using the reset switch on the back of the unit and immediately powering down, pausing and then powering up the unit.

Failed Solution 4: Via the http://mybooklive.local/UI/# link, disabling all services, including remote access.

Failed Solution 5: Unplugging unit, place it in the refrigerator for 15 minutes to cool all components, then restart.

Additional info: The hard drive has been in service for several years and the problem just began.

Excerpt from system log:

Jun 15 19:46:01 MyBookLive dhclient: bound to 192.168.1.101 – renewal in 298926 seconds.
Jun 16 02:15:57 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:15:58 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:16:00 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:16:04 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:16:12 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:16:28 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:17:11 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:17:12 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:17:14 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:17:18 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:17:26 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 02:17:42 MyBookLive mDNSResponder: ERROR: getOptRdata - unknown opt 4
Jun 16 12:03:11 MyBookLive ifplugd(eth0)[3984]: ifplugd 0.28 initializing.
Jun 16 12:03:11 MyBookLive ifplugd(eth0)[3984]: Using interface eth0/00:90:A9:B7:FB:80 with driver <ibm_emac> (version: 3.54)
Jun 16 12:03:11 MyBookLive ifplugd(eth0)[3984]: Using detection mode: SIOCETHTOOL
Jun 16 12:03:11 MyBookLive ifplugd(eth0)[3984]: Initialization complete, link beat detected.
Jun 16 12:03:11 MyBookLive ifplugd(eth0)[3984]: Could not open /dev/tty, cannot beep.
Jun 16 12:03:11 MyBookLive ifplugd(eth0)[3984]: Executing ‘/etc/ifplugd/ifplugd.action eth0 up’.
Jun 16 12:03:11 MyBookLive ifplugd(eth0)[3984]: client: /sbin/ifup: interface eth0 already configured
Jun 16 12:03:11 MyBookLive ifplugd(eth0)[3984]: Program executed successfully.
Jun 16 12:03:29 MyBookLive init: no more processes left in this runlevel
Jun 16 12:03:29 MyBookLive init: Switching to runlevel: 2
Jun 16 12:03:30 MyBookLive mdadm[4699]: NewArray event detected on md device /dev/md1
Jun 16 12:03:31 MyBookLive rpc.statd[4796]: Version 1.2.1 Starting
Jun 16 12:03:31 MyBookLive sm-notify[4797]: Failed to open /var/lib/nfs/sm.bak: No such file or directory
Jun 16 12:03:31 MyBookLive rpc.statd[4796]: statd running as root. chown /var/lib/nfs/sm to choose different user
Jun 16 12:03:34 MyBookLive netatalk[4962]: Netatalk AFP server starting
Jun 16 12:03:35 MyBookLive cnid_metad[4964]: volume “Public” does not support Extended Attributes or read-only volume
Jun 16 12:03:35 MyBookLive cnid_metad[4964]: volume “SmartWare” does not support Extended Attributes or read-only volume
Jun 16 12:03:35 MyBookLive cnid_metad[4964]: volume “TimeMachineBackup” does not support Extended Attributes or read-only volume
Jun 16 12:03:35 MyBookLive cnid_metad[4964]: volume “TimeMachine” does not support Extended Attributes or read-only volume
Jun 16 12:03:35 MyBookLive cnid_metad[4964]: volume “XXXXX” does not support Extended Attributes or read-only volume
Jun 16 12:03:35 MyBookLive cnid_metad[4964]: volume “XXXXX” does not support Extended Attributes or read-only volume
Jun 16 12:03:35 MyBookLive cnid_metad[4964]: CNID Server listening on localhost:4700
Jun 16 18:14:38 MyBookLive ntpdate[4716]: step time server 40.76.58.209 offset 22255.702704 sec
Jun 16 18:14:38 MyBookLive afpd[4963]: Netatalk AFP/TCP listening on 192.168.1.109:548
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: Found user ‘avahi’ (UID 107) and group ‘avahi’ (GID 110).
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: Successfully dropped root privileges.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: avahi-daemon 0.6.25 starting up.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: Successfully called chroot().
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: Successfully dropped remaining capabilities.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: No service file found in /etc/avahi/services.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::290:a9ff:feb7:fb80.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: New relevant interface eth0.IPv6 for mDNS.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.109.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: New relevant interface eth0.IPv4 for mDNS.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: Network interface enumeration completed.
Jun 16 18:14:40 MyBookLive avahi-daemon[5307]: Server startup complete. Host name is MyBookLive.local. Local service cookie is 2885989524.

Any assistance would be helpful. Everything is stored on this drive, including all my computer backups.

wdlive76 · June 17, 2016, 12:03am

Enable SSH. Then use Filezilla to access the MBL via SSH. See if you can get in and look for your data in /shares/ . If the data is there, good. If so far no problems, then use Putty to SSH into the MBL and restart the samba server. Then in Windows go to Network and see if you can get into the MBL and the files.
If none of this works, then use a Debrick guide from this forum. Honestly, I’d just go straight to a debrick if I were you. It’s the failsafe way to get a fresh reinstall of the OS without losing your data.

Marvin_Fuqua · June 17, 2016, 12:54am

I have never set up an FTP nor have I used Filezilla, but I have downloaded the file and have tried the following settings, but authentication fails.

Host: sftp://mybooklive.local/ui/ssh

Username: Admin

Password: I used the password from sftp://mybooklive.local/ui/ssh#

Port: 22

QuickConnect

Results:

Error: Critical error: Could not connect to server
Status: Disconnected from server
Status: Connecting to mybooklive.local…
Response: fzSftp started, protocol_version=5
Command: open “admin@mybooklive.local” 22
Command: Pass: *******
Error: Authentication failed.
Error: Critical error: Could not connect to server
Status: Disconnected from server
Status: Connecting to mybooklive.local…
Response: fzSftp started, protocol_version=5
Command: open “admin@mybooklive.local” 22
Command: Pass: *******
Error: Authentication failed.
Error: Critical error: Could not connect to server

I have tried using the default password 123456 and no password.

Any advice on setup?
After reading the section on Debricking the drive, I found that I would lose ALL of my data. My primary concern is being about to access the files. This drive IS my backup and does contain a large number of shared files.

Marvin_Fuqua · June 17, 2016, 1:18am

My mistake: The username is “root”, provided at sftp://mybooklive.local/ui/ssh.

I can read the files in FileZilla.

I am now able to access the data safely.

Any idea how to fix the mybooklive?

wdlive76 · June 17, 2016, 2:32am

I gave you a list of things to do, sounds like you’ve done only a few. The purpose of using SSH and Filezilla was to isolate the problem. Now at least you know that:

you have the ability to make a network connection to the MBL
the SSH server works on the MBL
the data is all there
the http (apache) server works (dashboard works)

So that leaves you with figuring out if the samba (Windows) server works or not, and if not then why. Look at my instructions again.

this should save you a minute of searching. /etc/init.d/samba restart

also debrick guide can do it without losing data.

Marvin_Fuqua · June 17, 2016, 3:50am

Thank you for your assistance. I have been copying files via FileZilla and will look further into your directions. I appreciate your assistance. I have never used Linux, FileZilla, FTP protocol and had no idea what SSH, MBL, or samba meant. I read numerous warnings about not attempting SSH without a thorough understanding of Linux at the risk of permanently ruining the drive. I still have some additional reading to do before attempting any recovering of my system and will be out of town for several days.

Again, thank you for your assistance it has been greatly appreciated.

Shabuboy · June 17, 2016, 4:14am

What changed? Did you just barely get Win10? You have Win10 it seems… If you do, 99% chance that is the issue and not MBL.
Have you tried another PC or another non-Win10 PC?
Have you tried your phone/tablet?

Green flashing LED means all is good, yellow means no ethernet connection. Check manual for other LED status.

Marvin_Fuqua · June 19, 2016, 2:34am

What changed? Beats me; one morning my wife said she could not access her data on the drive. To my knowledge, nothing unusual happened overnight?

One computer automatically upgraded to Windows 10 without my permission two weeks ago. The system was working great on that, a Windows 7 and Windows 8.2 machine, as well as an old Windows XP (inventory only) computer. When the problem occurred, none of these devices, including a Kindle Fire HD, nor the DishNetwork Hopper system could access the file system on the hard drive.

One user noted the constant flashing green could indicate that the daemon driver might be stuck in a loop trying to write an infinite number of times to the disk. I tried the suggested fixes for this problem and it did not work.

I have been out of town while using FileZilla to manually copy all of the files off the MyBookLive. When I got back in town, the green light was finally solid, but the file system could still not be accessed by any network device.

I will review wdlive76’s advice and read up on how to restart the samba server. I know nothing about Linux and have only a basic knowledge of unix, but the Internet is full of information. I only recently realized the MBL was an acronym for the MyBookLive, I thought it might be a Linux version of DOS’s MBR (Master Boot Record). Most of what I have read in this forum warns users against using the Linux OS on the MBL because the user could cause irreversible damage to the drive.

I will post my progress or lack thereof, for other users. If anyone requests, I will provide a detailed description of how I implemented wdlive76’s advice. Thank you for your input!

Marvin_Fuqua · June 19, 2016, 9:23pm

I tried to restart the samba server, but ran out of passwords while trying to access the drive.

I took wdlive76’s advice and ran the Debrick protocol as outlined here: [GUIDE] How to unbrick a totally dead MBL.

My drive is now accessible, but the flashing green light continued for about 10 minutes; now it is flashing red. Looks like more reading for me.