I feel I’m at the end of my tether with my 2tb MyBook Live. I have it hooked up to a WD MyNet750 (which ought to be a decent combination…). It serves my WDTV Live and Sonos along with all the computers in the house.
The link with the MyBook is incredibly unreliable. It will be accessible for around an hour or 2 after a power cycle and then become unaccessible after. I can remove the ethernet cable and replug but to no avail. It requires a power cycle to “come back to life”. As such, the cloud storage is essentially useless as I need to be in the house to restart the MyBook.
I have tried everything I can think of to try and get some stability. It is on the latest firmware. As a side note, updating firmware takes many hours. It seems to get stuck on the rebooting phase for a long long time. Anyhow, it eventually confirms that the firmware has been updated. It has not been reliable on former firmware either.
Any tips and tricks to get this horrible thing working as it is supposed to?
Cheers
Check your MyNet750 logs and post up or send to WD Support. There should be some useful information there. To check the MBL side:
* http://yourmblip/UI/ssh
* ensble ssh
* putty.exe or winscp.exe into your MBL
* post up or sent the /var/log/messages file to WD Support
Firstly, thanks for the reply 
Quick question, what’s the command line to see the messages in putty? Have got all the MyNet logs logging but I am not Linux pro…Far far from it! I have connected to MBL with putty but now have a script and I am not inclined to start making matters worse by entering any old script. I’ll take this to support and update accordingly.
Thanks again
* once you’re logged in via putty, run this command (it will scroll accross your screen)
cat /var/log/messages
* left click on the little putty console icon in the upper left hand corner of the screen
* Click “Copy all to Clip Board”
* open Notepad and click Paste and save it MBL-messages.txt
* exit out of putty
* save the MBL-messages.txt to your PC and sens it to support
Thanks pal that’s great. I’ll follow up once I hear from support
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SCon trol F0300)
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: Interrupt status = 0x00042020
Mar 9 20:02:22 MyBookLive kernel: dev status = 0x03087722
Mar 9 20:02:22 MyBookLive kernel: apm82181-adma: Probing AMCC APM82181 ADMA eng ines…
Mar 9 20:02:22 MyBookLive kernel: AMCC(R) APM82181 ADMA Engine found [1]: ( cap abilities: memcpy )
Mar 9 20:02:22 MyBookLive kernel: --------------- dma_async_device_register: 68 3-------------------------
Mar 9 20:02:22 MyBookLive kernel: ata2.00: ATA-8: WDC WD20EURS-63S48Y0, 51.0AB5 1, max UDMA/133
Mar 9 20:02:22 MyBookLive kernel: ata2.00: 3907029168 sectors, multi 0: LBA48 N CQ (depth 1/32)
Mar 9 20:02:22 MyBookLive kernel: apm82181 adma1: allocated 512 descriptor slot s
Mar 9 20:02:22 MyBookLive kernel: AMCC(R) APM82181 ADMA Engine found [2]: ( cap abilities: memcpy )
Mar 9 20:02:22 MyBookLive kernel: --------------- dma_async_device_register: 68 3-------------------------
Mar 9 20:02:22 MyBookLive kernel: apm82181 adma2: allocated 512 descriptor slot s
Mar 9 20:02:22 MyBookLive kernel: AMCC(R) APM82181 ADMA Engine found [3]: ( cap abilities: memcpy )
Mar 9 20:02:22 MyBookLive kernel: --------------- dma_async_device_register: 68 3-------------------------
Mar 9 20:02:22 MyBookLive kernel: apm82181 adma3: allocated 512 descriptor slot s
Mar 9 20:02:22 MyBookLive kernel: ata2.00: configured for UDMA/133
Mar 9 20:02:22 MyBookLive kernel: blk_queue_max_hw_segments: set to minimum 1
Mar 9 20:02:22 MyBookLive kernel: scsi 1:0:0:0: Direct-Access ATA WDC WD20EURS-63S 51.0 PQ: 0 ANSI: 5
Mar 9 20:02:22 MyBookLive kernel: oprofile: using timer interrupt.
Mar 9 20:02:22 MyBookLive kernel: Macsec proc interface Initiliazed
Mar 9 20:02:22 MyBookLive kernel: Registered Macsec Interface
Mar 9 20:02:22 MyBookLive kernel: IPv4 over IPv4 tunneling driver
Mar 9 20:02:22 MyBookLive kernel: sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Mar 9 20:02:22 MyBookLive kernel: sd 1:0:0:0: [sda] 4096-byte physical blocks
Mar 9 20:02:22 MyBookLive kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
Mar 9 20:02:22 MyBookLive kernel: GRE over IPv4 tunneling driver
Mar 9 20:02:22 MyBookLive kernel: sd 1:0:0:0: [sda] Write Protect is off
Mar 9 20:02:22 MyBookLive kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Mar 9 20:02:22 MyBookLive kernel: TCP cubic registered
Mar 9 20:02:22 MyBookLive kernel: NET: Registered protocol family 10
Mar 9 20:02:22 MyBookLive kernel: IPv6 over IPv4 tunneling driver
Mar 9 20:02:22 MyBookLive kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
Mar 9 20:02:22 MyBookLive kernel: sda:
Mar 9 20:02:22 MyBookLive kernel: NET: Registered protocol family 17
Mar 9 20:02:22 MyBookLive kernel: Bridge firewalling registered
Mar 9 20:02:22 MyBookLive kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@ candelatech.com>
Mar 9 20:02:22 MyBookLive kernel: All bugs added by David S. Miller <davem@redh at.com>
Mar 9 20:02:22 MyBookLive kernel: drivers/rtc/hctosys.c: unable to open rtc dev ice (rtc0)
Mar 9 20:02:22 MyBookLive kernel: sda1 sda2 sda3 sda4
Mar 9 20:02:22 MyBookLive kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Mar 9 20:02:22 MyBookLive kernel: md: Waiting for all devices to be available b efore autodetect
Mar 9 20:02:22 MyBookLive kernel: md: If you don’t use raid, use raid=noautodet ect
Mar 9 20:02:22 MyBookLive kernel: md: Autodetecting RAID arrays.
Mar 9 20:02:22 MyBookLive kernel: md: Scanned 2 and added 2 devices.
Mar 9 20:02:22 MyBookLive kernel: md: autorun …
Mar 9 20:02:22 MyBookLive kernel: md: considering sda2 …
Mar 9 20:02:22 MyBookLive kernel: md: adding sda2 …
Mar 9 20:02:22 MyBookLive kernel: md: adding sda1 …
Mar 9 20:02:22 MyBookLive kernel: md: created md0
Mar 9 20:02:22 MyBookLive kernel: md: bind
Mar 9 20:02:22 MyBookLive kernel: md: bind
Mar 9 20:02:22 MyBookLive kernel: md: running:
Mar 9 20:02:22 MyBookLive kernel: md0: WARNING: sda2 appears to be on the same physical disk as sda1.
Mar 9 20:02:22 MyBookLive kernel: True protection against single-disk failure m ight be compromised.
Mar 9 20:02:22 MyBookLive kernel: raid1: raid set md0 active with 2 out of 2 mi rrors
Mar 9 20:02:22 MyBookLive kernel: md0: detected capacity change from 0 to 20478 03392
Mar 9 20:02:22 MyBookLive kernel: md: … autorun DONE.
Mar 9 20:02:22 MyBookLive kernel: md0: unknown partition table
Mar 9 20:02:22 MyBookLive kernel: kjournald starting. Commit interval 5 second s
Mar 9 20:02:22 MyBookLive kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Mar 9 20:02:22 MyBookLive kernel: EXT3 FS on md0, internal journal
Mar 9 20:02:22 MyBookLive kernel: EXT3-fs: recovery complete.
Mar 9 20:02:22 MyBookLive kernel: EXT3-fs: mounted filesystem with ordered data mode.
Mar 9 20:02:22 MyBookLive kernel: VFS: Mounted root (ext3 filesystem) on device 9:0.
Mar 9 20:02:22 MyBookLive kernel: Freeing unused kernel memory: 448k init
Mar 9 20:02:22 MyBookLive kernel: Disable EMAC EMI Fix
Mar 9 20:02:22 MyBookLive kernel: eth0: link is up, 1000 FDX, pause enabled
Mar 9 20:02:25 MyBookLive S15mountDataVolume.sh: begin script: start
Mar 9 20:02:31 MyBookLive logger: hostname=MyBookLive
Mar 9 20:02:37 MyBookLive kernel: EXT4-fs (sda4): recovery complete
Mar 9 20:02:37 MyBookLive kernel: EXT4-fs (sda4): mounted filesystem with order ed data mode
Mar 9 20:02:39 MyBookLive _: pkg: wd-nas
Mar 9 20:02:40 MyBookLive _: pkg: networking-general
Mar 9 20:02:40 MyBookLive _: pkg: apache-php-webdav
Mar 9 20:02:40 MyBookLive _: pkg: date-time
Mar 9 20:02:41 MyBookLive _: pkg: alerts
Mar 9 20:02:41 MyBookLive _: pkg: admin-rest-api
Mar 9 20:02:41 MyBookLive [admin-rest-api.preinst] 03/09/13 20:02:41: test
Mar 9 20:02:41 MyBookLive [admin-rest-api.preinst] 03/09/13 20:02:41: test()
Mar 9 20:02:41 MyBookLive [admin-rest-api.preinst] 03/09/13 20:02:41: done.
Mar 9 20:02:42 MyBookLive [admin-rest-api.postinst] 03/09/13 20:02:42: test con text=test
Mar 9 20:02:42 MyBookLive [admin-rest-api.postinst] 03/09/13 20:02:42: permissi ons check for //var/www/Admin/webapp/config: PASSED
Mar 9 20:02:42 MyBookLive [admin-rest-api.postinst] 03/09/13 20:02:42: permissi ons check for /dynamicconfig.ini: FAILED
Mar 9 20:02:42 MyBookLive [admin-rest-api.postinst] 03/09/13 20:02:42: permissi ons check for //usr/local/nas/orion/: PASSED
Mar 9 20:02:42 MyBookLive [admin-rest-api.postinst] 03/09/13 20:02:42: permissi ons check for //usr/local/nas/orion//orion.db: PASSED
Mar 9 20:02:42 MyBookLive [admin-rest-api.postinst] 03/09/13 20:02:42: setup te st for admin-rest-api: PASSED
Mar 9 20:02:42 MyBookLive [admin-rest-api.postinst] 03/09/13 20:02:42: done.
Mar 9 20:02:42 MyBookLive _: pkg: upnp-nas
Mar 9 20:02:42 MyBookLive _: pkg: dlna-server-access
Mar 9 20:02:43 MyBookLive _: pkg: dlna-server-twonky
Mar 9 20:02:43 MyBookLive _: pkg: itunes
Mar 9 20:02:43 MyBookLive _: pkg: nas-safepoint
Mar 9 20:02:43 MyBookLive _: pkg: webui
Mar 9 20:02:44 MyBookLive _: pkg: orion-resources
Mar 9 20:02:44 MyBookLive _: pkg: afp
Mar 9 20:02:44 MyBookLive kernel: Adding 500608k swap on /dev/sda3. Priority:- 1 extents:1 across:500608k
Mar 9 20:02:47 MyBookLive S99wdInitFinalize: begin script: start
Mar 9 20:02:47 MyBookLive S99wdInitFinalize: currentRootDevice is set to /dev/m d0
Mar 9 20:02:47 MyBookLive S99wdInitFinalize: currentRootDevice = /dev/md0
Mar 9 20:02:47 MyBookLive logger: hostname=MyBookLive
Mar 9 20:02:47 MyBookLive S99wdInitFinalize: Running final checks… (version 02 .41.05-034 on /dev/md0)
Mar 9 20:02:47 MyBookLive S99wdInitFinalize: #--------------------------------- ----------#
Mar 9 20:02:47 MyBookLive S99wdInitFinalize: System restart: current version is 02.41.05-034
Mar 9 20:02:47 MyBookLive S99wdInitFinalize: #--------------------------------- ----------#
Mar 9 20:02:47 MyBookLive S99wdInitFinalize: Rotate logs
Mar 9 20:02:48 MyBookLive _: run pkg bootup scripts:
Mar 9 20:02:48 MyBookLive [bootscript_001_networking-general] 03/09/13 20:02:48 : ( boot-system ) begin
Mar 9 20:02:48 MyBookLive logger: hostname=MyBookLive
Mar 9 20:02:48 MyBookLive [bootscript_001_networking-general] 03/09/13 20:02:48 : done.
Mar 9 20:02:48 MyBookLive [bootscript_005_wd-nas] 03/09/13 20:02:48: ( boot-sys tem ) begin
Mar 9 20:02:48 MyBookLive [bootscript_005_wd-nas] 03/09/13 20:02:48: done.
Mar 9 20:02:48 MyBookLive [bootscript_015_webui] 03/09/13 20:02:48: ( boot-syst em ) begin
Mar 9 20:02:48 MyBookLive [bootscript_015_webui] 03/09/13 20:02:48: done.
Mar 9 20:02:48 MyBookLive [bootscript_035_nas-safepoint] 03/09/13 20:02:48: ( b oot-system ) begin
Mar 9 20:02:48 MyBookLive [bootscript_035_nas-safepoint] 03/09/13 20:02:48: don e.
Mar 9 20:02:48 MyBookLive [bootscript_075_orion-resources] 03/09/13 20:02:48: ( boot-system ) begin
Mar 9 20:02:48 MyBookLive [bootscript_075_orion-resources] 03/09/13 20:02:48: d one.
Mar 9 20:02:48 MyBookLive [bootscript_085_wd-lib] 03/09/13 20:02:48: ( boot-sys tem ) begin
Mar 9 20:02:48 MyBookLive [bootscript_085_wd-lib] 03/09/13 20:02:48: pkg wd-lib () system boot…
Mar 9 20:02:48 MyBookLive [bootscript_085_wd-lib] 03/09/13 20:02:48: done
Mar 9 20:02:48 MyBookLive [bootscript_095_admin-rest-api] 03/09/13 20:02:48: ( boot-system ) begin
Mar 9 20:02:49 MyBookLive apache2: 192.168.1.108 WebUI::session_start()
Mar 9 20:02:50 MyBookLive apache2: 192.168.1.108 WebUI::session_start()
Mar 9 20:02:54 MyBookLive apache2: 192.168.1.108 WebUI::session_start()
Mar 9 20:02:55 MyBookLive apache2: 192.168.1.108 WebUI::session_start()
Mar 9 20:02:56 MyBookLive [bootscript_095_admin-rest-api] 03/09/13 20:02:56: do ne.
Mar 11 18:21:50 MyBookLive logger: /usr/local/sbin/monitorio.sh: waiting for sys tem to become ready…
Mar 11 18:21:50 MyBookLive kernel: svc: failed to register lockdv1 RPC service ( errno 97).
Mar 11 18:21:56 MyBookLive logger: /usr/local/sbin/monitorio.sh: waiting for sys tem to become ready…
Mar 11 18:22:11 MyBookLive logger: /usr/local/sbin/monitorio.sh: waiting for sys tem to become ready…
Mar 11 18:22:17 MyBookLive logger: /usr/local/sbin/monitorio.sh: waiting for sys tem to become ready…
Mar 11 18:22:18 MyBookLive logger: /etc/rc2.d/S86orion: waiting for system to be come ready…
Mar 11 18:22:22 MyBookLive logger: /usr/local/sbin/monitorio.sh: waiting for sys tem to become ready…
Mar 11 18:22:22 MyBookLive : System ready
Mar 11 18:22:24 MyBookLive logger: Starting orion services: miocrawlerd, mediacr awlerd, communicationmanagerd
Mar 11 18:22:24 MyBookLive : Check if new firmware is available
MyBookLive:~#
Well all of this looks fairly alarming…
j0hnb0y wrote:
Well all of this looks fairly alarming…
Heheh… not at all. That’s a typical bootup log for the first major part. The Mar 11 stuff is typical maintenance tasks.
I just power cycled it a few minutes ago because from March 9 at some point until a few minutes ago the unit was not accessible on network. No dashboard, SSH access, anything…
I’ve just decided to switch to the WD Media DLNA server. And the … thing has got stuck whilst rebooting, just a white light for the past 15 minutes. I would love to RMA this thing but it says “out of region”, even though it was purchased in the UK.
Not happy at all 
I compared your messages out to my MBL after a clean reboot and the only difference other than the hostname and ip address is this line below. I ran “find / -name dynamicconfig.ini” and found two files, but I have no clue to what this FAILED message means (assuming it’s file permission). Perhaps someone more experienced with MBL firmware will speak up.
Mar 9 20:02:42 MyBookLive [admin-rest-api.postinst] 03/09/13 20:02:42: permissions check for /dynamicconfig.ini: FAILED
Sounds similar to the problem I had except that only the AVR was affected but not the blu-ray player which had no problems. Solved only coincidentally & without any good explanation why so.
The original connection of the MBL was to the router; the AVR & player was connected to a switch in another room & the 75 ft cable connected to a switch which was connected to the router. I had “dropouts” even while playing flac music on the AVR but never with the player playing video; the MBL even was disconnected in the middle of playing music! I was blaming both Yamaha & WD but difficult since the problem only affected the AVR.
Read here some people just connected all their devices to the switch instead of the router which seems more “intiutive” to me; so I moved the MBL connection to the switch.
AVR “dropouts” solved & not need to reboot the MBL or disconnect/connect the MBL cable to play music for 1 or 2 hrs or longer. A very strange coincidence & no valid reason why it worked. Could be a Netgear router problem but still isn’t a real explanation why only the AVR was affected.
Unless you have a switch around or can borrow a switch temporarily, it is an expensive try & test if that would work.
I had purchased an wifi extender to use as a bridge so not to have a long cable to the next room; but forgot that both my devices & the MBL were connected to a switch. With bated breath, after configurations, I started the AVR & it is working without disconnections even if the technically the wifi bridge is connected directly to the router. So it does seem like my 3T MBL like to be connected to a switch instead of directly to the router.
I am not going back to check if the MBL will still work correctly without problems by having the MBL connect directly to the router. Not looking at a gift from the gods of technology:smiley:.
Interesting Paul,
I have a Netgear switch sitting right next to the router but have never plugged the MBL into it. I just blindly assumed that a WD MBL plugged into a WD MyNet N750 ought to be the best solution!
Will give it a go. Today I still have frequent network dropouts and automatic restarts if I try to transfer too many files…
I think the MBL has broken me. I am going to purchase an external HDD (NOT WD!) and plug it into the USB on the router (at least this works as it is supposed to…) to share around the house. Will stick to DropBox for cloud storage.
WD I have always been a big advocate of your products until now. Poor support, poor firmware and from reviews on the net, a very poor product. I will certainly NOT be buying a Sentinel for my more important NAS needs after my experience with the MBL.
Disappointed. Rant over. If WD support ever bother to reply to my open email case and have a decent solution then I will of course eat humble pie and sing their praises again. I am eagerly awaiting a response saying “have you upgraded to the lastest firmware?”.
Thanks to the contributers to this thread and for trying to help. Seagate here I come
