Joy of Joy - Successful Recovery of data from Netgear ReadyNas NV+ running X-Raid
Thanks to some digging around, logic and a failed attempt by Kroll Ontrack to recover data we have managed to recover all my data using Ubuntu and R-Studio.
Let me recap the original situation:
1 - ReadyNas NV+ Box running 4x1Tb drives in X-Raid Mode started to grind to a halt.
2 - Since the RadyNas Box didn't specify what drive was failing and ground to a halt I had no choice (foolishly with hindsight) but to try and pull out one drive at a time to see if the Box would reeboot and work out which drive was faulty.
3 - Because of this action the ReadNas NV+ Box did some "funny things" and resulted in showing me the Volumes but telling me that they were not available. The screen at the front told me 0/0...I THOUGHT THAT WAS IT
4 - Took my ReadyNas box to Kroll Ontrack and told them that the system was running on X-Raid (which I took to mean a form of RAID 5)
5 - Kroll Ontrack confirmed that one of the drives was partially corrupt and they could only image it at 85% but the other 3 drives were fine
6 - After 2 weeks they came back and said that they only managed to recover 1/3 of the files that I was supposed to have and told me that they were seeing the Disks as Striped NOT as Raid 5??? Anyways the data they could recover was useless to me so I thanked them and only paid for the diagnostic. At this point I would like to say that Kroll Ontrack were extremely professional, were always available to answer my questions and gave me regular updates...just didn't succeed with recovering all the data.
7 - Having got the RadyNas NV+ Back and under the suggestion of Kroll Ontrack, I made Images of all 4 drives using R-Studio Network and used the Byte by Byte Image copy to copy the 4 disks onto 2 3TB USB external drives. The R-Studio Image copy for the 4th drive I put the parameters of 20 attempts to read sector failures. Each drive took around 6 hours to image.
6 - R-Studio showed me that 3 of the 4 drives had 4 volumes and one drive had 0 volumes (the drive with 0 volumes was not the corrupt 4th drive but one of the good ones), also I could see that this second drive had data on it!
7 - Doing a lot of research on the internet (I had 2 weeks of twiddling my thumbs) I found that the ReadyNas NV+ box is bascally running linux and that people had success in connectig the drives and viewing content on Ubuntu.
8 - I called my friend Steve at Regenology and since they do hosting I thought that he might be able to help as he knows a lot about Linux for obvious reasons.
9 - The first thing he did was to copy the Volume Table from one of the images that had a Volume Table to the image of the drive that didn't have the Volume Table (we saw that the volume tables were identical for all 3 drives). The loss of this volume table on drive 2 was probably caused by the ReadyNas NV+ box Initializing the disk when I was doing the drive swap test!
10 - The next thing we did was to mount these images in Ubuntu, including the partially corrupt one, and using the "kpartx -a" command in the terminal (this is where it all got too technical for me) followed by a "vgscan" VOLUME C appeared!!!! This has all the DATA!!!. This was the guiding article -
http://home.bott.ca/webserver/?p=306
11 - After listing the folders in this volume and determining the size (just to make sure that data was there) we "rsync" all the data onto an external Drive
Next thing I will try is to do the volume table rebuild on the the physical drive 2 from the ReadyNas box, see if it boots with the 3 good drives and then throw in a 4th drive (in place of the corrupt one) and let it do what it is supposed to do and re-sync all the data - Even though I seem to have all the data now anyways I have learnt my lesson and doubling on everything.
Also I haven't been able to determined if the corrupted Disk 4 data has affected any of the files that I have recovered via this method. But in theory the ReadyNas box should rebuild everything....but now I am not afraid to try!!
A big thanks to R-Studio for giving me to tool to clone the drives (in an easy way) and also cloning the corrupt drive.
A big thanks to Kroll Ontrack, even though they didn't manage to get the data, they still gave me information that allowed me to think of this...and didn't have to spend a fortune!
A big thanks to the forums and the internet
A big thanks for nothing to Netgear for being USELESS in their support
A big thanks to this forum - Alt and magicm
And finally a huge thanks to Steve at Regenology http://regenology.co.uk/ for doing the terminal work in Ubuntu (we used Google Chrome Remote Desktop App for him to access my computer)
I will let you know how I get on with the ReadyNas box when I do the physical rebuild....see if it works.
The main lesson learnt is BACKUP BACKUP BACKUP...Cloud, Physical, Remote...DO NOT RELY on just one medium
[b]Joy of Joy - Successful Recovery of data from Netgear ReadyNas NV+ running X-Raid[/b]
Thanks to some digging around, logic and a failed attempt by Kroll Ontrack to recover data we have managed to recover all my data using Ubuntu and R-Studio.
Let me recap the original situation:
1 - ReadyNas NV+ Box running 4x1Tb drives in X-Raid Mode started to grind to a halt.
2 - Since the RadyNas Box didn't specify what drive was failing and ground to a halt I had no choice (foolishly with hindsight) but to try and pull out one drive at a time to see if the Box would reeboot and work out which drive was faulty.
3 - Because of this action the ReadNas NV+ Box did some "funny things" and resulted in showing me the Volumes but telling me that they were not available. The screen at the front told me 0/0...I THOUGHT THAT WAS IT
4 - Took my ReadyNas box to Kroll Ontrack and told them that the system was running on X-Raid (which I took to mean a form of RAID 5)
5 - Kroll Ontrack confirmed that one of the drives was partially corrupt and they could only image it at 85% but the other 3 drives were fine
6 - After 2 weeks they came back and said that they only managed to recover 1/3 of the files that I was supposed to have and told me that they were seeing the Disks as Striped NOT as Raid 5??? Anyways the data they could recover was useless to me so I thanked them and only paid for the diagnostic. At this point I would like to say that Kroll Ontrack were extremely professional, were always available to answer my questions and gave me regular updates...just didn't succeed with recovering all the data.
7 - Having got the RadyNas NV+ Back and under the suggestion of Kroll Ontrack, I made Images of all 4 drives using R-Studio Network and used the Byte by Byte Image copy to copy the 4 disks onto 2 3TB USB external drives. The R-Studio Image copy for the 4th drive I put the parameters of 20 attempts to read sector failures. Each drive took around 6 hours to image.
6 - R-Studio showed me that 3 of the 4 drives had 4 volumes and one drive had 0 volumes (the drive with 0 volumes was not the corrupt 4th drive but one of the good ones), also I could see that this second drive had data on it!
7 - Doing a lot of research on the internet (I had 2 weeks of twiddling my thumbs) I found that the ReadyNas NV+ box is bascally running linux and that people had success in connectig the drives and viewing content on Ubuntu.
8 - I called my friend Steve at Regenology and since they do hosting I thought that he might be able to help as he knows a lot about Linux for obvious reasons.
9 - The first thing he did was to copy the Volume Table from one of the images that had a Volume Table to the image of the drive that didn't have the Volume Table (we saw that the volume tables were identical for all 3 drives). The loss of this volume table on drive 2 was probably caused by the ReadyNas NV+ box Initializing the disk when I was doing the drive swap test!
10 - The next thing we did was to mount these images in Ubuntu, including the partially corrupt one, and using the "kpartx -a" command in the terminal (this is where it all got too technical for me) followed by a "vgscan" VOLUME C appeared!!!! This has all the DATA!!!. This was the guiding article - [url]http://home.bott.ca/webserver/?p=306[/url]
11 - After listing the folders in this volume and determining the size (just to make sure that data was there) we "rsync" all the data onto an external Drive
Next thing I will try is to do the volume table rebuild on the the physical drive 2 from the ReadyNas box, see if it boots with the 3 good drives and then throw in a 4th drive (in place of the corrupt one) and let it do what it is supposed to do and re-sync all the data - Even though I seem to have all the data now anyways I have learnt my lesson and doubling on everything.
Also I haven't been able to determined if the corrupted Disk 4 data has affected any of the files that I have recovered via this method. But in theory the ReadyNas box should rebuild everything....but now I am not afraid to try!!
A big thanks to R-Studio for giving me to tool to clone the drives (in an easy way) and also cloning the corrupt drive.
A big thanks to Kroll Ontrack, even though they didn't manage to get the data, they still gave me information that allowed me to think of this...and didn't have to spend a fortune!
A big thanks to the forums and the internet
A big thanks for nothing to Netgear for being USELESS in their support
A big thanks to this forum - Alt and magicm
[b]And finally a huge thanks to Steve at Regenology [url]http://regenology.co.uk/[/url] for doing the terminal work in Ubuntu [/b](we used Google Chrome Remote Desktop App for him to access my computer)
I will let you know how I get on with the ReadyNas box when I do the physical rebuild....see if it works.
[b]The main lesson learnt is BACKUP BACKUP BACKUP...Cloud, Physical, Remote...DO NOT RELY on just one medium[/b]