LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 05-21-2015, 10:25 AM   #1
LoneTiger
LQ Newbie
 
Registered: May 2015
Posts: 10

Rep: Reputation: Disabled
Question GNU RAID 1 "Data volume failed to mount"


I'm using a Western Digital My Book Live DUO network drive with 2x2Tb HD's in RAID 1 configuration. The devices uses Linux GNU to manage the RAID array.
At some point after a reboot the UI returns this error:

"Data volume failed to mount Contact tech support"

I have very little linux knowledge, and trying to get the RAID error fixed so I can access and backup my data on another drive.

Here's the info I have managed to pull so far from the drive via SSH:


dmesg

Code:
login as: root
root@192.168.1.55's password:
Linux LTFileServer 2.6.32.11-svn70860 #1 Thu May 17 13:32:51 PDT 2012 ppc
Disclaimer: SSH provides access to the network device and all its
content, only users with advanced computer networking and Linux experience
should enable it. Failure to understand the Linux command line interface
can result in rendering your network device inoperable, as well as allowing
unauthorized users access to your network. If you enable SSH, do not share
the root password with anyone you do not want to have direct access to all
the content on your network device.

LTFileServer:~# dmesg
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(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 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 0x0d41, 0x0200; after 0x0d41, 0x0200
eth0: EMAC-0 /plb/opb/ethernet@ef600c00, MAC 00:90:a9:b7:10:66
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
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...
ata2.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133
ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 1/32)
irq: irq 13 on host /interrupt-controller0 mapped to virtual irq 41
AMCC(R) APM82181 ADMA Engine found [1]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
apm82181 adma1: allocated 512 descriptor slots
irq: irq 14 on host /interrupt-controller0 mapped to virtual irq 42
AMCC(R) APM82181 ADMA Engine found [2]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
ata1.00: ATA-8: WDC WD20EARX-00PASB0, 27.0CR.7, max UDMA/133
ata1.00: 3907209168 sectors, multi 0: LBA48
ata2.00: configured for UDMA/133
apm82181 adma2: allocated 512 descriptor slots
irq: irq 15 on host /interrupt-controller0 mapped to virtual irq 43
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
ata1.00: configured for UDMA/133
blk_queue_max_hw_segments: set to minimum 1
scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EARX-00P 27.0 PQ: 0 ANSI: 5
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
sd 0:0:0:0: [sda] 3907209168 512-byte logical blocks: (2.00 TB/1.81 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 WD20EARX-00P 51.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
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] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 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
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
 sdb: sdb1 sdb2 sdb3 sdb4
 sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
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 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: 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: Scanned 8 and added 4 devices.
md: autorun ...
md: considering sda2 ...
md:  adding sda2 ...
md:  adding sda1 ...
md:  adding sdb2 ...
md:  adding sdb1 ...
md: created md0
md: bind<sdb1>
md: bind<sdb2>
md: bind<sda1>
md: bind<sda2>
md: running: <sda2><sda1><sdb2><sdb1>
md0: WARNING: sda2 appears to be on the same physical disk as sda1.
md0: WARNING: sdb2 appears to be on the same physical disk as sdb1.
True protection against single-disk failure might be compromised.
raid1: raid set md0 active with 4 out of 4 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 ordered data mode.
VFS: Mounted root (ext3 filesystem) on device 9:0.
Freeing unused kernel memory: 448k init
Disable EMAC EMI Fix
eth0: link is up, 1000 FDX, pause enabled
eth0: no IPv6 routers present
md: md2 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 512741376
md: md3 stopped.
md: bind<sdb4>
md: bind<sda4>
raid1: raid set md3 active with 1 out of 2 mirrors
md3: detected capacity change from 0 to 1995774484480
md: recovery of RAID array md3
md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
md: using 2048k window, over a total of 1948998520 blocks.
md: resuming recovery of md3 from checkpoint.
 md3: unknown partition table
FAT: invalid media value (0x00)
VFS: Can't find a valid FAT filesystem on dev md3.
 md2: unknown partition table
