Experiencing access issue on MBLD from any device

I experience power outage yesterday & since then I’m been experiencing access issue on my MBLD from any device (Windows 7 x64 pcs, using my cloud app on iPad & andriod mobile phone). 

Once MBLD rebooted & initialized, it was accessible for a few minutes, afterwards it became inaccessible. Wasn’t able to browse Network Shares or access the UI through a browser. I reset the MBLD a few times, I experienced the same issue.

The WD quick view (WD Smartware program) is still able to find device, however stopped providing some information e.g. Used - currently displaying 0%, but there are files on the MBLD.

I followed guide on how to Factory Restore the MBLD using SSH.  [GUIDE] Fix Dashboard Errors 3xxxx

Once I completed the process, I was able to access the MBLD. Everything seemed to be fine, however the response time for browsing the network shares was slower than usual. But I’m just happy to be able to access my files.

This morning the MBL Duo became inaccessible. As time goes by, the MBD became accessible again, after a few minutes it became inaccessible. This issue is constantly occurring.

I’m still able to ping the MBLD when its accessible & inaccessible. 

I installed WD Discovery after it was recommending in the forum topics. It is able to find MBL Duo when it’s accessible & inaccessible. If I’m able to access the MBL Duo, I can map or browse the network shares using WD Discovery. But when the MBL Duo becomes inaccessible those two options are disabled.

A new issue I’m experiencing is when the MBLD is inaccessible, I have no SSH access. Even though I’m able to ping the MBLD. Once the MBLD is accessible I have SSH access. I’m not sure if that provides any useful information.

I spent time searching on the forum & unable to find topic with someone experiencing the same issues. Do I repeat the guide on how to Factory Restore the MBLD using SSH? Is there another process I need to do to resolve this issue?

Thanks in advance.

Have you performed a drive health test while the unit is accessible? It is possible the issues you are experiencing are related to a physical consequence of the power outage affecting certain components. If so, you may need to replace the device.

Regards,

Thank you for spending time to read about my situation & provide your feedback Trancer.

Unfortunately the device isn’t accessible long enough for me to run a diagnostic test. I think you are correct on the physical damage. I’m under the impression the MBLD case is damaged. According to the UI, the hard drives are in good health.

I have ordered a SATA docking station, access the hard drives from there. UI, WD SmartShare & SSH still pick up my files.

My stupid question to the community is do I send in the MBLD case to WD & ask them to assist or do I find a replacement case? My hard drives are WD30EZRS, I’m not sure which WD cases support those drives. I have looked My Cloud EX2 on the website, but my hard drives are not listed on the compatibility list.

Unfortunately at this moment WD does not feature case replacements for the WD My Book Live Duo, however, maybe you should try contacting WD’s Technical Support about this. You can do so either by phone or email.

To Contact WD for Technical Support
http://support.wdc.com/contact/index.asp?lang=en

Support by Country
http://support.wdc.com/country/index.asp

Regards,

Thanks for your feedback & assisting me with my issue. Thank you for links for WD Technical Support. I did contact WD & explained my situation to them. You were correct, they are unable to provide case replacements.

After doing some additional investigation in SSH, I discovered there is an issue with DHCP on my MBLD. Originally I was using DHCP instead of Static IP Address. From my understand (minimal), the renewal process for DHCP was failing, causing my MBLD being inaccessible. The power surge was misleading the cause of my issue. 

I was suggested by a friend to change from DHCP to Static IP Address. Once I changed to Static IP Address, the issue seem to be temporary resolved.

Due to the Factory Restore I did on my MBLD, I needed to recreate my shares. Unfortunately I’m unable to create any shared folders due to this error code: create_share_0. I will contact WD Technical Support to provide additional information on that error. Unless someone from the community can share some light on that error code.

This error has caused my MBLD being inaccessible again. I’m currently experiencing the same issues as before. I redid the Factory Restore & changed to Static IP Address. However this fix is not working anymore.

I’m completely clueless on the next steps I need to resolve this issue.

I have pasted below the boot-time messages for MBLD

