[SOLVED] P2V Win Server 2003 STOP error 0x0000007b (mergeide.reg)

jaysol

Active Member
Jul 30, 2019
22
5
43
51
Hello,

I think I've tried everything at this point.

Unable to successfully P2V a Windows Server 2003.

The phsyical server is:
- Dell R210
- Dell AHCPI with C: drive running in AHCI auto
- C: drive is partitioned as "basic" (not dynamic)
- C: drive has no underlying software/hardware raid
- In devmgmt.msc the host controller listed as "Intel PCH SATA AHCI Controller"
- Driver in use believed to be C:\windows\system32\drivers\iastor.sys

IMAGING OF ORIGINAL:

Using clonezilla:
I've tried imaging as-is and restoring using a PVE drive type of ide, sata, = BSOD 7b stop
I've tried running mergeide.reg without rebooting windows 2003 and then booting into clonezilla and restoring that to PVE = BSOD 7b stop

Using an old Acronis TIB:
I've tried restoring an old TIB backup of same server to PVE drive type of ide,sata = BSOD 7bstop

QM CONFIG OUTPUT:
(as it is now - I've tried lots of things all = BSOD 0x7B STOP)

acpi: 1
balloon: 0
bios: seabios
boot: order=ide1;ide0;ide2;usb0
cores: 2
cpu: Nehalem
ide0: zfast-mfgdisk:vm-101-disk-0,size=150G
ide1: none,media=cdrom
ide2: none,media=cdrom
machine: pc-i440fx-5.2
memory: 2048
meta: creation-qemu=9.2.0,ctime=1744648184
name: PCS-SCADA2
net0: e1000=00:26:B9:8D:A2:B8,bridge=vmbr1,firewall=1
numa: 0
ostype: wxp
smbios1: uuid=3d35350e-56af-4610-a5d6-49178ef15296
sockets: 2
spice_enhancements: videostreaming=all
usb0: host=4-1,usb3=1
vmgenid: 19f02903-1668-47d1-84cc-d2415fbcb603


Any ideas would be appreiated.

I have a few servers like this I would like to migrate to proxmox, but I cant even get the first one done because of BSOD's :(
 
Can add:

tried hirens fix_hdc = BSOD 7B stop error

(hirens found IDE controller and copied pciide.sys)
 
my VM id is 101.... so I did this:

qm set 101 --delete ide0
qm set 101 --delete scsi0
qm set 101 --sata0 zfast-mfgdisk:vm-101-disk-0
qm set 101 --boot order=sata0

then boot into hirens, run fix hdc, it used iastor6.sys drivers, and worked. :)
 
  • Like
Reactions: Kingneutron
Nope.... I'm wrong. I was unable to reproduce this "success".

Not sure what the combination was to get it to work, but it happened after I ran fix_hdc.

first I ran fix hdc as ide presented by the vm - - tried and BSOD
then I ran fix hdc as sata presented by the vm - tried and it worked.

But now I cant reproduce. :(
 
it may be the final piece of puzzle is to use DISKPART to verify partiton is active.

diskpart
select disk 0
select parition 1
active
exit

I just did this, and it WORKED --- but, curiously, the partition was already *ACTIVE.

So who knows. It's a win. I'll take it.