Adding 500544k swap on /dev/md2.  Priority:-1 extents:1 across:500544k
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 delayalloc with ioctl loaded at d4490000
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: cannot remove active disk sda1 from md0 ...
md: cannot remove active disk sda2 from md0 ...
md: cannot remove active disk sdb1 from md0 ...
md: cannot remove active disk sdb2 from md0 ...
Calling led_set_blink with value x
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
dwc_otg: version 2.60a 22-NOV-2006
dwc_otg: Shared Tx FIFO mode
dwc_otg: Using DMA mode
dwc_otg dwc_otg.0: DWC OTG Controller
dwc_otg dwc_otg.0: new USB bus registered, assigned bus number 1
dwc_otg dwc_otg.0: irq 28, io mem 0x00000000
dwc_otg: Init: Port Power? op_state=1
dwc_otg: Init: Power Port (0)
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: DWC OTG Controller
usb usb1: Manufacturer: Linux 2.6.32.11-svn70860 dwc_otg_hcd
usb usb1: SerialNumber: dwc_otg.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
md: md3: recovery done.
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sda4
 disk 1, wo:0, o:1, dev:sdb4
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
usb 1-1: new high speed USB device using dwc_otg and address 2
usb 1-1: New USB device found, idVendor=0781, idProduct=5581
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: Ultra
usb 1-1: Manufacturer: SanDisk
usb 1-1: SerialNumber: 4C530123091014123423
usb 1-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver libusual
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 2:0:0:0: [sdc] 62566488 512-byte logical blocks: (32.0 GB/29.8 GiB)
usb-storage: device scan complete
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Attached SCSI removable disk
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
md: cannot remove active disk sda1 from md0 ...
md: cannot remove active disk sda2 from md0 ...
md: cannot remove active disk sdb1 from md0 ...
md: cannot remove active disk sdb2 from md0 ...
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
LTFileServer:~#
LTFileServer:~#
mount

Code:
LTFileServer:~# mount
/dev/md0 on / type ext3 (rw,noatime,nodiratime,barrier=1)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755,size=5M)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,size=5M)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
tmpfs on /tmp type tmpfs (rw,size=100M)
/var/log on /var/log.hdd type none (rw,bind)
ramlog-tmpfs on /var/log type tmpfs (rw,size=20M)
/DataVolume/cache on /CacheVolume type none (rw,bind)
none on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/sdc1 on /var/media/Ultra type vfat (rw,utf8,errors=continue,fmask=013,dmask=002,uid=99,gid=1000)
LTFileServer:~#
LTFileServer:~#
parted -l

Code:
LTFileServer:~# parted -l
Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system     Name     Flags
 3      15.7MB  528MB   513MB   linux-swap(v1)  primary  raid
 1      528MB   2576MB  2048MB  ext3            primary  raid
 2      2576MB  4624MB  2048MB  ext3            primary  raid
 4      4624MB  2000GB  1996GB                  primary  raid


Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system     Name     Flags
 3      15.7MB  528MB   513MB   linux-swap(v1)  primary  raid
 1      528MB   2576MB  2048MB  ext3            primary  raid
 2      2576MB  4624MB  2048MB  ext3            primary  raid
 4      4624MB  2000GB  1996GB                  primary  raid


Model: SanDisk Ultra (scsi)
Disk /dev/sdc: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      11.2MB  32.0GB  32.0GB  primary  fat32        lba


Model: Unknown (unknown)
Disk /dev/md0: 2048MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2048MB  2048MB  ext3


Model: Unknown (unknown)
Disk /dev/md2: 513MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system     Flags
 1      0.00B  513MB  513MB  linux-swap(v1)


Error: /dev/md3: unrecognised disk label

LTFileServer:~#
LTFileServer:~#
LTFileServer:~#
From what I have managed to put together by reading left and right the RAID 1 is md0 made from sda and sdb (Hard drives)
And the problem seems to be something on the superblock being corrupted. but if I try to use fsck command to attempt to fix it it...

Code:
LTFileServer:~# fsck /dev/md0
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/md0 is mounted.

WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.

Do you really want to continue (y/n)? no

check aborted.
LTFileServer:~#
All help and advise is really welcome.

