ShareSpace 4TB unmountable volume

Hi,

I am struggling with my ShareSpace since today.

There seemed to be a power outage and now I am unable to mount the RAID 5 under OS 10.8. I’ve been through the majority of the posts and tried various ways to get hold of the issue, but since I am not the Linux pro I might need some assistance. It might be fairly easy and a HDD simply crashed, but after I’ve read the posts it might be something else as well. Especially since all 4 drives are labeled ‘Failed’ now.

This is what I can provide you with for now. As said I’m nowhere near a Pro, so not sure if anything below is helping so far.

Extract from the Storage Disk Manager

Disk Volume Size Description Status

HDD 4 Unassigned 931.51 GB WDC WD10EADS-00L5B1 Failed

HDD 3 Unassigned 931.51 GB WDC WD10EADS-00L5B1 Failed

HDD 2 Unassigned 931.51 GB WDC WD10EADS-00L5B1 Failed

HDD 1 Unassigned 931.51 GB WDC WD10EADS-00L5B1 Failed

Volume Type Disk Usage Size Status

DataVolume Raid 5 Unknown Unknown Degraded

~ $ fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 1 26 208844+ fd Linux raid autodetect
/dev/sda2 27 156 1044225 fd Linux raid autodetect
/dev/sda3 157 182 208845 fd Linux raid autodetect
/dev/sda4 183 121601 975298117+ fd Linux raid autodetect

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sdb1 1 26 208844+ fd Linux raid autodetect
/dev/sdb2 27 156 1044225 fd Linux raid autodetect
/dev/sdb3 157 182 208845 fd Linux raid autodetect
/dev/sdb4 183 121601 975298117+ fd Linux raid autodetect

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sdc1 1 26 208844+ fd Linux raid autodetect
/dev/sdc2 27 156 1044225 fd Linux raid autodetect
/dev/sdc3 157 182 208845 fd Linux raid autodetect
/dev/sdc4 183 121601 975298117+ fd Linux raid autodetect

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sdd1 1 26 208844+ fd Linux raid autodetect
/dev/sdd2 27 156 1044225 fd Linux raid autodetect
/dev/sdd3 157 182 208845 fd Linux raid autodetect
/dev/sdd4 183 121601 975298117+ fd Linux raid autodetect
 
$ mdadm --detail /dev/sd[abcd]4
mdadm: /dev/sda4 does not appear to be an md device
mdadm: /dev/sdb4 does not appear to be an md device
mdadm: /dev/sdc4 does not appear to be an md device
mdadm: /dev/sdd4 does not appear to be an md device
~ $ mdadm --assemble --scan -v
mdadm: No arrays found in config file
~ $ mdadm --assemble /dev/md2 /dev/sd[abcd]4
mdadm: device /dev/md2 already active - cannot assemble it
~ $ mdadm --examine /dev/sd[abcd]4
/dev/sda4:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 35aa2873:86532802:8474e5ca:a3c94384
  Creation Time : Mon Nov 16 21:45:16 2009
     Raid Level : raid5
  Used Dev Size : 975097920 (929.93 GiB 998.50 GB)
     Array Size : 2925293760 (2789.78 GiB 2995.50 GB)
   Raid Devices : 4
  Total Devices : 3
Preferred Minor : 2

    Update Time : Wed Jul 4 10:31:53 2012
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 62ffdb62 - correct
         Events : 4333406

         Layout : left-symmetric
     Chunk Size : 64K

      Number Major Minor RaidDevice State
this 0 8 4 0 active sync /dev/sda4

   0 0 8 4 0 active sync /dev/sda4
   1 1 0 0 1 faulty removed
   2 2 8 36 2 active sync /dev/sdc4
   3 3 8 52 3 active sync /dev/sdd4
/dev/sdb4:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 35aa2873:86532802:8474e5ca:a3c94384
  Creation Time : Mon Nov 16 21:45:16 2009
     Raid Level : raid5
  Used Dev Size : 975097920 (929.93 GiB 998.50 GB)
     Array Size : 2925293760 (2789.78 GiB 2995.50 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 2

    Update Time : Sun Jul 1 05:03:11 2012
          State : active
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 62b80972 - correct
         Events : 4238890

         Layout : left-symmetric
     Chunk Size : 64K

      Number Major Minor RaidDevice State
this 1 8 20 1 active sync /dev/sdb4

   0 0 8 4 0 active sync /dev/sda4
   1 1 8 20 1 active sync /dev/sdb4
   2 2 8 36 2 active sync /dev/sdc4
   3 3 8 52 3 active sync /dev/sdd4
/dev/sdc4:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 35aa2873:86532802:8474e5ca:a3c94384
  Creation Time : Mon Nov 16 21:45:16 2009
     Raid Level : raid5
  Used Dev Size : 975097920 (929.93 GiB 998.50 GB)
     Array Size : 2925293760 (2789.78 GiB 2995.50 GB)
   Raid Devices : 4
  Total Devices : 3
Preferred Minor : 2

    Update Time : Wed Jul 4 10:31:53 2012
          State : active
 Active Devices : 3
Working Devices : 3
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 62bdbc28 - correct
         Events : 4333407

         Layout : left-symmetric
     Chunk Size : 64K

      Number Major Minor RaidDevice State
this 2 8 36 2 active sync /dev/sdc4

   0 0 8 4 0 active sync /dev/sda4
   1 1 0 0 1 faulty removed
   2 2 8 36 2 active sync /dev/sdc4
   3 3 8 52 3 active sync /dev/sdd4
/dev/sdd4:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 35aa2873:86532802:8474e5ca:a3c94384
  Creation Time : Mon Nov 16 21:45:16 2009
     Raid Level : raid5
  Used Dev Size : 975097920 (929.93 GiB 998.50 GB)
     Array Size : 2925293760 (2789.78 GiB 2995.50 GB)
   Raid Devices : 4
  Total Devices : 3
Preferred Minor : 2

    Update Time : Wed Jul 4 10:31:53 2012
          State : active
 Active Devices : 3
Working Devices : 3
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 62bdbc3a - correct
         Events : 4333407

         Layout : left-symmetric
     Chunk Size : 64K

      Number Major Minor RaidDevice State
this 3 8 52 3 active sync /dev/sdd4

   0 0 8 4 0 active sync /dev/sda4
   1 1 0 0 1 faulty removed
   2 2 8 36 2 active sync /dev/sdc4
   3 3 8 52 3 active sync /dev/sdd4
~ $ cat /proc/mdstat 
Personalities : [linear] [raid0] [raid1] [raid5] 
md1 : active raid1 sdd2[3] sdc2[2] sdb2[1] sda2[0]
      1044160 blocks [4/4] [UUUU]
      
md2 : inactive sda4[0] sdd4[3] sdc4[2]
      2925894144 blocks
md0 : active raid1 sdc1[2] sdd1[3] sdb1[1] sda1[0]
      208768 blocks [4/4] [UUUU]
      
unused devices: <none>

Thanks very much in advance & any help is much appreciated.

Although the device is still within warranty I’d like to keep my data.

Thanks !

If the data is of a high value I recommend you to take the drive to a professional data recovery service, trying to do it yourself may end causing more corruption to the data and make it irrecoverable.