[Solved] int13_harddisk: function 15, unmapped device for ELDL=82

[Frustrated1]

I've been trying to get an image from an old 2003 server running for a couple weeks now. VB says it's running but the console screen remains black and doesn't accept any input. I've tried F12 and forced a boot from the first hard drive, same thing. I've upgraded VB to the latest version, no change. I've tried different converters on the VM, same thing. I saw something when googling this last week and saw something where ELDL=81 was a 2nd HD. This image has 2 HD's which seem to be recognized properly, at least they look ok on the status screen and in the log. Does the drive count start at 80 in which case 82 would be a 3rd drive? If so there is no 3rd drive on this machine.

Any ideas what might be causing this? Startup log is below:
[ModEdit; Partial log removed after the addition of a proper VBox.log]

[socratis]

Please avoid large chunk copy/pastes in the future...

Partial logs are not that useful. We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[Frustrated1]

I uploaded it to the original post. Thanks.

[socratis]

I've been trying to get an image from an old 2003 server running

The Physical-to-Virtual (P2V) is a rather delicate process, especially for something that old, which is not adaptable to hardware changes. The VM settings need to match as closely as possible the original computer, especially the hard drive controller. Do you have the original setup?

I've tried different converters on the VM, same thing

Like?

Have a look at the How to migrate existing Windows installations to VirtualBox article, and good luck, you're going to need it.

[Frustrated1]

It's running ok on a VMware server and I used the settings from that. I'll check again to see if anything is different.

[mpack]

IOAPIC defaults to on with VMware XP/2003 VMs. It defaults to off in VirtualBox, so turn it on.

[Frustrated1]

Thanks mpack, that did it! Running fine now.