Last edited by LoneTiger; 05-22-2015 at 04:38 PM.
 
Old 05-21-2015, 07:45 PM   #2
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 2,448

Rep: Reputation: Disabled
The superblock in question is the md superblock, the metadata describing the RAID setup, not the filesystem superblock. You should absolutely not run fsck on any of the devices/partitions!

It looks like this device uses the Linux md driver to create RAID volumes, and it also seems to use the older v0.90 superblock format. This puts the RAID superblock at the very end of each partition, rather than at the beginning. For RAID 1 volumes, that means it should be possible to mount one of the partitions directly and access the file system.

What did your RAID setup look like before the crash? The dmesg log contains some troubling messages, claiming that the RAID member partitions are residing on the same disk, which means you'd have no redundancy. That doesn't sound quite right, and might mean that the RAID superblock is badly damaged.

You should probably leave the device alone until you've had a talk with WD Technical Support. If the device is faulty, trying to access the partitions using the built-in OS could cause further damage. It would be better to remove one or both drives and connect them to another system running a reasonable recent version of Linux.
 
Old 05-21-2015, 08:23 PM   #3
LoneTiger
LQ Newbie
 
Registered: May 2015
Posts: 10

Original Poster
Rep: Reputation: Disabled
Question

I do not know what the RAID setup looked like earlier, I learned it had SSH access after it returned mounting error on the device UI and managed to get the logs above, trying to get as much info as possible from it.
At the moment I have not executed any repair command like fsck or the like, still looking for information or a way to try salvage my data.

So far my talks with WD support have given me a free extended warranty to replace the device but not to salvage my data from it. (Which makes me think its their default go-to response)
Hoping to get more support from them but its very slow.

Some of the responses I have seen on forums also suggest connecting hard drives to a linux-running computer. Isn't the data suposed to be accessible from either HD in a RAID 1 configuration?

I can probably get some linux installation on a computer but what version of linux would be a good idea? I have seen Red-hat, Fedora and CentOS
 
Old 05-22-2015, 04:03 PM   #4
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 2,448

Rep: Reputation: Disabled
Quote:
Originally Posted by LoneTiger View Post
Some of the responses I have seen on forums also suggest connecting hard drives to a linux-running computer. Isn't the data suposed to be accessible from either HD in a RAID 1 configuration?
It is, and at this point I think that's the best way to proceed.

You don't even need to find a system running Linux. Just use a Live CD/DVD/USB stick.
 
Old 05-22-2015, 04:16 PM   #5
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,508

Rep: Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102
Quote:
Originally Posted by LoneTiger View Post
Isn't the data suposed to be accessible from either HD in a RAID 1 configuration?
Yes, but it really helps to know what the raid configuration is supposed to be before you go trying to recover it. Your system has three RAID arrays, which is why this is so complicated. From what I can tell looking at your output:

md0 is a 4-device RAID 1 consisting of sda1, sda2, sdb1, sdb2. This contains the root filesystem and it appears to be working
md2 is a 2-device RAID 1 consisting of sda3, sdb3. This contains your swap and it appears to be working
md3 is a 2-device RAID 1 consisting of sda4, sdb4. This contains ??? and is the one experiencing problems (see below)
Code:
VFS: Can't find a valid FAT filesystem on dev md3
and
Code:
Error: /dev/md3: unrecognised disk label
What does your /etc/fstab look like, and what is the output of:
Code:
mdadm --detail /dev/md0
mdadm --detail /dev/md2
mdadm --detail /dev/md3
Did you experience any power outages or anything of the sort when this started?

Last edited by suicidaleggroll; 05-22-2015 at 04:18 PM.
 
Old 05-22-2015, 04:47 PM   #6
LoneTiger
LQ Newbie
 
Registered: May 2015
Posts: 10

Original Poster
Rep: Reputation: Disabled
Question

Through SSH the My Book Live Duo drive returns the following:

mdadm --detail /dev/md0
mdadm --detail /dev/md2
mdadm --detail /dev/md3


