raid 1 data recovery

[kght22]

just upgraded motherboard and proc from fx8350 to r7 1700 and the new board's raid isn't compatible with the old one, is there an easy straight forward way for me to recover the data from my 3tb redundant raid short of rebuilding (and loading up) my old motherboard? (btw i wasnt even able to create a new raid0 and install windows on it on x370, the drivers weren't on the disk according to windows, well on the thumb drive i put the drivers from the disk on, on a prime x370-pro).

[NumLock21]

raid 1 has all the data.

[kght22]

windows can't read the data, won't let me mount either of the drives or anything, i've been able to scan and see the data only, and only using software that costs money to actually use.

[kght22]

windows sees "healthy gpt partition" on both drives, can't mount them to a drive letter, cant view the files at all.

[kght22]

this is quickly driving me to pirate bay, i shouldn't need special tools to recover data from a raid 1 drive, wtf.

[NumLock21]

11 minutes ago, kght22 said:

windows can't read the data, won't let me mount either of the drives or anything, i've been able to scan and see the data only, and only using software that costs money to actually use.

How did you setup your raid on your old system? Something tells me your setup is not done correctly.

do you have RAID 0 or RAID 1, there is a major difference between those 2.

 

10 minutes ago, kght22 said:

windows sees "healthy gpt partition" on both drives, can't mount them to a drive letter, cant view the files at all.

All 64bit OS supports GPT and it can be mounted.

[kght22]

1 minute ago, NumLock21 said:

How did you setup your raid on your old system? Something tells me your setup is not done correctly.

 

All 64bit OS supports GPT and it can be mounted.

i cannot click open or explore on either of the drives in disk management using windows 10 home x64, so much for that

[NumLock21]

Just now, kght22 said:

i cannot click open or explore on either of the drives in disk management using windows 10 home x64, so much for that

How did you setup your RAID in your old system?

[kght22]

Just now, NumLock21 said:

How did you setup your RAID in your old system?

hardware on a 970a chipset amd board nothing special, no special settings, just a default raid 1 from the bios.

[kght22]

phaw i'm gonna start rebuilding that 970a in another case, lemme know if ya got any ideas, i'd prefer not to go to pirate bay for something i shouldn't even need.

[NumLock21]

15 minutes ago, kght22 said:

hardware on a 970a chipset amd board nothing special, no special settings, just a default raid 1 from the bios.

Then it should not cause any problem, where your HDD cannot be read when it's in a new system. RAID 1 is basically 2 mirror drives of the same data. Done it plenty of times and they all read it, when I put it to another system. Your only option is to take the non modified HDD and put it back into the old system, then transfer what you want out of it to another drive. No need to rebuild. Rebuild is just recopying everything from the complete HDD into the incomplete one.

 

Did you setup raid through the raid setup utility?

[kght22]

19 minutes ago, NumLock21 said:

Then it should not cause any problem, where your HDD cannot be read when it's in a new system. RAID 1 is basically 2 mirror drives of the same data. Done it plenty of times and they all read it, when I put it to another system. Your only option is to take the non modified HDD and put it back into the old system, then transfer what you want out of it to another drive. No need to rebuild. Rebuild is just recopying everything from the complete HDD into the incomplete one.

 

Did you setup raid through the raid setup utility?

when i say rebuild i just mean i'm tossing the old board into another old case with its old psu and an old gpu, loading up windows, and recovering the data that way. and i set up the raid in the bios using ctrl+r, i guess you could call that a utility, i just call it the raid bios because i used to do the same stuff with old adaptec scsi cards that had a bios, although you could jump into those bios' from the dos prompt by executing a spot in memory, been a long long time lmao.

 

EDIT: actually already have it rebuilt, just about to start tossing a copy of windows onto an old 500gb hdd

[kght22]

i still would like a solution that doesn't involve hooking up one of the drives to the original motherboard or another with the same chipset/marvel controller. i've managed to pull 1.5tb of data off and that is enough for now, next time i do a mirror raid i guess it should be software based. none of the data is important just inconvenient to re download (steam library, origin library, a few unimportant backups, which are actually higher priority because they can't be re downloaded). actually at this point my problem is that the drive i wiped out is in two partitions with 700+gb on a partition that i can't format or change using windows disk management. meh, once i get the other drive cleared off i'll kill the problem on it using the original board then make a data mess throwing everything off the other to temp storage and kill it's issue on the original board, then just rebuild the mirror in windows instead of using hardware raid and put the data back. but it should definately not be this much of a headache for raid 1. clearly something was screwed up with am3+/marvell raid 1 because i should have been able to just plug one drive in and have access to the data easily. either way i was gonna have to temp dump the data though to rebuild a raid 1 on my new motherboard, that i expected, having to use the old motherboard just to see the data without paying for software.... wtf.

[kght22]

On 3/15/2017 at 11:20 PM, NumLock21 said:

Then it should not cause any problem, where your HDD cannot be read when it's in a new system. RAID 1 is basically 2 mirror drives of the same data. Done it plenty of times and they all read it, when I put it to another system. Your only option is to take the non modified HDD and put it back into the old system, then transfer what you want out of it to another drive. No need to rebuild. Rebuild is just recopying everything from the complete HDD into the incomplete one.

 

Did you setup raid through the raid setup utility?

as a response to you, ultimately i ended up just having to dump all of the data off to temps from one of the drives, then i (stupidly) rebuilt the raid on the new motherboard's built in raid, then copied the stuff back in. but now i am stuck on a ryzen platform with a hardware raid 1 again and no idea how i would properly recover if my motherboard failed, because i wouldn't buy the same board in that case, i would end up with the update/upgraded ryzen board. i've been dealing with computers since i was a kid in the early 90s, and raid since the late 90s, why won't they fucking standardize, i shouldn't have to rebuild my array or not be able to read it just because i changed my motherboard. btw, when i changed from one 970a motherboard to another 970a motherboard, the raid broke. wtf, same chipset, same chip for the sata controller, wtf. i expected it when i went to ryzen, but still, shouldn't have happend, why is raid so fucking non-standard? does that make even a hair of sense? i got it in the 90s, you had adaptec, and ibm, sun, actual competing standards that were different. raid 0 is raid 0 and raid 1 is raid 1, why do controllers have non standard protocols concerning those implementations? it makes no sense.

[seagate_surfer]

There's a 3rd party tool you might be able to give a shot called UFS Explorer Raid Recovery. It's not something that comes from us, but it is something that may be worth a shot here.