Inaccessible_boot_device

A

Alan C

I have had to replace a mainboard and cpu in a Win2k pro box, and
now on startup it BSD's with 'INACCESSIBLE_BOOT_DEVICE' . I guess
it is because the new m/board has a different chipset and the old
drivers don't like it. I have tried a repair of W2k with no
success.
Any ideas/tips/guidance on how to recover without doing a clean
install (and loosing data) would be greatly appreciated.

--
--------------------------------------------------------------------
---------
This message has been checked for all known viruses.

The information contained in this e-mail and any attachments is
confidential and may be the subject of legal, professional or other
privilege. It is intended for the named addressee only and may not
be disclosed to any other parties without the prior permission of
the originator.

Fight Spam! Join EuroCAUCE: http://www.euro.cauce.org
 
A

Abhijeet Nigam [MSFT]

Hi,

You can do a parallel install on the same machine
simply the way you do the normal install
and then you can try Big Copy

We completed a parallel install to another directory and brought it up to
the same
Service Pack level as the original installation.
We made a backup copy of the original installations System32 and
System32\Drivers
directories. We then performed a big copy of the System32 and
system32\Drivers
directory from the parallel to the original installation and selected yes
to
overwrite. <copy just the files and not the sub-directories>
Once the files were copied we rebooted selecting the original installation
from the
boot menu and successfully booted and logged on to the server.



Abhijeet Nigam
This posting is provided "AS IS" with no warranties, and confers no rights.
 
D

DL

You dont repair - R - its an inplace upgrade installation, as outlined in
the first para of the link
 
L

Lars

Alan,

"Inaccessible Boot device" I believe is something that
happens before W2k has had any chance of being stunned by
your new mainboard and cpu.

Does your Bios see the HD properly?
Is it IDE?
Do you now have more or fewer IDE devices than previously?
Had you somehow changed drive letters in Windows?

Often you can straighten out boot problems by starting a new
installation to the same partition and folder as previously,
but interrupting it at the very last screen before actually
overwriting Windows.

I have done similar replacement of major hardware several
times. The one method that has always worked has been to run
the sysprep tool in Windows prior to shutting down the last
time.

Sysprep comes with W2k resource kit.
You run it from command line or the "Run" box and with the
-pnp switch to make W2k cause hardware detection after first
reboot.

http://support.microsoft.com/support/kb/articles/Q216/9/15.ASP

I have had to replace a mainboard and cpu in a Win2k pro box, and
now on startup it BSD's with 'INACCESSIBLE_BOOT_DEVICE' . I guess
it is because the new m/board has a different chipset and the old
drivers don't like it. I have tried a repair of W2k with no
success.
Any ideas/tips/guidance on how to recover without doing a clean
install (and loosing data) would be greatly appreciated.


Lars
Stockholm
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Netware Volumes 3
Auto-archiving 1
Inbox will not archive 1
mci command handling window 2
Cannot Logon 2
IE6 window size 3
Sp2 Problem 2
Server not found - DNS error 2

Top