Yep, with admin on this one.

Talking about forcing drives online, clearing and importing configs, cross-flashing RAID cards, swapping with incompatible cards, using "MegaRAID Storage Manager" ... I am sorry - I mean no offense - but you clearly do not know how RAID works on this system, and I would suggest next time you consult with an expert before doing anything on your own. Not understanding how RAID is implemented on your server can lead to catastrophic results, as you have seen.

It was already too late for a retag by the time you posted this.

Sounds like it will be a long night (and probably all day tomorrow too) restoring from backups.

Never ever force a drive online unless the array is failed and the drive you are forcing online was online previously. Forcing a new drive online is not a rebuild and simply puts the drive online as if it was previously part of the array with the same virtual disk block table and data as the other drives in the array. If the new drive was forced online successfully, it will not doubt immediately corrupt the array data as this new drive does not have the same parity data as the other drives.

Your only chance, and it is really slim, is to do a retag with the new drive.

Here is what you should do. Leave the new drive in and the other drives that were online and recreate the same array as what was previously there. VERY IMPORTANT, DO NOT INITIALIZE THE ARRAY. Then after the array is recreated and before you attempt to boot, remove the new drive. If you are able to boot, then insert the new drive and it should start to rebuild. If the rebuild does not start automatically, you need to set the new drive as a hot spare, and a rebuild should begin.

With that being said, it is likely that the drive that was force online corrupt the entire array data and you will likely have to restore the data from backup.

I don't think the OP has a backup to call upon as he stated "I have lost *EVERYTHING*. I am seriously up the creek if I have lost everything".

Been there, done that.. Learning can be painful but the moral of the story must be RAID is not a backup...

[edited to add following]
Oh, and if your data is important and you have no backups as seems the case, don't do anything else with the HDD's and instead contact a data recovery center pronto (big $$).

If your curious and want to understand some aspects of RAID data recovery, read this page and the referenced links but don't try a recovery data yourself if ineed the data is important to you...

Correct. I have no backups :( 

From knowledge it may help you 

1. Entering the PERC BIOS Configuration Utility
2. Controller Operations
3. Creating the Virtual Disk
4. Selecting Member Disks and Naming VD.
5. Finishing Steps
6. Initializing the Virtual Disk
7. Initializing the Virtual Disk

If you created multiple VDs, ensure the correct VD you wish to boot to is selected on the controller Management Screen.

For more information click here

thanks 

surya

No, no, and no. 

How about actually reading the post next time before you just start posting random answers.

From everything that I've read, that's the sure way to destroy everything beyond recovery.

Bummer about the backups. I wish I had better news for you.

I have reported the spam post.

Why are you using MegaRAID Storage Manager when your RAID is already managed by the H700 ?