Code:
LTFileServer:~#
LTFileServer:~#
LTFileServer:~#
LTFileServer:~# mdadm --detail /dev/md0
/dev/md0:
        Version : 0.90
  Creation Time : Wed Jan 28 03:00:53 2015
     Raid Level : raid1
     Array Size : 1999808 (1953.27 MiB 2047.80 MB)
  Used Dev Size : 1999808 (1953.27 MiB 2047.80 MB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri May 22 16:39:05 2015
          State : clean, degraded
 Active Devices : 3
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 1

           UUID : 6cc78f11:e60b2d09:6309c37f:74049cd1 (local to host LTFileServer)
         Events : 0.7228

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8        1        1      active sync   /dev/sda1
       2       8       18        2      active sync   /dev/sdb2
       4       8        2        3      spare rebuilding   /dev/sda2
LTFileServer:~#
LTFileServer:~#
LTFileServer:~# mdadm --detail /dev/md2
/dev/md2:
        Version : 1.0
  Creation Time : Wed Dec 31 18:09:46 1969
     Raid Level : raid1
     Array Size : 500724 (489.07 MiB 512.74 MB)
  Used Dev Size : 500724 (489.07 MiB 512.74 MB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Fri May 22 16:38:03 2015
          State : clean, degraded
 Active Devices : 1
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 1

           Name : MyBookLiveDuo:2
           UUID : ff212100:102164c7:d017c1b8:c595e2ba
         Events : 70907

    Number   Major   Minor   RaidDevice State
       2       8        3        0      spare rebuilding   /dev/sda3
       1       8       19        1      active sync   /dev/sdb3
LTFileServer:~#
LTFileServer:~#
LTFileServer:~# mdadm --detail /dev/md3
/dev/md3:
        Version : 1.0
  Creation Time : Mon Apr 30 17:44:34 2012
     Raid Level : raid1
     Array Size : 1948998520 (1858.71 GiB 1995.77 GB)
  Used Dev Size : 1948998520 (1858.71 GiB 1995.77 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Fri May 22 16:39:27 2015
          State : clean, degraded, recovering
 Active Devices : 1
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 1

 Rebuild Status : 2% complete

           Name : T3LFileServer:3
           UUID : f065311c:f71ea485:dc3d3e70:89003bc1
         Events : 1259089

    Number   Major   Minor   RaidDevice State
       3       8        4        0      spare rebuilding   /dev/sda4
       2       8       20        1      active sync   /dev/sdb4
LTFileServer:~#
Note: It may say "Rebuilding" but that is because I rmeoved the hard drives to test for errors using one of WD's diagnostics tools. (No repairs of any kind just checkup)
Hard drives appear fine physically.

Quote:
Yes, but it really helps to know what the raid configuration is supposed to be before you go trying to recover it. Your system has three RAID arrays, which is why this is so complicated. From what I can tell looking at your output:

md0 is a 4-device RAID 1 consisting of sda1, sda2, sdb1, sdb2. This contains the root filesystem and it appears to be working
md2 is a 2-device RAID 1 consisting of sda3, sdb3. This contains your swap and it appears to be working
md3 is a 2-device RAID 1 consisting of sda4, sdb4. This contains ??? and is the one experiencing problems (see below)
I cannot say why is this the case, the UI only gives an option to activate RAID 1 and it builds the array but I have no idea why it would build more than 1 array.

Quote:
Did you experience any power outages or anything of the sort when this started?
Sometimes, small power outages, I noticed a problem when trying to delete some of the files via windows computer--mapped network drive pointing to this device, it did not delete them but also did not throw any errros. I rebooted the device via UI and then the crap hit the fan.

In my limited experience any linux computer that is not rebooted every few days begins to act up.
 
Old 05-22-2015, 05:19 PM   #7
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 2,448

Rep: Reputation: Disabled
Quote:
Originally Posted by LoneTiger View Post
In my limited experience any linux computer that is not rebooted every few days begins to act up.
Please don't tell my servers, which typically have an uptime of 200+ days.

If you have to reboot every so often just to keep things running, there's something seriously wrong with either the hardware or the software.
 
Old 05-22-2015, 05:32 PM   #8
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,508

Rep: Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102
So it looks like the RAID arrays are fine, or at least they think they're fine. This means the filesystem on md3, not md3 itself, is the problem. This is the type of failure that RAID does not protect you from. If something happens to corrupt the filesystem, the RAID software will happily sync that corruption to both drives.

You should start by using some recovery software (testdisk/photorec) to grab as much data as possible before you start any fsck-type recovery process.

Quote:
Originally Posted by LoneTiger
In my limited experience any linux computer that is not rebooted every few days begins to act up.
Your experience is quite odd...most of my Linux systems stay up for years before they're rebooted, usually due to a power outage.
 
Old 05-22-2015, 05:56 PM   #9
LoneTiger
LQ Newbie
 
Registered: May 2015
Posts: 10

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by suicidaleggroll View Post
You should start by using some recovery software (testdisk/photorec) to grab as much data as possible before you start any fsck-type recovery process.
Downloading testdisk and photorec to my windows computer to try them out and attempt to salvage as much data I can from the book duo.
 
Old 05-22-2015, 07:26 PM   #10
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 15,721

Rep: Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120
Let's see /etc/fstab. Personally I don't reckon I would futze with any of the disks while they are rebuilding.
Taking them out (while powered down) shouldn't force a rebuild if you put them back in the same slots.
 
Old 05-22-2015, 08:51 PM   #11
LoneTiger
LQ Newbie
 
Registered: May 2015
Posts: 10

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by syg00 View Post
Let's see /etc/fstab. Personally I don't reckon I would futze with any of the disks while they are rebuilding.
Taking them out (while powered down) shouldn't force a rebuild if you put them back in the same slots.
As requested: /etc/fstab

Code:
LTFileServer:~# cat /etc/fstab
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0

## found that Access DLNA can sometimes temporarily use up to 70M of the /tmp space
## increasing to 100M maximum
tmpfs /tmp tmpfs rw,size=100M 0 0

/dev/md0 / ext3 defaults,noatime,nodiratime,barrier=1 0 0
LTFileServer:~#
Not sure why the UI says its rebuilding but gonna wait for it to finish before powering down and trying testdisk/photorec
 
Old 05-22-2015, 09:04 PM   #12
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,508

Rep: Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102Reputation: 2102
No md3? Where is all of your data stored? md0 is only 2GB
 
Old 05-22-2015, 09:43 PM   #13
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 15,721

Rep: Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120
Do you have a /etc/exports ?.
 
Old 05-22-2015, 10:17 PM   #14
LoneTiger
LQ Newbie
 
Registered: May 2015
Posts: 10

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by suicidaleggroll View Post
No md3? Where is all of your data stored? md0 is only 2GB
Its a Western Digital My book Live DUO network drive, it is a 2x2Tb RAID 1 unit and from what I can gather it runs GNU Linux to manage the filesystem and the RAID 1 array. The drive terminal is accessed via SSH, using putty for that but for copying files and such its normal windows "map network drive"

Quote:
Originally Posted by syg00
Do you have a /etc/exports ?.

/etc/exports

Code:
LTFileServer:~# cat /etc/exports
# Use guest user (uid 500) for nfs guest.  This is restricted from private
# shares by trustees.
#
/nfs *(rw,all_squash,sync,no_subtree_check,insecure,anonuid=500,anongid=1000)
LTFileServer:~#
 
Old 05-22-2015, 10:39 PM   #15
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 15,721

Rep: Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120Reputation: 2120
And /etc/samba/smb.conf ?.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
WD MyBook Live Duo - Raid 0 fails to mount data volume (can't find superblocks) gilsonsjc Linux - Hardware 3 06-08-2014 04:17 PM
NTFS signature is missing, trying to mount RAID-5 volume ofuser Linux - Hardware 4 10-15-2010 02:21 AM
Unable to mount additional harddrive from a RAID volume system. andrei_r20 Linux - Server 3 04-10-2010 02:04 AM
upgrade system with lvm on software raid-1 data volume w/o losing data BinWondrin Linux - General 1 01-13-2009 03:25 PM
Need to mount LVM volume and save Data -- Recovering from power loss. chuckcom Linux - General 1 02-09-2008 07:57 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 04:45 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration