Volume Status - Volume 'DataVolume' doesn't exist

Community Archives WD ShareSpace
1

Hi All,

I m stuck in a very bad position with my WD ShareSpace with firmware ver. 2.2.90 with MioNet 4.3.0.8

It has 4 Disks of 1 T.B each with RAID 5 configured and only one Volume. I am unable to access data in it. When i try accessing it on network it shows all shares but does not allow to go in it.

Last night during a data copy process it reached Full space utilization and then “Data Volume” became unavailable. We tried restarting it but to no success. Currently it is showing alert of " [Volume Status] Data Volume ‘DataVolume’ doesn’t exist!". While all 4 disks are showing “Failed” status and volume as Unassigned.

I did try removing all 4 disks after unit shutdown cleaned them up and plugged back. Then i start it but with same status. I have put some log from it below which shows that disks are detected.

5/15 23:56:01  WDNAS daemon.alert wixEvent[926]: Volume Status - Volume ‘DataVolume’ doesn’t exist.

  05/15 23:34:05  WDNAS daemon.warn wixEvent[926]: iTunes Server - iTunes server cannot find the path to /Public/Shared Music. Please verify that the folder name has not been changed.

  05/15 23:33:41  WDNAS daemon.info wixEvent[926]: Network IP Address - NIC 1 use static IP address 172.18.10.109

  05/15 23:33:41  WDNAS daemon.info wixEvent[926]: System Startup - System startup.

  05/15 23:33:41  WDNAS daemon.info wixEvent[926]: Network Link - NIC 1 link is up 1000 Mbps full duplex.

  05/15 23:33:38  WDNAS syslog.info miocrawler: === Walking directory done.

  05/15 23:33:38  WDNAS syslog.info miocrawler: === mc_trans_updater_init() …Done.

  05/15 23:33:38  WDNAS syslog.info miocrawler: mc_trans_updater_init() …

  05/15 23:33:38  WDNAS syslog.info miocrawler: === inotify init done.

  05/15 23:33:38  WDNAS syslog.info miocrawler: === mcUtilsInit() Done.

  05/15 23:33:38  WDNAS syslog.info miocrawler: mcUtilsInit() Creating free queue pool

  05/15 23:33:38  WDNAS syslog.info miocrawler: === mc_db_init …Done.

  05/15 23:33:37  WDNAS syslog.info miocrawler: ++++++++ database exists: ret = 0

  05/15 23:33:37  WDNAS syslog.info miocrawler: mc_db_init …

  05/15 23:33:37  WDNAS syslog.info miocrawler: +++++++++++++++ START OF ./miocrawler at 2011:05:15 - 23:33:37 [Version 01.09.00.96] ++++++++++++++

  05/15 23:33:36  WDNAS daemon.warn wixEvent[926]: Network Link - NIC 1 link is down.

  05/15 23:33:36  WDNAS daemon.info wixEvent[926]: HDD Status - HDD 1 is found.

  05/15 23:33:21  WDNAS daemon.info wixEvent[926]: HDD Status - HDD 2 is found.

  05/15 23:33:16  WDNAS daemon.info wixEvent[926]: HDD Status - HDD 3 is found.

  05/15 23:33:12  WDNAS daemon.info wixEvent[926]: HDD Status - HDD 4 is found.

  05/15 23:33:08  WDNAS syslog.info syslogd started: BusyBox v1.1.1

  05/15 04:57:34  WDNAS syslog.info System log daemon exiting.

  05/15 04:57:32  WDNAS daemon.info afpd[891]: shutting down on signal 15

  05/15 04:57:31  WDNAS daemon.err mountd[829]: Caught signal 15, un-registering and exiting.

  05/15 04:57:31  WDNAS auth.info sshd[784]: Received signal 15; terminating.

  05/15 04:57:28  WDNAS daemon.warn wixEvent[938]: System Shutdown - System will be shutdown.

  05/15 04:53:28  WDNAS daemon.info wixEvent[938]: User Manage - User admin modified.

  05/15 04:50:43  WDNAS daemon.warn wixEvent[938]: iTunes Server - iTunes server cannot find the path to /Public/Shared Music. Please verify that the folder name has not been changed.

  05/15 04:50:13  WDNAS daemon.info wixEvent[938]: Network IP Address - NIC 1 use static IP address 172.18.10.109

  05/15 04:50:13  WDNAS daemon.info wixEvent[938]: System Startup - System startup.

  05/15 04:50:13  WDNAS daemon.info wixEvent[938]: Network Link - NIC 1 link is up 1000 Mbps full duplex.

  05/15 04:50:11  WDNAS syslog.info miocrawler: === Walking directory done.

  05/15 04:50:11  WDNAS syslog.info miocrawler: === mc_trans_updater_init() …Done.

  05/15 04:50:11  WDNAS syslog.info miocrawler: mc_trans_updater_init() …

  05/15 04:50:11  WDNAS syslog.info miocrawler: === inotify init done.

  05/15 04:50:11  WDNAS syslog.info miocrawler: === mcUtilsInit() Done.

  05/15 04:50:11  WDNAS syslog.info miocrawler: mcUtilsInit() Creating free queue pool

  05/15 04:50:11  WDNAS syslog.info miocrawler: === mc_db_init …Done.

  05/15 04:50:09  WDNAS daemon.warn wixEvent[938]: Network Link - NIC 1 link is down.

  05/15 04:50:09  WDNAS daemon.info wixEvent[938]: HDD Status - HDD 1 is found.

  05/15 04:50:08  WDNAS syslog.info miocrawler: ****** database does not exist. ret = -1, creating path

  05/15 04:50:08  WDNAS syslog.info miocrawler: mc_db_init …

  05/15 04:50:08  WDNAS syslog.info miocrawler: +++++++++++++++ START OF ./miocrawler at 2011:05:15 - 04:50:08 [Version 01.09.00.96] ++++++++++++++

  05/15 04:49:59  WDNAS daemon.info wixEvent[938]: HDD Status - HDD 2 is found.

  05/15 04:49:55  WDNAS daemon.info wixEvent[938]: HDD Status - HDD 3 is found.

  05/15 04:49:51  WDNAS daemon.info wixEvent[938]: HDD Status - HDD 4 is found.

  05/15 04:49:46  WDNAS syslog.info syslogd started: BusyBox v1.1.1

  05/15 04:48:33  WDNAS syslog.info System log daemon exiting.

  05/15 04:48:32  WDNAS daemon.info afpd[871]: shutting down on signal 15

  05/15 04:48:30  WDNAS daemon.err mountd[810]: Caught signal 15, un-registering and exiting.

  05/15 04:48:30  WDNAS auth.info sshd[763]: Received signal 15; terminating.

  05/15 04:48:26  WDNAS daemon.warn wixEvent[910]: System Reboot - System will reboot.

  05/15 02:50:11  WDNAS daemon.alert wixEvent[910]: Volume Used - Volume ‘DataVolume’ had reached full capacity.

  05/08 20:49:20  WDNAS daemon.info afpd[871]: server_child[1] 5924 done

  05/08 20:49:20  WDNAS daemon.info afpd[5924]: ASIP session:548(4) from 172.18.10.158:50216(6)

  05/08 20:49:19  WDNAS auth.info sshd[5923]: Did not receive identification string from 172.18.10.158

  05/06 13:10:13  WDNAS daemon.alert wixEvent[910]: Volume Used - Volume ‘DataVolume’ had reached 95% capacity.

  05/15 04:48:33  WDNAS syslog.info System log daemon exiting.  05/15 04:48:32  WDNAS daemon.info afpd[871]: shutting down on signal 15  05/15 04:48:30  WDNAS daemon.err mountd[810]: Caught signal 15, un-registering and exiting.  05/15 04:48:30  WDNAS auth.info sshd[763]: Received signal 15; terminating.  05/15 04:48:26  WDNAS daemon.warn wixEvent[910]: System Reboot - System will reboot.  05/15 02:50:11  WDNAS daemon.alert wixEvent[910]: Volume Used - Volume ‘DataVolume’ had reached full capacity.  05/08 20:49:20  WDNAS daemon.info afpd[871]: server_child[1] 5924 done  05/08 20:49:20  WDNAS daemon.info afpd[5924]: ASIP session:548(4) from 172.18.10.158:50216(6)  05/08 20:49:19  WDNAS auth.info sshd[5923]: Did not receive identification string from 172.18.10.158  05/06 13:10:13  WDNAS daemon.alert wixEvent[910]: Volume Used - Volume ‘DataVolume’ had reached 95% capacity.

