Server 2003 crash ... new mobo / hd controller

I have a server whose mobo crashed.  New mobo installed by same manufacturer but slight differences in contollers.  I had to add a sata controller card on this one to accept the hard drives.  The original setup had a mirror which was broken and no long in use.  So data was going to the c: and e: drives.  Running Server 2003 service pack 1.

I know the data was still entact.  and I do have a backup using NT backup.  After reassembly - the OS starts to boot .. makes it to the MS booting up panel then reboots.  Is there a risk to the data (there is an SQL database involved) to run a recovery console command like bootcfg /rebuild to get it to boot as orignally?  

Any suggestions?


palefaceAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

abisenCommented:
There should be no danger to the existing data because of booting to Windows 2003 with the new motherboard and a HD controller.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
fixati0nCommented:
What error did you receive? Sounds like a possible HAL issue.
0
DRZCMCommented:
I suggest booting up in safe mode and uninstalling all possible drivers and devices that might not work with the new Motherboard.  Then start up normally and reinstall your drivers  etc.  There should be no problem with your data.

DR Z
0
Brain2000Commented:
I've had this happen to me.  The first problem is, the controller is a different model, and therefore not working properly.  You should boot up into safe mode and install generic IDE/EIDE drivers.  Anytime you change a motherboard or controller card brand/model/etc..., make sure you have the generic disk drivers installed, or you'll blue screen with inaccessible_boot_device.

After doing step one, you may still have inaccessible_boot_device, especially if you had dynamic disks(as opposed to basic).  If so, there is a utility called Active Partition Recovery, which can recover partitions.  It will even convert dynamic disks to basic disks without losing any data.

Between the generic drivers, and APR.exe, you should be able to get the server back up and running.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.