At which point does it stall? 1hr is way to long if you’re on a broadband connection.
Greetings
lstener1
The download of the new firmware seems to work fine, but then it says something like “initializing new firmware” and stalls. I also downloaded the FW manually and used “install from file” - here the message is different, but the process stalls as well
The box continuous to be accessible in the meantime, though. A reboot did not help, there’s still the old firmware installed afterwards.
Actually something seems to be broken: Windows (Vista) claimed it could not find a driver for the disk, the web interface is slow and sometimes inaccessible, and transfer rates are poor (1-5 MB/s).
The WD FAQ says that if Windows asked for a driver the disk is definitely broken and needs to be replaced. Too bad, it’s brand new but never worked 
FRAC
birdman wrote:
As posted in another thread, I have not been able to update the firm ware on my MyBook Live. I have tried to check for updates and to manual import the downloaded firmware. Each time, all I get is “Please Wait” and it seems to hang for ever. I have unplugged the NAS a few times but I still have not yet been able to upgrade the firmware.
Any suggestions?
I’m having the same problems, I purchased a 3TB My Book Live a few days ago and am unable to install the new firmware from the original setup from new (the version listed in the dashboard is MyBookLive 01.03.03 : MioNet). When i choose check for updates it lists MyBookLive 01.05.07 as the update version (and fails to update). I manually downloaded the latest firmware from the website and tried to install it via the dashboard and “update from file” and again it fails to update. Any advice or help in this matter would be appreciated 
Is your drive working fine except for the FW update? No other issues, like WIndows asking for a driver, slow web interface or poor transfer rates?
wd:~# dmesg
host /interrupt-controller1 mapped to virtual irq 19
Probing AMCC DMA driver
irq: irq 0 on host /interrupt-controller0 mapped to virtual irq 20
PPC4xx PLB DMA engine IRQ 20
__ioremap(): phys addr 0x0 is RAM lr c04c6284
PPC460ex PLB DMA engine @0x00_00000100 size 263
new_chan->chan_id 0x0
new_chan->chan->chan_id 0x0
apollo3g_gpio_init: GPIO 1 @ 0xe0000000; GPIO 2 @ 0xe1000000
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Slow work thread pool: Starting up
Slow work thread pool: Ready
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
SGI XFS with security attributes, large block/inode numbers, no debug enabled
msgmni has been set to 492
Cryptodev Interface Loaded
User space CryptoAPI driver v0.1 loaded
async_tx: api initialized (async)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
irq: irq 3 on host /interrupt-controller1 mapped to virtual irq 21
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4ef600300 (irq = 19) is a 16550A
console [ttyS0] enabled
4ef600300.serial: ttyS0 at MMIO 0x4ef600300 (irq = 19) is a 16550
brd: module loaded
sata-dwc 4bffd1800.sata: Gettting DMA channel 1
sata-dwc 4bffd1800.sata: id 0, controller version 1.91
irq: irq 25 on host /interrupt-controller0 mapped to virtual irq 25
sata-dwc 4bffd1800.sata: DMA initialized
sata-dwc 4bffd1800.sata: DMA CFG = 0x00000001
dma_register_interrupt register irq (25)
irq: irq 27 on host /interrupt-controller0 mapped to virtual irq 27
ata4294967295: sata_dwc_port_start: setting burst size in DBTSR: 0x00100010
sata-dwc 4bffd1800.sata: **** GEN II speed rate negotiated
scsi0 : sata-dwc
ata1: SATA max UDMA/133 irq 27
Found: SST 39LF040
4fff80000.nor_flash: Found 1 x8 devices at 0x0 in 8-bit bank
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
Creating 2 MTD partitions on “4fff80000.nor_flash”:
0x000000000000-0x000000020000 : “3genv”
0x000000020000-0x000000080000 : “u-boot”
ndfc 4fff80000.ndfc: failed to get memory
ndfc: probe of 4fff80000.ndfc failed with error -5
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999-2008 Intel Corporation.
PPC 4xx OCP EMAC driver, version 3.54
mal0: descriptor-memory = ocm
irq: irq 6 on host /interrupt-controller2 mapped to virtual irq 22
irq: irq 7 on host /interrupt-controller2 mapped to virtual irq 23
irq: irq 3 on host /interrupt-controller2 mapped to virtual irq 24
irq: irq 4 on host /interrupt-controller2 mapped to virtual irq 26
irq: irq 5 on host /interrupt-controller2 mapped to virtual irq 28
irq: irq 8 on host /interrupt-controller2 mapped to virtual irq 29
irq: irq 12 on host /interrupt-controller2 mapped to virtual irq 31
MAL: Enabled Interrupt Coal TxCnt: 1 RxCnt: 8
TxTimer: 0 RxTimer: 10000
MAL v2 /plb/mcmal, 1 TX channels, 1 RX channels
RGMII /plb/opb/emac-rgmii@ef601500 initialized with MDIO support
TAH /plb/opb/emac-tah@ef601350 initialized
irq: irq 16 on host /interrupt-controller2 mapped to virtual irq 32
irq: irq 20 on host /interrupt-controller2 mapped to virtual irq 33
/plb/opb/emac-rgmii@ef601500: input 0 in RGMII mode
bcm54610_init: before 0x2c8c, after 0x2c8c
bcm54610_init: before 0x0d41, 0x0200; after 0x0d41, 0x0200
eth0: EMAC-0 /plb/opb/ethernet@ef600c00, MAC 00:90:a9:b2:9a:a3
eth0: found BCM54610 Gigabit Ethernet PHY (0x01)
Intel(R) Gigabit Ethernet Network Driver - version 1.3.16-k2
Copyright (c) 2007-2009 Intel Corporation.
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Fusion MPT base driver 3.04.12
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SAS Host driver 3.04.12
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
Initializing USB Mass Storage driver…
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
dwc_otg: version 2.60a 22-NOV-2006
input: rst_button as /class/input/input0
i2c /dev entries driver
irq: irq 2 on host /interrupt-controller0 mapped to virtual irq 34
ibm-iic 4ef600700.i2c: using standard (100 kHz) mode
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
Registered led device: a3g_led
irq: irq 20 on host /interrupt-controller0 mapped to virtual irq 35
AMCC 4xx PKA v0.1 @0x04_00114000 size 16384 IRQ 35
Initializing PKA…
PKA Driver Successfully Initialized
Reading pvr value = 12c41c81
irq: irq 29 on host /interrupt-controller0 mapped to virtual irq 36
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
Interrupt status = 0x00042020
dev status = 0x03087722
ata1.00: ATA-8: WDC WD30EZRS-11J99B1, 80.00A80, max UDMA/133
Interrupt status = 0x00042020
dev status = 0x03087722
ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 1/32)
Interrupt status = 0x00042020
dev status = 0x03087722
ata1.00: configured for UDMA/133
blk_queue_max_hw_segments: set to minimum 1
Interrupt status = 0x00042020
dev status = 0x03087722
scsi 0:0:0:0: Direct-Access ATA WDC WD30EZRS-11J 80.0 PQ: 0 ANSI: 5
Interrupt status = 0x00042020
dev status = 0x03087722
sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: Attached scsi generic sg0 type 0
apm82181-adma: Probing AMCC APM82181 ADMA engines…
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
irq: irq 13 on host /interrupt-controller0 mapped to virtual irq 37
AMCC(R) APM82181 ADMA Engine found [1]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
sda:apm82181 adma1: allocated 512 descriptor slots
irq: irq 14 on host /interrupt-controller0 mapped to virtual irq 38
AMCC(R) APM82181 ADMA Engine found [2]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
apm82181 adma2: allocated 512 descriptor slots
irq: irq 15 on host /interrupt-controller0 mapped to virtual irq 39
AMCC(R) APM82181 ADMA Engine found [3]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
apm82181 adma3: allocated 512 descriptor slots
oprofile: using timer interrupt.
Macsec proc interface Initiliazed
Registered Macsec Interface
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
sda1 sda2 sda3 sda4
NET: Registered protocol family 17
Bridge firewalling registered
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
sd 0:0:0:0: [sda] Attached SCSI disk
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
md: Waiting for all devices to be available before autodetect
md: If you don’t use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 2 and added 2 devices.
md: autorun …
md: considering sda2 …
md: adding sda2 …
md: adding sda1 …
md: created md0
md: bind<sda1>
md: bind<sda2>
md: running: <sda2><sda1>
md0: WARNING: sda2 appears to be on the same physical disk as sda1.
True protection against single-disk failure might be compromised.
raid1: raid set md0 active with 2 out of 2 mirrors
md0: detected capacity change from 0 to 2047803392
md: … autorun DONE.
md0: unknown partition table
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with writeback data mode.
VFS: Mounted root (ext3 filesystem) on device 9:0.
Freeing unused kernel memory: 384k init
Enable EMAC EMI Fix
eth0: link is up, 1000 FDX, pause enabled
eth0: no IPv6 routers present
EXT4-fs (sda4): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda4): mounted filesystem with ordered data mode
Adding 500608k swap on /dev/sda3. Priority:-1 extents:1 across:500608k
svc: failed to register lockdv1 RPC service (errno 97).
eth0: link is down
eth0: link is up, 1000 FDX, pause enabled
------------[cut here]------------
Badness at c026bb2c [verbose debug info unavailable]
NIP: c026bb2c LR: c04ad02c CTR: 00000000
REGS: c828de80 TRAP: 0700 Not tainted (2.6.32.11-svn45595)
MSR: 00029000 <EE,ME,CE> CR: 28044288 XER: 20000000
TASK = c811bc10[1788] ‘nfsd’ THREAD: c828c000
GPR00: 00000001 c828df30 c811bc10 c9ea0c68 00000000 00000000 00020000 c80ece3c
GPR08: 00000000 00000000 c80ecde8 c87ca7cc 48044282 1001b1cc 0ffc0400 00000000
GPR16: 0ffb46c4 0ffbad8c 00000000 00000000 c80ecf74 c06d0000 000dbba0 c80f7d80
GPR24: c87ca7c0 00000003 c80ecd20 00000003 c0698648 88044288 c9ea0c60 c9ea0c74
NIP [c026bb2c] kref_get+0xc/0x24
LR [c04ad02c] svc_recv+0x298/0x790
Call Trace:
[c828df30] [c04acf48] svc_recv+0x1b4/0x790 (unreliable)
[c828df90] [c0176760] nfsd+0xf0/0x174
[c828dfc0] [c003db14] kthread+0x78/0x7c
[c828dff0] [c000df60] kernel_thread+0x4c/0x68
Instruction dump:
409e0010 7c8903a6 4e800421 38000001 7c030378 80010014 38210010 7c0803a6
4e800020 80030000 7c000034 5400d97e <0f000000> 7d201828 31290001 7d20192d
------------[cut here]------------
Kernel BUG at c00a7fdc [verbose debug info unavailable]
Oops: Exception in kernel mode, sig: 5 [#1]
PowerPC 44x Platform
Modules linked in:
NIP: c00a7fdc LR: c03d744c CTR: c04a0738
REGS: c828de10 TRAP: 0700 Tainted: G W (2.6.32.11-svn45595)
MSR: 00029000 <EE,ME,CE> CR: 88044282 XER: 20000000
TASK = c811bc10[1788] ‘nfsd’ THREAD: c828c000
GPR00: 00000001 c828dec0 c811bc10 c81e7ee8 c0777860 00000000 00000001 c804e8a0
GPR08: 00000101 00000043 c0790000 c0690000 48044282 1001b1cc 0ffc0400 00000000
GPR16: 0ffb46c4 0ffbad8c 00000000 00000000 c80ecf74 c06d0000 000dbba0 c80f7d80
GPR24: c87ca7c0 00000003 c80ecd20 00000003 00000004 88044288 00000000 c81e7ee8
NIP [c00a7fdc] iput+0x28/0x90
LR [c03d744c] sock_release+0x98/0x9c
Call Trace:
[c828dec0] [88044288] 0x88044288 (unreliable)
[c828ded0] [c03d744c] sock_release+0x98/0x9c
[c828def0] [c04a0794] svc_sock_free+0x5c/0x8c
[c828df00] [c04ac168] svc_xprt_free+0x4c/0x68
[c828df10] [c026bb08] kref_put+0x54/0x6c
[c828df20] [c04abd58] svc_xprt_put+0x1c/0x2c
[c828df30] [c04ad0a0] svc_recv+0x30c/0x790
[c828df90] [c0176760] nfsd+0xf0/0x174
[c828dfc0] [c003db14] kthread+0x78/0x7c
[c828dff0] [c000df60] kernel_thread+0x4c/0x68
Instruction dump:
38210010 4e800020 9421fff0 7c0802a6 93e1000c 7c7f1b79 90010014 4182005c
801f0110 68000040 7c000034 5400d97e <0f000000> 3c80c06e 3884ae0c 3884001c
—[end trace d9817735e961955b]—
Unable to handle kernel paging request for data at address 0x94220004
Faulting instruction address: 0xc001393c
Oops: Kernel access of bad area, sig: 11 [#2]
PowerPC 44x Platform
Modules linked in:
NIP: c001393c LR: c04a3434 CTR: c04a3410
REGS: c8525db0 TRAP: 0300 Tainted: G D W (2.6.32.11-svn45595)
MSR: 00029000 <EE,ME,CE> CR: 84048288 XER: 00000000
DEAR: 94220004, ESR: 00000000
TASK = c8118910[1789] ‘nfsd’ THREAD: c8524000
GPR00: c04a97c0 c8525e60 c8118910 94220004 c8525ebb 94220003 dc311760 00000000
GPR08: 00000000 c0263064 0000ffff 0affffff 00000000 1001b1cc 0ffc0400 00000000
GPR16: 0ffb46c4 0ffbad8c 00000000 00000000 00000000 00000000 00000000 0000000a
GPR24: 00000000 c93b000c c077788c 00000003 c8525ea8 c0697728 9421fff0 c8525ea8
NIP [c001393c] strcmp+0x8/0x24
LR [c04a3434] ip_map_match+0x24/0x88
Call Trace:
[c8525e60] [c03d8b38] lock_sock_nested+0x90/0xa4 (unreliable)
[c8525e70] [c04a97c0] sunrpc_cache_lookup+0x60/0x184
[c8525e90] [c04a3184] ip_map_lookup+0x108/0x12c
[c8525f00] [c04a3264] svcauth_unix_set_client+0xbc/0x1e8
[c8525f40] [c04a2890] svc_set_client+0x1c/0x2c
[c8525f50] [c049f21c] svc_process+0x5fc/0x78c
[c8525f90] [c017674c] nfsd+0xdc/0x174
[c8525fc0] [c003db14] kthread+0x78/0x7c
[c8525ff0] [c000df60] kernel_thread+0x4c/0x68
Instruction dump:
3884ffff 8c050001 2c000000 4082fff8 38a5ffff 8c040001 2c000000 9c050001
4082fff4 4e800020 38a3ffff 3884ffff <8c650001> 2c830000 8c040001 7c601851
—[end trace d9817735e961955c]—
Unable to handle kernel paging request for data at address 0x94220004
Faulting instruction address: 0xc001393c
Oops: Kernel access of bad area, sig: 11 [#3]
PowerPC 44x Platform
Modules linked in:
NIP: c001393c LR: c04a3434 CTR: c04a3410
REGS: c84ffc80 TRAP: 0300 Tainted: G D W (2.6.32.11-svn45595)
MSR: 00029000 <EE,ME,CE> CR: 84008448 XER: 00000000
DEAR: 94220004, ESR: 00000000
TASK = c82940f0[1793] ‘rpc.mountd’ THREAD: c84fe000
GPR00: c04a97c0 c84ffd30 c82940f0 94220004 c84ffd8b 94220003 dc311760 0afff522
GPR08: 00000000 c0263064 0000ffff 00000000 00000000 1002c764 10024774 10024794
GPR16: 1002477c 10024780 00000002 1001259c 00000000 00000000 1001258c c84ffe10
GPR24: c84ffde8 c84ffdf8 c077788c c84ffdf0 c84ffd78 c0697728 9421fff0 c84ffd78
NIP [c001393c] strcmp+0x8/0x24
LR [c04a3434] ip_map_match+0x24/0x88
Call Trace:
[c84ffd30] [c0697d78] 0xc0697d78 (unreliable)
[c84ffd40] [c04a97c0] sunrpc_cache_lookup+0x60/0x184
[c84ffd60] [c04a3184] ip_map_lookup+0x108/0x12c
[c84ffdd0] [c04a4188] ip_map_parse+0x198/0x26c
[c84ffea0] [c04a7bd4] cache_do_downcall+0xc4/0xe8
[c84ffec0] [c04a86dc] cache_write+0xac/0x110
[c84ffee0] [c00d70ac] proc_reg_write+0x4c/0x70
[c84ffef0] [c00943d0] vfs_write+0xb4/0x188
[c84fff10] [c0094938] sys_write+0x4c/0x90
[c84fff40] [c000e184] ret_from_syscall+0x0/0x3c
Instruction dump:
3884ffff 8c050001 2c000000 4082fff8 38a5ffff 8c040001 2c000000 9c050001
4082fff4 4e800020 38a3ffff 3884ffff <8c650001> 2c830000 8c040001 7c601851
—[end trace d9817735e961955d]—
NFS daemon crashed.
Can you please fix thins?
manually download 1.05.07. You need to install this first before moving to the 02.xx.xx firmwares
First of all, thank you both for replying so soon :smileyvery-happy:
FRAC42 wrote:> Is your drive working fine except for the FW update? No other issues, like WIndows asking for a driver, slow web interface or poor transfer rates?
FRAC,
Yes, the drive works fine now. Initially there was a very slow transfer rate (less than 1Mb/sec), but it works fine now I think (around 10Mb/sec). No other issues that I have seen. My OS is Win 7 btw.
cman548 wrote:
manually download 1.05.07. You need to install this first before moving to the 02.xx.xx firmwares
Cman,
I have tried finding that on WDs website, all I get is the open source .zip file. I am too inexperienced and don’t want to mess around with stuff I don’t know about. If you know of any older links that would be great to be able to download the 1.05.07. deb file 
:smileyvery-happy: IT WORKS!!! :smileyvery-happy:
Finally everything works fine for me and I don’t need to send the drive back.
Unfortunately I can’t tell what exactly was the solution since I did 2 things at the same time.
-
I shut the drive down and disconnected it from both power and the network router. After a night and a working day I reconnected it again.
-
I connected my PC via Gigabit ETN to the router rather than via WLAN.
Result: When I started the web console and found the “new firmware available” message I accepted to do a firmware update. Same as yesterday. The system reacted quite differently, though! A message popped up warning that I should first backup all my data. Not sure that happened yesterday. But I m pretty sure I didn’t see the next warning about loosing My Mio with this update. After accepting that the download started (takes a few seconds, maybe 20 or so), and then the upgrade started. Surprise again - there was a progress bar which was not there yesterday! And the front LED of the disk went blue. The progress bar actually did show some progress. After a few minutes (maybe 3 or 5 or something in that range) an “Update finished - rebooting system” message popped up and soon afterwards everything was done.
My guess is that the lower speed of the wireless network badly interferes with some timeouts or something like this. I doubt that switching off the disk over night did the trick. But I can’t tell for sure.
So give it a try - grab an ethernet cable, switch off wireless and try the update again. Maybe you end up as happy as I now am
FRAC
Strange. That’s because the entire upgrade process is performed by the network drive which downloads the firmware directly into itself and then reporting that to the applications used by the Web UI to show process.
When My MBL went gaga I initiated the update by using SSH to retrieve the firmware (can be download by the PC and stuck in the Publis chare if desitred) and then invoking the script that does the update directly from the command line.
I had to do this because after a reboot BEFORE performing the firmware updater the Web UI went 100% missing. As if the web server within the NAS that operates the Web UI had failed to start, but it did start.
SUCCESS!
Instead of using the dashboard I selected update from the WD quick view window, that installed 01.05.07. Then I just did it again to install the latest firmware :smileyvery-happy:
Anyone know how to get the UI (dashboard) back after installing the new firmware? MBL’s SSH is not enabled so I can’t use the SSH method. The WDsmartware/quickview is not picking up the MBL either. It kept ask me to connect MBL to the local network. However, MBL is connected to the network and I can see its IP on my router. Even typing the MBL’s IP directly in the browser doesn’t work as it displays a blank page. Really regretting updating the firmware now.
Have exactly the same problem as ATY583 ’s. Any ideas ?
thanks
Judging from the posts here, the new firmware has some serious problems. I have also had serious problems.
I have two 2TB MBL drives connected to the same router. One was working fine before firmware upgrade to 020202-020-20110825.deb and is about 4 months old. It has not seen muchuse and has spent the time in sleep mode. The other is brand new and was immediately upgraded to 020202-020. I am configuring these devices from Mac Leopard.
After firmware upgrade, I can find both devices and their file systems using Mac’s finder. The first issue I noticed is that both devices were in continuous disk operation mode even withno other computers or devices on the network. The older unit flashed yellow-red (or perhaps green-red); the new unit blinked green. The disk operations continued even with the MBLs disconnected from the network (ethernet unplugged). The other problem was communication errors on trying to run diagnostics, which I describe below.
I turned the two drives off for 24 hours. I turned them on, unconnected to the router. Status lights are red, as they should be. However, both drives are doing incessant disk operations, noisy and quite warm. The operations began as soon as the disks were fully booted. I then plugged the two drives into the network. The new unit has a continuous blinking green light that seems to correctly reflect the fact that it continued its busy disk operations. The older unit resumed the red-green alternating blinking light (this is not a possibility given in the manual). Both units are accessible and I can open files on them.
Both units are accessible from the dashboard. The dashboard says the status of both units is “good”. On the new unit, I try to run a short diagnostic test but the new unit logouts before it completes the request and is apparently suffering some sort of network disconnect. However, I do not appear to lose my mount point on the Mac. After several tries, it does not log out but I get the error message: “31319 Unknown error. Please ensure you are not facing network connectivity issues and try again.”
On the older unit, I tried to run the short diagnostic test: it proceeds and then gives an error message: “31319 Unknown error. Please ensure you are not facing networkconnectivity issues and try again.” I try to run it again and I get “30400 A bad request was made”. This unit will also logout, but not as frequently. The older unit does not get the proper time from NPT server,so something is wrong with its internet access.
I have downloaded the system status using the support page on the dashboard for both units, but I don’t know what to look for in the logs. It would be helpful if someone could let me know how to enable ssh onthe MBL using my Mac.
Any help would be appreciated, but I think I am dead in the water until a new release of firmware comes out.
jwc
I wonder… In the Samba documentation there is something about if the Samba server is configured as a workgroup master browser then there should not be a second Samba sever configured the same because if there is then the two Samba severs endlessly force elections on who is going to be tbe browse list master.
Could this be reason with both MyBook Lives on the local network?
I can’t test this. I only have one MyBook Live.
I did read that your drives chatter away even with the network cable unplugged. Could that be Twonky goping through the collection of media on the disc and the monitor.io script doing it stuff?
Hi, I’m really tired of that NFS kernel bugs. Can you please switch to the unfs3 user space daemon (lenny) instead of the kernel implementation? That kernel crashes are really unsuitable, because its even impossible to reboot the device remotely when that “Oops” happened. I can see ppl post the same issues for another WD devices, like WDTV. Seems PPC NFS kernel implementation is really unstable.
Actually, the Lunix OS seems to do a good job of keeping an eye on some of the services. When I first encountered the problem I didn’t realise where the problem was because as soon as the Samba service panicked and quit then some watchdog within the MyBook Live noticed and reloaded the Samba service which incidentally made me think the problem was with Microsoft’s SyncToy. It’s when I looked at the logs a week(ish) later I noticed that Samba was having virtual fits.
The system “keeps an eye” on services indeed, but the NFS daemon is running IN-THE-KERNEL, so when it crashes the kernel becomes really unstable. I propose to discard the in-kernel NFS implementation and switch to the unfs3 user-space NFS daemon, which is much more stable and no less in speed. The unfs3 daemon may be taken from lenny distro. Configuration changes are minimal (exports file fix).
I ain’t a Linux Guru but the issue I’m describing is with the Samba service. Does that daemon within the kernel ring out just outside of the kernel ring? I;m asking this because even though (ages ago) Samba was having a dickyfit the Linux OS remained stable at that moment in time.
Allow me to shout:
THIS PRODUCT **bleep** !
Now, the facts. My LAN is built around an Airport Extreme router. Stations are iMac nd MacBookPro, both running updated Snow Leopard.
I’ve bought this unit because I wanted a NAS, not a simple external USB drive. It is 4 months old.
The unit has been working over the last 4 months, but always with bad performance - I mean veeeeery slow access to files (songs and photos, only 200 GB).
All previous firmware updates occurred flawlessly. This last one, however, besides having taken a lot of time to download, got stuck in the beginning of initialization, with a message like “connection error”.
I’m sure no one touched the cables and there was not a power failure, so why “connection error” ?
Now, all I get is a black brick with a beautiful blue light that shines white, from time to time - over the last hours.
Resetting the unit was useless. Dashboard is gone. FINDER doesn’t find the unit, neither IP SCANNER does.
I never liked this product, from installation day. I guess I was fooled by WD brand name. **bleep**.
Should I return it to WD? From Brazil? At whose expense? **bleep**, again.
Sorry for all those “bleeps”, but this unit really “bleeped” me off.
