Well about a week ago I was fortunate to backup my RAID0 array for the first time in 3 years (yes I'm horrible) and if fate was on my side, 5 days later it all crashed.
In an effort to be brief, lets just say using Paragon Backup & Recovery 10 hasn't given me the best of luck, neither restoring to the original/rebuilt RAID0 array, or in its current form separated into three 640GB WD Blue drives. I've tried there WinPE to recover with little to no luck. Alternatively this is where I'm at now and while this may be a shot in the dark I figure ya'll would be the ones who could figure this out.
Having separated the RAID0 array after the crash in the Bios to 3 individual disks, I started rebuilding from scratch on Disk 1. Decided since the Recovery CD failed to recovery my already verified Image Backup that maybe if I rebuild and just load the program I can do a recovery through the Windows Environment. This however failed as well and Disk 2 and Disk 3 were left completely formated and blank.
After a couple of days of playing around I finally found a method of restoring and figured I'd do this on Disk 2 while my bare bones Windows 7 install on Disk 1 was being used. All went well, after 3 days finally some success!
Now, a minor issue (I say minor because I can now run that image off Disk 2 like I wanted and my data is intact
) is that I can't run this recovered image from Disk 2. If I set in the bios to run Disk 2 it gives me Boot Manager missing error. The information is ON THAT DISK, but having tried both methods known to fix the bootldr/mbr using the Windows 7 DVD, neither have worked. However, if I boot from Disk 1 then I get a boot prompt that says:
Windows 7 <-------------Disk 1's own bare bones Windows 7 install I used to recover
Windows 7 <-------------Boots to Disk 2
Memory Diagnostic
Now this is not making much sense to me. When I restored to Disk 2 from Disk 1 everything went fine, so what is causing Disk 1 to see both its own OS plus Disk 2's? I'm thinking that somehow during recovery Paragon got the bright idea of adding Disk 2's recovery partition into its boot manager, but nothing I've done has been able to rebuild the revcovered boot manager while booting through just Disk 2. Is this common or is there something I can do for those familiar with Paragon Backup & Restore to do to remedy the situation?
Like I said, it isn't a big deal right now because I can still access my original files although in an unusual way, but if I could solve this glitch I would. I still have the original backup image in case this is a Paragon issue thats my fault.
Thanks for any and all help in advance and sorry to make it so long lol.
In an effort to be brief, lets just say using Paragon Backup & Recovery 10 hasn't given me the best of luck, neither restoring to the original/rebuilt RAID0 array, or in its current form separated into three 640GB WD Blue drives. I've tried there WinPE to recover with little to no luck. Alternatively this is where I'm at now and while this may be a shot in the dark I figure ya'll would be the ones who could figure this out.
Having separated the RAID0 array after the crash in the Bios to 3 individual disks, I started rebuilding from scratch on Disk 1. Decided since the Recovery CD failed to recovery my already verified Image Backup that maybe if I rebuild and just load the program I can do a recovery through the Windows Environment. This however failed as well and Disk 2 and Disk 3 were left completely formated and blank.
After a couple of days of playing around I finally found a method of restoring and figured I'd do this on Disk 2 while my bare bones Windows 7 install on Disk 1 was being used. All went well, after 3 days finally some success!
Now, a minor issue (I say minor because I can now run that image off Disk 2 like I wanted and my data is intact
Windows 7 <-------------Disk 1's own bare bones Windows 7 install I used to recover
Windows 7 <-------------Boots to Disk 2
Memory Diagnostic
Now this is not making much sense to me. When I restored to Disk 2 from Disk 1 everything went fine, so what is causing Disk 1 to see both its own OS plus Disk 2's? I'm thinking that somehow during recovery Paragon got the bright idea of adding Disk 2's recovery partition into its boot manager, but nothing I've done has been able to rebuild the revcovered boot manager while booting through just Disk 2. Is this common or is there something I can do for those familiar with Paragon Backup & Restore to do to remedy the situation?
Like I said, it isn't a big deal right now because I can still access my original files although in an unusual way, but if I could solve this glitch I would. I still have the original backup image in case this is a Paragon issue thats my fault.
Thanks for any and all help in advance and sorry to make it so long lol.