We help IT Professionals succeed at work.

RAID/Server 2003 Mirrored drive problem

Medium Priority
288 Views
Last Modified: 2012-05-07
Hello Experts! I have a question for you! I have a Microsoft 2003 Server with a mirrored RAID set. I'll be the first to admit, I am not the best at RAID configs, but DO know enough to get by. Having said that...I ASSUMED (we all know what that means), that there were 2 SATA 250 GB drives installed in a mirrored set AND that there was another BOOTABLE drive with the OS on it. NOT TRUE. THe drives WERE mirrored, but housed. I thought that the technician that they had before me, had never built the RAID properly (This was due to MANY other issues that I found in a short time). Nevertheless...I rebuilt the RAID losing all data. Or so I thought... I swapped drive 0 with drive 1 and the RAID resynced. I thought that I was out of the woods...not yet. The system would not boot into the OS. I then swapped drives again (back to their original posistions). Still no luck. Is there a way to make the drive boot again. I believe that all data is there and in tact, but I think that there may be a problem with the boot sector. Any ideas?
Comment
Watch Question

Commented:
If I read your question properly, you are concerned about recovering the data itself -- not about the OS.  I also am reading that we are dealing with software mirroring here?

The safe way is to quit messing with the existing drives for now.  Either put a spare drive into the server and load a base install, or hook up your existing drives to another system.  Go into disk management to activate the drive, then see if your data is good.

You can also boot off the 2003 install disk into recovery console and use command line to get to your data.

Finally, you could download a NTFS aware boot disk from the Internet and use it to recover your data.

Author

Commented:
That's part of the problem (unfortunately). I can't get to the OS to see what was installed. I can get to the "SAS Manager". I forgot to mention, this is a Dell PowerEdge (not sure of the model/not onsite). The drives show "Optimal" in the manager. and I don't have another swappable drive as of right now....

Commented:
OK, so we are talking about hardware RAID here.  I sure hope your data is actually there.

Go the route of the recovery console or a NTFS boot disk to bypass the OS (if you don't already have one, Google "download NTFS boot disk").  Understand that I am not talking about booting off the hard drive and hitting F8 -- I am talking about booting off a CD or floppy.  The Windows Server install disk will allow you to go to a command prompt recovery console which gives you a handful of dos-type commands.  A NTFS boot disk is going to give you access to a broader feature set to recover your data.

Once you are sure that your data is safe, delete your RAID container then re-create it.  If the disk is bad you will find out during this process.


Sorry for the difficult solution, but I have seen guys blow away any chance of data recovery by trying to repair a RAID setup.  I still painfully remember an entire night spent bailing out a colleague who wiped the RAID on a live DELL server trying to fix something, then discovered his backups were not running right.

Author

Commented:
The data isn't really a HUGE concern. They only use it for ONE program and the data is backed up already on a flash drive. I just don't want to have to rebuild the whole system if there's an easier way.
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
I rebuilt the Operating System. I thought I could work around it but this was the best answer. THANKS!
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.