Solved

Server 2003 crash ... new mobo / hd controller

Posted on 2007-04-05
4
215 Views
Last Modified: 2010-04-18
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?


0
Comment
Question by:paleface
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 1

Accepted Solution

by:
abisen earned 200 total points
ID: 18859870
There should be no danger to the existing data because of booting to Windows 2003 with the new motherboard and a HD controller.
0
 
LVL 6

Expert Comment

by:fixati0n
ID: 18859886
What error did you receive? Sounds like a possible HAL issue.
0
 
LVL 2

Assisted Solution

by:DRZCM
DRZCM earned 150 total points
ID: 18861117
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
 
LVL 8

Assisted Solution

by:Brain2000
Brain2000 earned 150 total points
ID: 18870332
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

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

More or less everybody in the IT market understands the basics of Networking, however when we start talking about Storage Networks, things get a bit dizzier, and this is where I would like to help.
In this article we have discussed the manual scenarios to recover data from Windows 10 through some backup and recovery tools which are offered by it.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question