NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Recovering RAID Array after "No volume Found" error
A client of mine has a ReadyNAS 3200 and after a hard drive started to become corrupted, it stopped working. When I log into the web console, it gives me an error saying "no volume exists" . It was setup to use RAID6 so there should be redundancy in scenerios such as this. Regardless, I really need to get this working and I need some help.
Here's what I have found...
The unit is trying to mount the device "/dev/c/c" however this doesn't exist.
Here's is the output of the mdadm scan:
NAS3200:/c# mdadm -D --scan -vv
/dev/md/0:
Version : 1.2
Creation Time : Thu Mar 18 04:01:19 2010
Raid Level : raid1
Array Size : 4194292 (4.00 GiB 4.29 GB)
Used Dev Size : 4194292 (4.00 GiB 4.29 GB)
Raid Devices : 12
Total Devices : 12
Persistence : Superblock is persistent
Update Time : Sat Jan 30 15:12:25 2016
State : clean
Active Devices : 12
Working Devices : 12
Failed Devices : 0
Spare Devices : 0
Name : 003048FAF4C0:0
UUID : 4180ac37:4a2fedcc:ecdf1aac:62a18ee9
Events : 75517
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
4 8 81 4 active sync /dev/sdf1
5 8 65 5 active sync /dev/sde1
6 8 97 6 active sync /dev/sdg1
7 8 113 7 active sync /dev/sdh1
8 8 129 8 active sync /dev/sdi1
9 8 145 9 active sync /dev/sdj1
10 8 161 10 active sync /dev/sdk1
12 8 177 11 active sync /dev/sdl1
/dev/md/1:
Version : 1.2
Creation Time : Wed Sep 23 11:16:53 2015
Raid Level : raid6
Array Size : 5242240 (5.00 GiB 5.37 GB)
Used Dev Size : 524224 (512.02 MiB 536.81 MB)
Raid Devices : 12
Total Devices : 12
Persistence : Superblock is persistent
Update Time : Sat Jan 30 15:11:03 2016
State : clean
Active Devices : 12
Working Devices : 12
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : 003048FAF4C0:1
UUID : bad515a8:ea150314:4f2d666e:73879304
Events : 145
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
4 8 66 4 active sync /dev/sde2
5 8 82 5 active sync /dev/sdf2
6 8 98 6 active sync /dev/sdg2
7 8 114 7 active sync /dev/sdh2
8 8 130 8 active sync /dev/sdi2
9 8 146 9 active sync /dev/sdj2
10 8 162 10 active sync /dev/sdk2
11 8 178 11 active sync /dev/sdl2I also confirmed that the unit see's each disk in a RAID array:
NAS3200:/c# fdisk -l Found valid GPT with protective MBR; using GPT Disk /dev/sda: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 50490f79-a127-49b1-b40f-fe0665d54c76 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdb: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): db4e54ca-1d2b-4d91-9a08-899cc335a6a8 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdc: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 83fb9395-8cf1-43d6-bc6b-1def79be7cec Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdd: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): b5a37072-284b-474d-b1d4-ebf9692cbbe1 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sde: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 00a7e831-e823-4255-931d-c5afd46bc661 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdf: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): e6d709ae-0680-4ad8-a7e6-c5b576809896 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdg: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 02b5ab8b-1a80-4031-9a82-396feab2ddf9 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdh: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 71cda151-6fb5-4223-8f75-5c6fb6f20cc5 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdi: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 56b3561d-a05f-4779-b828-2fce2258f27f Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdj: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 6d447850-a645-4f51-82a7-6f728276cb77 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdk: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 5fbe08c2-1d3a-4a66-b034-19e55e1df427 Partition table holds up to 8 entries First usable sector is 4, last usable sector is 3907029164 Number Start (sector) End (sector) Size Code Name 1 4 8388611 4096M 0700 Linux RAID 2 8388612 9437187 512M 0700 Linux RAID 5 9437189 3907024064 1858G 0700 Linux RAID Found valid GPT with protective MBR; using GPT Disk /dev/sdl: 3907029168 sectors, 1863G Logical sector size: 512 Disk identifier (GUID): 483486b0-f6c9-4981-b246-d4022f7d7e0c Partition table holds up to 128 entries First usable sector is 34, last usable sector is 3907029134 Number Start (sector) End (sector) Size Code Name 1 64 8388671 4096M 0700 2 8388672 9437247 512M 0700 5 9437256 3907024131 1858G 0700 Disk /dev/md0: 4294 MB, 4294955008 bytes 2 heads, 4 sectors/track, 1048573 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md0 doesn't contain a valid partition table
Any help you can give me would be VERY appriciated!
11 Replies
Replies have been turned off for this discussion
You may have to transfer the disks in order to a linux box and recover that way
have a look at
There is another more involved thread of the forum
and there are some windows based software packages once agine which involve installing the discs into a windows machine
Reclaime and UFS Explorer
I am sure the MDGM will reply to this and advise
This could be a data recovery situation. The output you have provided shows that the array on which the data volume sits has failed to start.
Can you send me your logs (see the Sending Logs link in my sig)?
This is a 3200 which runs RAIDiator-x86, which uses EXT4 not BTRFS.
Disk 12 has failed. It has a huge reallocated sector count and has failed basic self-testing.Also the volume failed to mount. This does sound like a data recovery situation so you would be best to contact support if you wish to purchase a data recovery contract. Please note that data recovery may be unsuccessful.
It looks like you have attempted to fix the problem yourself which appears to have only succeeded in making the problem worse.
It's one thing to attempt to recover data using a Linux machine when the array, volume, disks are fine. It's quite another to attempt data recovery when there are problems with one/more disks, the volume and the array.I recovered an ext volume from an NV+v! which had a disc "fail" using ufs explorer
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