2

Hi there, it could be that your SS has failed. Since you have a RAID 5 then it’s possible to recover the data. A WD representative said that you could recover the data by connecting the 4 disks directly to a computer via SATA and use Fedora Core 14 Live cd to access the volume.

You can see the full post in here.

Good luck, I hope you have a backup, RAID just adds fault tolerance in case single drive failure, it still needs a backup somewhere else.

1 Like
3

Make sure you test each of the 4 drives as well.  I would run WinDLG on all 4 drives to see if there is more than one that is bad. 

Here’s a link to WinDLG:

http://support.wdc.com/product/download.asp?groupid=612&sid=3&lang=en

There is a common mis-conception that the UI is going to report a bad drive 100% of the time.  Most backplanes and NAS devices simply report the SMART status (which can be good on a failing or failed drive), which leaves the possibility that you could have more then 1 drive in your array which failed (causing the entire RAID 5 to fail).

1 Like
4

Thank a lot for reply, i will try connecting all 4 drives to a system to run Fedora Live from CD and see if it could show me data. I have not worked on Linux enough, so just curious if Fedora Core Live is Fedora Desktop Live CD as no separate download could be found for Fedora Core.

Further should i connect drives from 1 to 4 on simple SATA ports in order as removed from ShareSpace. and if there is need for setting up any RAID config on the computer?

5

@ ThePizzaMatrix bundle and bundle of thanks. The Fedora Live CD solution after some work in SSH through mdadm worked. I am currently copying data and verified some of it, Now remaining is in process of copy, kindly post something on it as solution to help others as well.

Full detail on how it worked for me is here,

http://community.wdc.com/t5/WD-ShareSpace/Datavolume-doesn-t-exist-message/m-p/191598

6

Sorry, new to this and trying to learn on the fly through the forums. My new Sharespace just did pretty much the same thing. I was going to RMA the faulty drive, replace it, and let it rebuild everything, but your comment there scared me a bit.

Are you saying that if I have RAID5 and replace a drive that I’ll lose the data?

7

@  PlaySafe: Glad I was able to help :slight_smile:

@  Jerbaldo: If you replace 2 at the same time drives or if 2 drives fail at once, you lose the data. Get a backup, RAID just adds fault tolerance to single drive failure, so it still needs a separate backup if you don’t want to lose your files.