MyBookLiveDuo:~# dmesg
t module.
irq: irq 1 on 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 c04d50c4
PPC460ex PLB DMA engine @0x00_00000100 size 263
new_chan->chan_id 0x0
new_chan->chan->chan_id 0x0
irq: irq 28 on host /interrupt-controller2 mapped to virtual irq 28
irq: irq 26 on host /interrupt-controller1 mapped to virtual irq 26
irq: irq 12 on host /interrupt-controller0 mapped to virtual irq 21
apollo3g_gpio_init: GPIO 1 @ 0xe0000000; GPIO 2 @ 0xe1000000
Installing knfsd (copyright © 1996 okir@monad.swb.de).
Slow work thread pool: Starting up
Slow work thread pool: Ready
NTFS driver 2.1.29 [Flags: R/O].
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.13)
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 22
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 4bffd1000.sata: Gettting DMA channel 0
sata-dwc 4bffd1000.sata: id 0, controller version 1.91
irq: irq 25 on host /interrupt-controller0 mapped to virtual irq 25
sata-dwc 4bffd1000.sata: DMA initialized
sata-dwc 4bffd1000.sata: DMA CFG = 0x00000001
dma_register_interrupt register irq (25)
irq: irq 26 on host /interrupt-controller0 mapped to virtual irq 23
ata4294967295: sata_dwc_port_start: setting burst size in DBTSR: 0x00100010
sata-dwc 4bffd1000.sata: **** GEN II speed rate negotiated
scsi0 : sata-dwc
ata1: SATA max UDMA/133 irq 23
sata-dwc 4bffd1800.sata: Gettting DMA channel 1
sata-dwc 4bffd1800.sata: id 0, controller version 1.91
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
scsi1 : sata-dwc
ata2: 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® PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright © 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 24
irq: irq 7 on host /interrupt-controller2 mapped to virtual irq 29
irq: irq 3 on host /interrupt-controller2 mapped to virtual irq 31
irq: irq 4 on host /interrupt-controller2 mapped to virtual irq 32
irq: irq 5 on host /interrupt-controller2 mapped to virtual irq 33
irq: irq 8 on host /interrupt-controller2 mapped to virtual irq 34
irq: irq 12 on host /interrupt-controller2 mapped to virtual irq 35
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 36
irq: irq 20 on host /interrupt-controller2 mapped to virtual irq 37
/plb/opb/emac-rgmii@ef601500: input 0 in RGMII mode
bcm54610_init: before 0x2c8c, after 0x2c8c
bcm54610_init: before 0x01e1, 0x0200; after 0x0141, 0x0200
eth0: EMAC-0 /plb/opb/ethernet@ef600c00, MAC 00:90:a9:b6:9e:12
eth0: found BCM54610 Gigabit Ethernet PHY (0x01)
Intel® Gigabit Ethernet Network Driver - version 1.3.16-k2
Copyright © 2007-2009 Intel Corporation.
tun: Universal TUN/TAP device driver, 1.6
tun: © 1999-2004 Max Krasnyansky maxk@qualcomm.com
Fusion MPT base driver 3.04.12
Copyright © 1999-2008 LSI Corporation
Fusion MPT SAS Host driver 3.04.12
input: rst_button as /devices/virtual/input/input0
i2c /dev entries driver
irq: irq 2 on host /interrupt-controller0 mapped to virtual irq 38
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 39
AMCC 4xx PKA v0.1 @0x04_00114000 size 16384 IRQ 39
Initializing PKA…
PKA Driver Successfully Initialized
Reading pvr value = 12c41c82
irq: irq 29 on host /interrupt-controller0 mapped to virtual irq 40
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
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
apm82181-adma: Probing AMCC APM82181 ADMA engines…
irq: irq 13 on host /interrupt-controller0 mapped to virtual irq 41
AMCC® APM82181 ADMA Engine found [1]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
ata2.00: ATA-8: WDC WD30EZRS-00J99B0, 80.00A80, max UDMA/133
ata2.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 1/32)
apm82181 adma1: allocated 512 descriptor slots
irq: irq 14 on host /interrupt-controller0 mapped to virtual irq 42
AMCC® 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 43
AMCC® APM82181 ADMA Engine found [3]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
apm82181 adma3: allocated 512 descriptor slots
ata2.00: configured for UDMA/133
oprofile: using timer interrupt.
Macsec proc interface Initiliazed
Registered Macsec Interface
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: © 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
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
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
ata1.00: ATA-8: WDC WD30EZRS-00J99B0, 80.00A80, max UDMA/133
ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 1/32)
ata1.00: configured for UDMA/133
blk_queue_max_hw_segments: set to minimum 1
scsi 0:0:0:0: Direct-Access ATA WDC WD30EZRS-00J 80.0 PQ: 0 ANSI: 5
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
blk_queue_max_hw_segments: set to minimum 1
scsi 1:0:0:0: Direct-Access ATA WDC WD30EZRS-00J 80.0 PQ: 0 ANSI: 5
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
sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
sd 1:0:0:0: [sdb] 4096-byte physical blocks
sd 1:0:0:0: Attached scsi generic sg1 type 0
sda:
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
sdb: sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
sdb1 sdb2 sdb3 sdb4
sd 1:0:0:0: [sdb] Attached SCSI disk
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: invalid raid superblock magic on sda3
md: sda3 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda4
md: sda4 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sdb3
md: sdb3 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sdb4
md: sdb4 does not have a valid v0.90 superblock, not importing!
md: Scanned 8 and added 4 devices.
md: autorun …
md: considering sdb2 …
md: adding sdb2 …
md: adding sdb1 …
md: adding sda2 …
md: adding sda1 …
md: created md1
md: bind
md: bind
md: bind
md: bind
md: running:
md1: WARNING: sdb2 appears to be on the same physical disk as sdb1.
md1: WARNING: sda2 appears to be on the same physical disk as sda1.
True protection against single-disk failure might be compromised.
raid1: md1 is not clean – starting background reconstruction
raid1: raid set md1 active with 4 out of 4 mirrors
md1: detected capacity change from 0 to 2047803392
md: … autorun DONE.
md1:
md: resync of RAID array md1
md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
md: using 2048k window, over a total of 1999808 blocks.
unknown partition table
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on md1, internal journal
ext3_orphan_cleanup: deleting unreferenced inode 50140
EXT3-fs: md1: 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) on device 9:1.
Freeing unused kernel memory: 448k init
sata-dwc 4bffd1000.sata: RX DMA PENDINGING
sata-dwc 4bffd1000.sata: dma_dwc_xfer_setup: dma channel unavailable
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:c0:0f/00:00:00:00:00/e0 tag 0 dma 65536 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
ata1.00: configured for UDMA/133
ata1.00: device reported invalid CHS sector 0
ata1: EH complete
sata-dwc 4bffd1000.sata: sata_dwc_isr intr with no active qc qc=(null)
Disable EMAC EMI Fix
eth0: link is up, 1000 FDX, pause enabled
eth0: no IPv6 routers present
sata-dwc 4bffd1000.sata: RX DMA PENDINGING
sata-dwc 4bffd1000.sata: dma_dwc_xfer_setup: dma channel unavailable
sata-dwc 4bffd1000.sata: error interrupt err_reg=0x00000001
sata-dwc 4bffd1000.sata: dma_dwc_terminate_dma terminate DMA on channel=0 enable d=0
ata1: Detect errors: ERRE
sata-dwc 4bffd1000.sata: Detect Internal host adapter error
sata-dwc 4bffd1000.sata: dma_dwc_terminate_dma terminate DMA on channel=0 enable d=0
ata1: Freeze port with 1 QCs aborted
ata1.00: exception Emask 0x20 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: irq_stat 0x040000c8
ata1.00: failed command: WRITE DMA
ata1.00: cmd ca/00:80:00:ee:51/00:00:00:00:00/e0 tag 0 dma 65536 out
res d1/40:80:00:ee:51/00:00:00:00:00/e0 Emask 0x22 (host bus error)
ata1.00: status: { Busy }
ata1.00: error: { UNC }
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
ata1.00: configured for UDMA/133
ata1: EH complete
sata-dwc 4bffd1000.sata: RX DMA PENDINGING
sata-dwc 4bffd1000.sata: dma_dwc_xfer_setup: dma channel unavailable
sata-dwc 4bffd1000.sata: error interrupt err_reg=0x00000001
sata-dwc 4bffd1000.sata: dma_dwc_terminate_dma terminate DMA on channel=0 enable d=0
ata1: Detect errors: ERRE
sata-dwc 4bffd1000.sata: Detect Internal host adapter error
sata-dwc 4bffd1000.sata: dma_dwc_terminate_dma terminate DMA on channel=0 enable d=0
ata1: Freeze port with 1 QCs aborted
ata1.00: exception Emask 0x20 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: irq_stat 0x040000c8
ata1.00: failed command: WRITE DMA
ata1.00: cmd ca/00:80:80:ff:15/00:00:00:00:00/e0 tag 0 dma 65536 out
res d1/40:80:80:ff:15/00:00:00:00:00/e0 Emask 0x22 (host bus error)
ata1.00: status: { Busy }
ata1.00: error: { UNC }
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
ata1.00: configured for UDMA/133
ata1: EH complete
md: md3 stopped.
md: bind
md: bind
md3: detected capacity change from 0 to 5991936540672
md3: unknown partition table
EXT4-fs (md3): warning: maximal mount count reached, running e2fsck is recommend ed
EXT4-fs (md3): recovery complete
EXT4-fs (md3): mounted filesystem with ordered data mode
JBD: barrier-based sync failed on md3-8 - disabling barriers
ufsd: bad vermagic: kernel tainted.
Disabling lock debugging due to kernel taint
ufsd: module license ‘unspecified’ taints kernel.
ufsd: driver 8.5 (NTFS4LINUX_U85_014_S[2011-09-15-11:41:06]) LBD=ON with delayal loc with ioctl loaded at d2720000
NTFS read/write support included
Big endian platform
Hfs+/HfsX read/write support included
Built_for__WD_APM_82181_2011-08-09_sec

svc: failed to register lockdv1 RPC service (errno 97).
md: md0 stopped.
md: cannot remove active disk sda1 from md1 …
md: cannot remove active disk sda2 from md1 …
md: cannot remove active disk sdb1 from md1 …
md: cannot remove active disk sdb2 from md1 …