Migration of Windows 2003 server to Proxmox VE

[cyrofilho]

Hello all,

I have followed the guide:

http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE

To migrate my windows 2003 server to a kvm virtual image. But after the first start within proxmox ve, the windows 2003 gets corrupted. The message that appears is:

Windows could not start because the following file is missing or corrupt:

\WINDOWS\SYSTEM32\CONFIG\SYSTEM

And then it suggest to use the recovery console from windows 2003 install disk!

What am i doing wrong? I would really apreciate any help.

Thanks.

 

[tom]

Hello all,

I have followed the guide:

http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE

To migrate my windows 2003 server to a kvm virtual image. But after the first start within proxmox ve, the windows 2003 gets corrupted. The message that appears is:

Windows could not start because the following file is missing or corrupt:

\WINDOWS\SYSTEM32\CONFIG\SYSTEM

And then it suggest to use the recovery console from windows 2003 install disk!

What am i doing wrong? I would really apreciate any help.

Thanks.

never got such an issue here, maybe a hardware fault, e.g. on your disk system? do you have a hardware raid system?

I always tested with win2003 sp2 systems.

 

[cyrofilho]

Yes the physical server had hardware raid! Can i still p2v it?

 

[tom]

Yes the physical server had hardware raid! Can i still p2v it?

yes, but the question is if a hardware fault breaks the migration.

 

[cyrofilho]

I tryed two times and got the same error! And i did not see any erros during the process! Thanks.

 

[dietmar]

And what happens if you start the recovery console and check the filesystem - does it work then?

- Dietmar

 

[dietmar]

We also got that error here one time. After repairing the boot block it works again.

- Dietmar

 

[serverBaboon]

Me Too

I too have had this problem several times with two machines I coverted from VMWARE server. I have also repaired one of the machines several times but it still occassionaly fails. I have not yet had the time to try building a fresh W2k3 machine from scratch to see if this is a conversion issue or not.

I have at various times repaired the boot block and or the file system, although one time this file system repair corrupted the Active directory partition (it is a DC).

The error nearly always occurs after the initial boot (after transferring to proxmox) where the device detection occurs.


I haven't mentioned this yet as I have been too busy to investigate this yet. I will try and build a new machine this week.

 

[tom]

I too have had this problem several times with two machines I coverted from VMWARE server. I have also repaired one of the machines several times but it still occassionaly fails. I have not yet had the time to try building a fresh W2k3 machine from scratch to see if this is a conversion issue or not.

I have at various times repaired the boot block and or the file system, although one time this file system repair corrupted the Active directory partition (it is a DC).

The error nearly always occurs after the initial boot (after transferring to proxmox) where the device detection occurs.


I haven't mentioned this yet as I have been too busy to investigate this yet. I will try and build a new machine this week.

we got this on a fresh installed one, but only one time. the machine war running for more than 3 weeks with several reboots due to configurations. after fixing the boot loader everything is running again as expected.