Data Recovery and Disk Utilities Forum @R-TT

Perfect!

As stated in my previous post

with a RAID0 the fundamental part of the job, is to get both the drives images.

Then in my case with HEX editor, in your case with an automatic tool, you can get the parameters for R-Studio

Please note that your damage was really light, since automatic tools usually fails on serious filesystem damages or if they are missed some strategic sectors.

C.

[quote="Alt"]You don't have to scan the entire RAID, just 100 GB more than enough to see the results. You may continue to scan it later, if necessary. Just save the scan info.[/quote]

Ahh thanks. Wish I had known that before. My scans run from 9-10 hours.

Good news though is the last scan allows me to recover my files FULLY now. I still get some mismatch and MFT errors, but all my files that I recover open withouy any issues. You just saved me [size=200][b][color=#FF0000]$3400. [/color][/b][/size]

The files I was in danger of losing date back all the way to high school and I've spent the last two weeks researching and running scans with R-studio on a work laptop. I was really prepared to pay to get someone to recover it, but I'm glad I came across R-studio. I'm going to update my first post soon to let everyone know what I did and I how I got my files back. I am very happy right now. Just got the slow process of putting back 900+ GBs on new HDs in my laptop but all is well now. I am a happy to do a review on R-Studio.

THANK YOU SO MUCH. Your one comment practically saved my hard drive.

:D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D

You don't have to scan the entire RAID, just 100 GB more than enough to see the results. You may continue to scan it later, if necessary. Just save the scan info.

Here are the results from [b]Reclaime raid recovery[/b].

These instructions are provided for R-Studio version 5.1
1. Launch R-Studio

2. On the toolbar, click "Open image". Enter "E:\mx02.dsk" as the file name, click "Open"
3. On the toolbar, click "Open image". Enter "E:\mx01.dsk" as the file name, click "Open"
4. On the toolbar, click "Create Virtual RAID". Then, select "Create Virtual Block RAID" from the dropdown menu.

5. Right click the disk list on the right, select "Add E:\mx02.dsk" from the pop-up menu.
6. Right click the disk list on the right, select "Add E:\mx01.dsk" from the pop-up menu.

7. On the right side of the R-Studio window, set "RAID type" to "RAID0 (Stripe set)".
8. Below that, set "Block size" to "128 KB".
9. In the "Parents" table, enter "0 Sectors" as "Offset" in all rows.

10. Below the RAID diagram, click "Apply".
11. On the left panel, "Virtual Block RAID 1" is the newly created RAID. Double click it to start recovery.
Generated by ReclaiMe Free RAID Recovery build 1461, http://www.FreeRaidRecovery.com


I am now running a scan based on these parameters and instruction. Ill let everyone know results once it is done. I went out and purchased a 3TB external in place of the 2TB I had prior.

Thanks

[quote="Alt"]I think you can try this free software: [url=http://www.freeraidrecovery.com/]ReclaiMe Free RAID Recovery[/url] to detect RAID 0 parameters.[/quote]

Thanks for this. I will certainly try this later on today.

I get mixed results every time I change block size and disk order. The closest I got to recovering anything was with a 4KB block size with the disk in the default order they appear in the screens. It was the first time the folders did not have RED Xs on them. Some of my files recovered completely, but I still got some MFT and mismatch errors. Some pictures recovered, but were jumbled.

Hopefully this will help me set the right parameters and get a scan without those errors.

Thanks

I think you can try this free software: [url=http://www.freeraidrecovery.com/]ReclaiMe Free RAID Recovery[/url] to detect RAID 0 parameters.

So I've tried creating the block raid with drives in both orders and I'm still getting MFT mismatch and fixup errors. My pictures recover successfully, but some are jumbled up while some appear perfectly. None of my games open. The only thing I can think of is the block size is incorrect, since I have created two Virtual block raids with each drive being in a different order. Opening the drive files for different recognized partitions yields different results each time, but all of them give me mismatch errors. I'm going to try and reach out to the vendor today and see if they can give me a different block size and try to make the raid that way.

If the block size is incorrect, would this cause some problems?

So the deep scan finished today finally and I still had no red Xs on the directories I wanted to recover, but when I tried to open a file from a recognized partition it would still not open. My only guess now is that I put the drives in the wrong order when I created the virtual raid block. When I open a recognized partition, I get a lot of record child mismatch aborting and Fixup 1/2 errors which from what I have been researching means the drives are in the wrong order. Hopefully, putting the drives in the correct order will resolve the issue.

Can anyone chime in and let me know if I am making progress or not?

Thanks

So yesterday I setup the virtual raid block again with the images, but I set the block size to 4KB which is indicated under the properties for my drives in R-Studio. I stopped the scan mid way on the image, because it was set for 2 Days to complete and I was going to set parameters for to scan to speed it up. When I checked what it managed to scan during the time it ran, my user profile where all my files were on [b][color=#FF0000]DID NOT have a RED X[/color][/b] on it. I tried to recover a file, but it gave me another error that I can't recall but different than what I have been getting. I think I may have it now. I started the scan again and I would know by now except Windows updates rebooted my PC in the middle of the night and I had to start it again this morning.

I'll know later this afternoon how the scan turns out.

In the properties of my drive images, it list the index block size. Is that the block size I set in the Virtual Block Raid?