inaccessable boot device

[Rustyb]

I have cloned a 4 gig hard drive to a 40 gig hard drive,
from old machine running win2k. I now want to put the 40
gig in a new fujitsu machine. When I reboot I get a BSOD
with inaccessable boot device.

How can I avoid this?

 

[Abhijeet Nigam [MSFT]]

hi,

I definetly believe their is some kind of MBR corruption or drivers Issues
Can please send me the hexadecimal code after stop error
using those codes I could know that what kind of BSOD your system is facing
You can try one step
boot from windows xp or windows 2003 or windows 2000 cd and got to recovery
console

their run the following commands
fixmbr and then press enter
fixboot and then press enter
chkdsk /r and then press enter





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

 

[Jetro]

If both BIOSes are or aren't ACPI-compliant and the chipsets are the same
make, you wouldn't have any problem. If chipsets are different, patch the
systems following the first link instructions. In-place upgrade helps almost
always and sysprep is the last resort before full reinstall.

http://support.microsoft.com/default.aspx?scid=kb;en-us;822052
How to troubleshoot "Stop 0x0000007B" error messages in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;EN-US;292175
How to Perform an In-Place Upgrade of Windows 2000

 

[Pegasus \(MVP\)]

I have cloned a 4 gig hard drive to a 40 gig hard drive,
from old machine running win2k. I now want to put the 40
gig in a new fujitsu machine. When I reboot I get a BSOD
with inaccessable boot device.

How can I avoid this?

This error is the result of Win2000 encountering different hardware,
not of any corruption. Running fixmbr, fixboot and chkdsk will not
resolve it. Check this link instead:

http://support.microsoft.com/default.aspx?scid=kb;en-us;824125

Check the MS Knowledge Base for further articles on
"Inaccessible Boot Device" (watch the spelling!).

 

[Flavio Borup]

A customer suffer from a Power Outage last saturday, and a WIn200+EXC 5.5
problem was solved using chkdsk /r app... IBM eSeries with RAID-0