NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Ready NAS Pro Pioneer RAID 5 Recovery
Hello everyone! A couple of month ago my Ready NAS Pro Pioneer Edition - 6 disks, RAID 5 - failed me after 6 years of service, not starting up at all. Since my biggest concern was to retrieve the...
Seeing that both disks dropped out at the same time it hopefully will work.
However forcing an array online is not without its risks. If it doesn't work out then your array may be left in a state where you can't recover anything.
You may wish to clone your disks first. It's up to you.
There should be info on the OS partition which indicates the drive order.
When your Pro Pioneer did not start up at all do you mean to say that you had no response when you attempted to power it on? If it did say get stuck with booting on the display that would suggest a bad disk. It's also advisable to power down, remove the disks (label order) and see if you get any response with the disks removed if you get no response with the disks installed. With no disks installed you should get an error indicating that no disks are installed.
It is advisable to check the health of the disks before attempting to start the array and to check that the array is in a good state.
You can check the health of the disks using e.g. SeaTools for SeaGate disks or WD Data Lifeguard Diagnostics for WD disks. This can be done using a boot disk such as the Ultimate Boot CD (a free boot disk). Alternatively if you prefer you can install smartmontools on Linux and use the smartctl command.
To check the update time for the md devices you could use e.g.
# cat /proc/partitions
# mdadm -E /dev/sda3
# mdadm -E /dev/sdb3
Assuming that the 3rd partition is the large one. It may be sda5 if you last did a factory reset on very old firmware. Furthermore if you have multiple RAID layers there will be multiple layers to check.
Mounting the volume read-only is certainly preferable.
Data recovery using an ordinary Linux PC is a last resort.
Thanks very much for the quick reply!
The unit did not start up at all, just the Network LEDs on the RJ45 LAN-Ports were flickering dimly, with and without drives installed. Somewhere here a user fixed his ReadyNAS Pioneer with said behaviour by changing the PSU, which did not work for me. With the new PSU still no response.
So i am focusing on recovering the data initiallly. The drives are 6x Hitachi 3TB Hitachi HDS5C3030ALA630, running for about 3 years. What I gathered from the system info (Windows and Linux) the drives look fine (temperature, partitions, etc.).
smartctl indicated no errors, selftests have been ok.
mdadm -E /dev/<big partition> gives the following results (magic numbers match, all states clean, all checksums correct):
/dev/sda3: Device Role: Active device 4, Array State: AAAAAA , Events: 68
/dev/sdb3: Device Role: Active device 5, Array State: AAAAAA , Events: 68
/dev/sdc3: Device Role: Active device 3, Array State: AAAA.. , Events: 75
/dev/sde3: Device Role: Active device 2, Array State: AAAA.. , Events: 75
/dev/sdf3: Device Role: Active device 1, Array State: AAAA.. , Events: 75
/dev/sdg3: Device Role: Active device 0, Array State: AAAA.. , Events: 75
(missing 2 devices on 4 of the disks)
1. How do I proceed from there? Do I have to reconfigure the raid somehow? Is mdadm --assemble --verbose --force a correct approach? As mentioned I just started using linux and am a little nervous to do further damage, so try and error is out of the question.
2. Is the order the devices are attached to the hardware controller in any way important?
What are the update times for sda3 and sdb3?
You may wish to consider purchasing a new ReadyNAS e.g. 316 and purchasing a data recovery attempt rather than try to recover it yourself. It is very easy to get things wrong when attempting data recovery is you are unfamiliar with doing it.
The update times
sda3: 23:21:01
sdb3: 23:21:01
sdc3: 23:49:08
sde3: 23:49:08
sdf3: 23:49:08
sdg3: 23:49:08.
I was copying a rather large file of 128 GB at that time, that failed to read after 40 GBs.
Here is the /proc/mdstat to give a picture of the setup, if that might help.
Personalities : [raid1] [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid10]
md2 : inactive sdc3[3](S) sde3[2](S) sdg3[0](S) sdf3[1](S) sda3[4](S) sdb3[5](S)
17553269331 blocks super 1.2md1 : active raid6 sde2[2] sdc2[3] sdg2[0] sdf2[1] sda2[4] sdb2[5]
2096896 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md0 : active raid1 sde1[2] sdc1[3] sdg1[0] sdf1[1] sda1[4] sdb1[5]
4193268 blocks super 1.2 [6/6] [UUUUUU]I am aware that I might screw things up during but that is a risk ill have to take since I cant invest more than time into the recovery at the moment.
in this scenario, would
mdadm --asseble --force /dev/md2 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sde3 /dev/sdf3 /dev/sdg3
be the right command for an assemble? can --force destroy data, eg in the superblocks?
Seeing that both disks dropped out at the same time it hopefully will work.
However forcing an array online is not without its risks. If it doesn't work out then your array may be left in a state where you can't recover anything.
You may wish to clone your disks first. It's up to you.
There should be info on the OS partition which indicates the drive order.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
