Datavolume doesn't exist ! message

[wizza59]

I am experiencing the same sort of problems as Storm8.

I really hope that somebody can help.

Recovery of the data is the most important thing to me at the moment.

[deepak]

Hello,

I also have the same issue with my 4TB Sharespace.

Need some detailed help in getting data off the drives...

Please help.

Thanks

Deepak

[hmblm1245]

I am also having the same problem as Storm8.

[hmblm1245]

I am having the same problem and it looks like  cohiba88 figured that it is due to the raid thinking that it is unable to rebuild from 2 drives. After testing i found that drive 2 and 3 (out of 0123) are not active but cannot be rebuilt into the raid. hence the assemble from 2 drives - not enough to start. so we need to start the array from disk 0 or 1. cohiba88 can you help with that please and maybe give a "Datavolume doesn't exist ! message for dummies" guide. Please help. THANKS.

[Cohiba88]

Hi hmblm1245 I pretty much gave up on running RAID5. I changed the setup to a not use RAID5 and just span all the disks.  I know this is risky, but its less risky than my volume failing every other month and having to restore.

I think my problem  has to do with my Power setup, where I am, I have frequent power issues lasting about 1-2 minute  5 - 10 times a day.  My UPS lasts about 15 minutes.  When the interruptions happen frequently, the UPS does not get a chance to recharge and then cannot sustain an outage of even 20 seconds.     So, on the first outage, the RAID5 olume breaks because there will be an inconsistency in writing the parity data, and then the system will rebuild the drive, on the subsequent outage, it will then break the RAID5 completely.   So now I'll end up with a bunch of completely healthy (physically) drives, but no data!!

So my solution was to strip the data with parity so when the power does go out, that there is no inconsistency check to fail (I think this is how it works).  I tested it by yanking the power and then doing it mutiple times.

The next part was to make the Sharespace talk to my UPS, it couldnt! because my UPS did not have a USB port, so I went out and bought a APC SmartUPS, with the Sharespace CANNOT recognize!!!   there is absolutely no documentation about UPS on teh WDC site.  So now I just connect the UPS to my MAC, which instantly recognizes it, and will try to create a script to log into the Sharespace and shut it down gracefully when there is a low battery condition.

Will I ever get a Sharespace again?  NEVER!!!!   I'll stick to independent USB / Network Drives and partition my data instead of centralizing it, together with a 1:1 backup.

[hmblm1245]

I also had my Sharespace connect to a UPS and the power flickered off and on and right after it caused this issue. I am guessing the same thing happened. Is there any other options that I could try to help get the rest of us poor WD Sharespace owner's data back?

I have been messing aroiund with mdadm and found that when running mdadm /dev/md[0123] i get

 Version : 00.90.01
  Creation Time : Mon Mar  2 01:11:15 2009
     Raid Level : raid1
     Array Size : 208768 (203.91 MiB 213.78 MB)
    Device Size : 208768 (203.91 MiB 213.78 MB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Aug 13 09:53:18 2010
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

           UUID : 70a4b827:72b11c03:f91b9113:7d13d1a8
         Events : 0.3531138

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
       2       8       33        2      active sync   /dev/sdc1
       3       8       49        3      active sync   /dev/sdd1
/dev/md1:
        Version : 00.90.01
  Creation Time : Mon Mar  2 01:11:15 2009
     Raid Level : raid1
     Array Size : 1044160 (1019.86 MiB 1069.22 MB)
    Device Size : 1044160 (1019.86 MiB 1069.22 MB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Thu Aug 12 23:52:46 2010
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

           UUID : 1858ad4b:ae658c2a:d86952b3:959a615c
         Events : 0.6798

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2
       2       8       34        2      active sync   /dev/sdc2
       3       8       50        3      active sync   /dev/sdd2
mdadm: md device /dev/md2 does not appear to be active.
mdadm: md device /dev/md3 does not appear to be active.

when i try to run fibreiv's fi'x first line mdadm -D /dev/md2

mdadm: md device /dev/md2 does not appear to be active.

same thing that the others are having.

When i run the 2nd line to attempt to assemble the array

mdadm --assemble /dev/md2 /dev/sda4 /dev/sdb4 /dev/sdc4 /dev/sdd4
mdadm: /dev/md2 assembled from 2 drives - not enough to start the array.

how wiould i format this to force array to start if that is even the right solution.

[hmblm1245]

Not sure what this firmware update is. My sharespace does not update to it i am still on the official version 2.1.92 however i stumbled on this page 2.2.8 which should on the last line listed below fix the RAID 5 issue. now how do i apply it or get to download it?

Resolved full configuration restore causing failed RAID 5

http://support.wdc.com/download/notes/WD_ShareSpace_release_notes_2_2_8_r2-tw2.pdf

These release notes provide information on the latest posting of firmware
for WD ShareSpace Network Storage System.
These release notes provide information on the following:
• Version 2.2.8
• Version 2.1.92
• Version 2.1.3
• Version 2.1.1
• Version 1.2.2
• Version 1.0.5 (Initial Release)
• Firmware Installation Procedure

Version 2.2.8:
Resolved Issues:
• Added USB driver to resolve performance issues for NTFS formatted drives
• Added support for HFS+J formatted USB drives
• Added RAID 10 support
• Added support Windows Server 2008 ADS
• Added AFP/TimeMachine support
• Updated Twonky Media Server
• Corrected CTorrent to accept torrents with an apostrophe (‘)
• Corrected CTorrent to accept filenames that start with non-alphanumeric characters that were rejected
• Corrected CTorrent to accept torrent files with a back quote (‘) in the filename
• Corrected CTorrent to accept torrent files with spaces in the name
• Corrected BitTorrent lable in web UI to CTorrent
• Resolved full configuration restore causing failed RAID 5

[calamityjane]

Please help! I'm having the same problem (Data volume doesn't exist!") but don't even understand the 16+ hour fix description. (I'm a photographer, not an IT bod, unfortunately). Please could you explain the steps as if to an idiot? (e.g. I don't know what SSH means). (I checked for updates to firmware and got the message it was up to date). All of my photographs are on there. Yes, I do have this year's work in two other places but it's the historical stuff that's only on there. RAID seems utterly pointless if you have to have a second RAID array to back up the first!

Best

Calam

[kylee]

I also facing same problem with 'hmblm1245'.

May I know how to solved above problem??

Thanks