cannot access data volume or web utility # 19117808

update:

ERR: could not mount root raid d

when rebooting

Open a tech support case at my.NetGear.com and post your case number.

Case# 19117808
Waiting on a call back

Update: has been escalated to Level 3 hopefully they will be able to get my data back.

One drive has stopped working (no power up) and i think it is the board. the other drive im having alot of trouble reading from, (tons of LBA errors in sea tools), the third drive seems to be ok.

anyone have any luck with raid reconstruction and recovery? Is it possible to get data from one drive in the array? Even when it may have been formatted by the readynas?

Using iRecover i was able to see a large amount of data fragments on the drive. all it was able to recover however, were system files for the readynas about 454mb and NO data from the shares. strange because roughly 80% of a 500gb drive had data fragments.

Thanks in advance for your thoughts and advice.

Hey DTschoolIT,

I took a look into your case and your NAS while it's up in tech support mode real quick. Looks like you had 3 drives to start with, I'll assume the one drive that stopped working from your post was drive 3. Drive 2 looks OK and drive 1 unfortunately has reached the point where it's trying to start up but fails. With 2/3 drives failed like that I can't bring up the RAID or the volume.

If you can get that failing drive cloned over to a new one, or have a data recovery company take care of that (I've seen them work wonders on cloning failing drives, something we just don't have the resources to do ourselves) there may be a chance to get back at the data. Barring that, getting data off 1 drive is going to be tricky due to striping, I haven't used iRecover myself but you may want to give "photorec" a shot too, I don't hold high hopes for it being able to pull anything, though.

thank you for the response.

were you the person assigned to my case?

should i then take it out of tech support mode?

thanks

Another option for attempting to clone the disk would be to use dd_rescue though from what siigna has said it sounds like the disk has failed pretty badly, but it's still worth a try.

readysecure1985 wrote:

Here is a simple guide to quickly recover a failed drive using dd_rescue. I often have to deal with pesky failed drives, so here is a quick simple guide how to achieve this with a free Linux Live CD and a PC with two SATA connections. I will be using a Knoppix 6.2 Live CD for this guide. Can be found at http://www.knoppix.net Using dd_rescue command allows you to copy data from one drive to another block for block. This is especially useful for recovering a failed drive. Often when a drive fails, the drive is still accessible, it has just surpassed the S.M.A.R.T. error threshold. dd_rescue allows you to ignore the bad sectors and continue cloning the bad drive to a new healthy drive. 1) Connect your old drive and new drive to your PC 2) Boot up using your Linux live CD 3) Launch a terminal window. 4) Run fdisk -l to make sure the system sees both of the hard drives. 5) Run hdparm -i /dev/sdx on both of the drives to find which drive is your source drive and which drive is your destination drive 6) Once you know which drive is which you can start the clone process. dd_rescue /dev/sdx(source disk) /dev/sdx(destination drive) 7) You will see the process start, just keep an eye on it, it might take a few hours for the clone job to finish, depending on the size of the drive. Once the process is complete, there will be no notification, the transfer will just stop and you will see the terminal prompt again. If you see a lot of errors or see that there is no more data being shown as succxfer: it means the drive got marked faulty by the kernel. At this point reboot the system and make sure you know which drive is which again, as it is possible they lettering might switch. Run the dd-rescue command again but this time with -r option. This will start the cloning again but this time will start from the back of the drive and will make sure to get the data that has not been cloned yet. There is no guarantee this will recover your data, but there is a very high chance this will work and its free…

If you really need your data back going to a data recovery company would be the best option but they can be very expensive. Having a good backup just in case would have been much cheaper. Regardless of the outcome I hope you backup your data regularly in future. Multiple disk failures is one of multiple problems that can take out an array. See Preventing Catastrophic Data Loss

Thank you for the responses everyone.

I am attempting to recover my data and have made images of two of the disks, the other one has a bad board which will not power up (the tvs diode is completely fried) which i am going to have sent out for repair.

What are the raid parameters for the readynas pro? I am going to try and define them manually to reconstruct the array as several different recovery programs have had trouble detecting the settings or crashing after 2 days of running recovery.

Thanks again.

Model: Readynas Pro bus 6000

RAID: x-raid (raid-5)

I was able to pull this from the last raid_config log:


***** RAID configuration log from 2012/07/29 *****


***** mdadm -D --scan -v *****

ARRAY /dev/md/0 level=raid1 num-devices=3 metadata=1.2 name=001F33EA2C57:0 UUID=0f0a778f:dc43be88:41a301fc:626b8cee
devices=/dev/sda1,/dev/sdb1,/dev/sdc1
ARRAY /dev/md/1 level=raid1 num-devices=3 metadata=1.2 name=001F33EA2C57:1 UUID=9fabc069:af4b968f:3d59e47c:b08945b4
devices=/dev/sda2,/dev/sdb2,/dev/sdc2
ARRAY /dev/md/2 level=raid5 num-devices=3 metadata=1.2 name=001F33EA2C57:2 UUID=59ecf7cb:b0351eca:49693321:e86751da
devices=/dev/sda5,/dev/sdb5,/dev/sdc5
***** mdadm -D --scan -vv *****

/dev/md/0:
Version : 1.2
Creation Time : Tue Apr 28 18:54:40 2009
Raid Level : raid1
Array Size : 4194292 (4.00 GiB 4.29 GB)
Used Dev Size : 4194292 (4.00 GiB 4.29 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent

Update Time : Sun Jul 29 06:47:01 2012
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0

Name : 001F33EA2C57:0
UUID : 0f0a778f:dc43be88:41a301fc:626b8cee
Events : 150358

Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
4 8 17 1 active sync /dev/sdb1
3 8 33 2 active sync /dev/sdc1
/dev/md/1:
Version : 1.2
Creation Time : Mon Apr 18 10:23:37 2011
Raid Level : raid1
Array Size : 524276 (512.07 MiB 536.86 MB)
Used Dev Size : 524276 (512.07 MiB 536.86 MB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent

Update Time : Sun Jul 29 06:47:01 2012
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0

Name : 001F33EA2C57:1
UUID : 9fabc069:af4b968f:3d59e47c:b08945b4
Events : 40

Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
3 8 18 1 active sync /dev/sdb2
2 8 34 2 active sync /dev/sdc2
/dev/md/2:
Version : 1.2
Creation Time : Tue Apr 28 18:54:41 2009
Raid Level : raid5
Array Size : 967330592 (922.52 GiB 990.55 GB)
Used Dev Size : 483665296 (461.26 GiB 495.27 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent

Update Time : Sun Jul 29 06:47:01 2012
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 16K

Name : 001F33EA2C57:2
UUID : 59ecf7cb:b0351eca:49693321:e86751da
Events : 7055

Number Major Minor RaidDevice State
0 8 5 0 active sync /dev/sda5
4 8 21 1 active sync /dev/sdb5
3 8 37 2 active sync /dev/sdc5