Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using the latest VMware Converter Standalone to p2v a physical Windows 2000 Professional SP4 PC. The PC is a standard Pentium with IDE disk from circa 2001. The disk is 20GB partitioned logically into C: and D. It converts with no errors (I did both disks into one VMDK).

When I power on the VM in VMware Workstation 6.5 (or Vmware Player 2.5) it gets to the Win 2000 boot graphic then I get a BSOD with the classic 0x7B Stop error: inaccessible_boot_device.

Is there anything I can do to get the vm to boot? I am lost for ideas, normally p2v of a basic IDE pc works flawlessly.

I'm willing to put a bounty on this as I am trying to sort this out for a client urgently.

share|improve this question
What version of the service pack are you running? There are "Rollups" with SP4. – andyhky Jun 1 '09 at 19:56
up vote 0 down vote accepted

I injected the SCSI driver on the target VM by attaching the VMDK to an existing VM and copying the SCSI driver into the appropriate location

for 2000, vmscsi.sys for 2003, symmpi.sys

share|improve this answer

In instances where I've seen this before, I boot off of the Windows CD and choose to reinstall. It will then detect there's an existing installation and give you the option to repair it. Take that second repair option. You'll need to reinstall all the service packs again.

share|improve this answer
This worked for me, as well. Fired up like a charm after the repair. I'm guessing there was a device driver misfiring. – Kara Marfia Jun 3 '09 at 20:01

the reason this happens is the physical disk geometry has changed but the NTFS disk label is still using the old layout.

This blog post explains how to fix the issue on Linux while it's still a VM image. If it's too late for that, my advice is to get yourself a bootdisk like BartPE and run an NTFS rescue program.

Good Luck!

share|improve this answer
I don't understand. Why would the physical disk geometry change in the VM? It's never happened for Windows 2003 servers that I've P2Ved, I'm wondering if it's just a Win2000 thing. – PowerApp101 Jun 1 '09 at 9:42
I've just read the blog post - it's irrelevant here. I'm not resizing partitions, just creating a vm with target disks the same size as the source. No resize involved. – PowerApp101 Jun 1 '09 at 9:48
Well it depends if you have changed the physical disk size or layout during the conversion. If that has not changed then I suspect it's corrupted your image in some way. Boot your VM with a rescue disk image and see what you can find. – Sekenre Jun 1 '09 at 9:50
I can mount the vmdk with the vmware-mount tool ok. I can see all the files and folders in it. It just won't boot! – PowerApp101 Jun 1 '09 at 10:35

To be clear on the 'reinstall Windows 2000' you boot from Windows 2000 iso, don't follow the first Repair link, do an install, F8, then when it detects you already have Windows installed, do a repair from there. See for details.

share|improve this answer

It sounds like you have p2ved the individual drive partitions, not the whole disk. If this is the case you're probably missing the partition sector, and the boot block(s)

share|improve this answer
The converter only gave me the option to clone volumes (volume-based clone), there was no option for the entire disk. – PowerApp101 Jun 1 '09 at 9:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.