Failed to mount volume

hello

i ahev a 2x2TB mirrored My Book World Edition II with above error message

if i login into ssh and do cat /proc.mdstat it shows md2 is inactive which seems to correlate…but i dont really know what to do to fix this issue…restart et al doesnt seem to do much…not sure what i should do…similar post to this dont seem to go anywhere from what i can see

any help or suggestion ? thanks inadnace

cheers

david

some info below taken from SSH but not really sure what it means other than probalem with md2 being inactive !

~ $ cat /proc/mdstat
Personalities : [linear] [raid0] [raid1]
md2 : inactive sda40
      1950277343 blocks super 1.2

md1 : active raid1 sdb2[0] sda2[1]
      256896 blocks [2/2] [UU]

md3 : active raid1 sdb3[0] sda3[1]
      987904 blocks [2/2] [UU]

md0 : active raid1 sdb1[0] sda1[1]
      1959872 blocks [2/2] [UU]

unused devices:
~ $ mdadm --assemble --scan
mdadm: No arrays found in config file or automatically
~ $ mdadm --stop /dev/md2
mdadm: error opening /dev/md2: Permission denied
~ $ su
-sh: su: not found
~ $ pwd
/shares
~ $
~ $
~ $ adadm
-sh: adadm: not found
~ $ dmesg
pport DPO or FUA
 sdb: sdb1 sdb2 sdb3 sdb4
sd 1:0:0:0: [sdb] Attached SCSI disk
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
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 sdb4
md: sdb4 does not have a valid v0.90 superblock, not importing!
md: Scanned 8 and added 6 devices.
md: autorun …
md: considering sdb3 …
md:  adding sdb3 …
md: sdb2 has different UUID to sdb3
md: sdb1 has different UUID to sdb3
md:  adding sda3 …
md: sda2 has different UUID to sdb3
md: sda1 has different UUID to sdb3
md: created md3
md: bind
md: bind
md: running:
raid1: raid set md3 active with 2 out of 2 mirrors
raid1 using hardware RAID 0x00000001
md: considering sdb2 …
md:  adding sdb2 …
md: sdb1 has different UUID to sdb2
md:  adding sda2 …
md: sda1 has different UUID to sdb2
md: created md1
md: bind
md: bind
md: running:
raid1: raid set md1 active with 2 out of 2 mirrors
raid1 using hardware RAID 0x00000001
md: considering sdb1 …
md:  adding sdb1 …
md:  adding sda1 …
md: created md0
md: bind
md: bind
md: running:
raid1: raid set md0 active with 2 out of 2 mirrors
raid1 using hardware RAID 0x00000001
md: … autorun DONE.
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).
Freeing init memory: 108K
Adding 256888k swap on /dev/md1.  Priority:-1 extents:1 across:256888k
Registered led device: oxnas-wd810-leds:switch
Registered led device: oxnas-wd810-leds:state
Registered led device: oxnas-wd810-leds:activity
Registered led device: oxnas-wd810-leds:capacity
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on md3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Probing for Synopsis GMAC, unit 0
eth0: PHY is LSI ET1011C
eth0: GMAC ver = 51, vendor ver = 17 at 0xe8000000, IRQ 8
eth0: Found PHY at address 1, type 0x0282f014 -> 10/100/1000
eth0: Ethernet addr: 00:90:a9:71:20:b3
thermAndFan: initializing - ox810
Power button driver registered
Recovery button driver registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Initializing USB Mass Storage driver…
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
10 Dec 2004 USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver@e7000000 Device ID                                                                              register 42fa05
oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
eth0: PHY is LSI ET1011C
oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
oxnas-ehci oxnas-ehci.0: irq 7, io mem 0x00000000
oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
ufsd: module license ‘Commercial product’ taints kernel.
ufsd: driver 8.1 (000_A) LBD=ON loaded at bf050000
NTFS read/write support included
Hfs+/HfsX read/write support included
OXNAS bit-bash I2C driver initialisation OK
rtc-ds1307: probe of 0-0068 failed with error -5
CoPro: Programming start address as 0x9801e000 (basic adr = 0x9801e000)
eth0: LSI ET1011C PHY no Rx clk workaround start
Resetting GMAC
eth0: LSI ET1011C PHY no Rx clk workaround end
GMAC reset complete
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Installing knfsd (copyright © 1996 okir@monad.swb.de).
oxnas_wd810_leds_state state=9
eth0: PHY is LSI ET1011C
eth0: link down
eth0: link up, 1000Mbps, full-duplex, using pause, lpa 0xCDE1
oxnas_wd810_leds_state state=10
md: md2 stopped.
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd c8/00:08:c8:c9:62/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:ca:c9:62/00:00:00:00:00/e0 Emask 0x9 (media error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { UNC }
ata2.00: configured for UDMA/133
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd c8/00:08:c8:c9:62/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:ca:c9:62/00:00:00:00:00/e0 Emask 0x9 (media error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { UNC }
ata2.00: configured for UDMA/133
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd c8/00:08:c8:c9:62/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:ca:c9:62/00:00:00:00:00/e0 Emask 0x9 (media error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { UNC }
ata2.00: configured for UDMA/133
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd c8/00:08:c8:c9:62/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:ca:c9:62/00:00:00:00:00/e0 Emask 0x9 (media error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { UNC }
ata2.00: configured for UDMA/133
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd c8/00:08:c8:c9:62/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:ca:c9:62/00:00:00:00:00/e0 Emask 0x9 (media error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { UNC }
ata2.00: configured for UDMA/133
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd c8/00:08:c8:c9:62/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:ca:c9:62/00:00:00:00:00/e0 Emask 0x9 (media error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { UNC }
ata2.00: configured for UDMA/133
sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 62 c9 ca
sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sdb, sector 6474186
ata2: EH complete
md: disabled device sdb4, could not read superblock.
md: sdb4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
sd 1:0:0:0: [sdb] 3907029168 512-byte hardware sectors (2000399 MB)
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
sd 1:0:0:0: [sdb] 3907029168 512-byte hardware sectors (2000399 MB)
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
md: bind
oxnas_wd810_leds_state state=11
oxnas_wd810_leds_state state=12
FAT: Unrecognized mount option “usrquota” or missing value
FAT: Unrecognized mount option “usrquota” or missing value
oxnas_wd810_leds_state state=13
oxnas_wd810_leds_state state=1
oxnas_wd810_leds_state state=14
oxnas_wd810_leds_state state=1
oxnas_wd810_leds_state state=1
oxnas_wd810_leds_state state=1
FAT: Unrecognized mount option “usrquota” or missing value
oxnas_wd810_leds_state state=0
oxnas_wd810_leds_state state=1
oxnas_wd810_leds_state state=1
FAT: Unrecognized mount option “usrquota” or missing value
FAT: Unrecognized mount option “usrquota” or missing value
FAT: Unrecognized mount option “usrquota” or missing value

You might need to replace the device, it is advisable to contact WD Tech support:

http://support.wdc.com/contact/index.asp?lang=en