FAILED: agent.internal.fault.PlatformError.summary - Partition:Invalid sector magic number.

[bduane]

Attempting to convert a power-on Windows Server 2003 source machine. There are two 40 GB drives in this server and they appear to be set up in a mirrored raid (i think i was mistaken here, computer managment shows the second drive as unallocated). Only about 10GB is used space, so I am setting it to resize the disk to 15GB. Conversion fails at 10%.

The GUI shows the error "FAILED: agent.internal.fault.PlatformError.summary"

I have attached the agent log. The following lines seem to be of interest:

2009-03-23 09:42:25.228 'App' 4664 info Partition:Invalid sector magic number.

2009-03-23 09:42:25.228 'App' 4664 info Disk number 1 has been skipped because of errors while reading partition table

2009-03-23 09:42:25.228 'App' 4664 info Partition:Invalid sector magic number.

2009-03-23 09:42:25.228 'App' 4664 info Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted

2009-03-23 09:42:25.228 'App' 4664 info Partition:Invalid sector magic number.

2009-03-23 09:42:25.838 'App' 4664 info Partition:Invalid sector magic number.

2009-03-23 09:42:25.838 'App' 4664 info Partition:Invalid sector magic number.

2009-03-23 09:42:25.838 'App' 4664 info Partition:Invalid sector magic number.

2009-03-23 09:42:25.838 'App' 4664 info Partitioning disk 0

2009-03-23 09:42:25.838 'App' 4664 info

-

---

2009-03-23 09:42:25.838 'App' 4664 info ....Creating MBR Partition Table ....

2009-03-23 09:42:25.838 'App' 4664 info ..... Partition Entry: 0 .....

2009-03-23 09:42:25.838 'App' 4664 info .....Current Partition Offset 0: .....

2009-03-23 09:42:25.838 'App' 4664 info .....Current Partition Offset 0: .....

2009-03-23 09:42:25.838 'App' 4664 info ...Boot Indicator: 0X80

2009-03-23 09:42:25.838 'App' 4664 info ...Partition Type Id 0X7

2009-03-23 09:42:25.838 'App' 4664 info ...Starting Head 1

2009-03-23 09:42:25.838 'App' 4664 info ...Starting Sector 1

2009-03-23 09:42:25.838 'App' 4664 info ...Starting Cylinder 0

2009-03-23 09:42:25.838 'App' 4664 info ...Ending Head 254

2009-03-23 09:42:25.838 'App' 4664 info ...Ending Sector 63

2009-03-23 09:42:25.838 'App' 4664 info ...Ending Cylinder 1023

2009-03-23 09:42:25.838 'App' 4664 info ...Relative Sectors 63

2009-03-23 09:42:25.838 'App' 4664 info ...Total Sectors 31471272

2009-03-23 09:42:25.838 'App' 4664 info

-

---

2009-03-23 09:42:25.838 'App' 4664 info Partition 0: offset: 0

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{aece0736-cd67-11db-aff1-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{93a63dc3-cd68-11db-aed0-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{93a63dc4-cd68-11db-aed0-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{aece0736-cd67-11db-aff1-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{93a63dc3-cd68-11db-aed0-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{93a63dc4-cd68-11db-aed0-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 info Scheduling cloning from source volume
?\Volume{aece0736-cd67-11db-aff1-806e6f6e6963}\ to destination disk 0 partition 1

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{aece0736-cd67-11db-aff1-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{93a63dc3-cd68-11db-aed0-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 verbose Found volume with name "
?\Volume{93a63dc4-cd68-11db-aed0-806e6f6e6963}\"

2009-03-23 09:42:25.947 'App' 4664 verbose GetDriveLetterOrMountPoint: Mount point for volume
?\Volume{aece0736-cd67-11db-aff1-806e6f6e6963}\ is C:

2009-03-23 09:42:25.947 'App' 4664 info Cloning volume C:

2009-03-23 09:42:25.947 'App' 4664 info Scheduling FileLevelCloningTask for execution...

2009-03-23 09:42:25.963 'App' 4664 info Prepared.

2009-03-23 09:42:25.963 'App' 4664 info Clone task preparation succeeded.

2009-03-23 09:42:25.963 'App' 4664 info Creating a snapshot for cloning...

2009-03-23 09:42:25.963 'App' 4664 info LiveImportSource::CreateSnapshot: Creating an atomic system-wide snapshot.

2009-03-23 09:42:39.744 'App' 4664 info LiveImportSource::CreateSnapshot: The snapshot is successfully created.

2009-03-23 09:42:39.744 'App' 4664 verbose Found volume with name "
?\Volume{aece0736-cd67-11db-aff1-806e6f6e6963}\"

2009-03-23 09:42:39.744 'App' 4664 verbose Found volume with name "
?\Volume{93a63dc3-cd68-11db-aed0-806e6f6e6963}\"

2009-03-23 09:42:39.744 'App' 4664 verbose Found volume with name "
?\Volume{93a63dc4-cd68-11db-aed0-806e6f6e6963}\"

2009-03-23 09:42:39.744 'App' 4664 verbose GetDriveLetterOrMountPoint: Mount point for volume
?\Volume{aece0736-cd67-11db-aff1-806e6f6e6963}\ is C:

[bduane]

I ended up using clonzeilla to create an image of the hard drive, restoring the image to a new virtual machine, then converting the virtual machine to reduce the disk drive. The process was made more painful due to the fact that I didn't have enough free space in my datastore to store the full size of the hard drive, so I ended up having to sue and external HD, it wasn't pretty.

I am running in to this same problem again today, this time I am trying to convert a Windows 2000 source. It failed at 17% with the same error, and the logs show the same "Invalid sector magic number."

This is at a different customer, different setup, suprised to see this error so frequently.

[POCEH]

You probably lost connection with NFC server. Did you try convertion again?

[bduane]

Not sure what the "NFC server" is, i am assuming that is the computer the vmware converter standalone is running on?

I this case I have not tried it again, but in the initial post, i tried it 2-3 times.

[bduane]

I'm running the VMware converter standalone on that server locally and it looks like it is getting much further.

Out of 9 servers total that i've tried to convert, 2 would not convert using VMware converter, even when trying to convert by installing VMware converter standalone locally.

The most recent one that is failing is a Windows Server 2003 computer. The event viewer shows that the converter agent service terminates unexpectedly. Within the converter (when running it local), i get an error within the converter why i try to view "Source Info", the error is something pertaining to file not found, but it doesn't specify what file.

[kresimir_pirkl]

Hello to everyone,

I had the same issue. After some troubleshooting I've concluded that this is a firewall problem. I had an ISA server involved and after opening port 902 everything worked like a charm.

Verify that source can access to port 902 on destination ESX server.

To do that open command prompt on source server and try:

telnet "x.x.x.x" 902

where x.x.x.x is IP of ESX server.

If the port is open you should receive this message:

220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtoco

l:SOAP, MKSDisplayProtocol:VNC ,

Also you could verify the route to the ESX server

tracert x.x.x.x

Regards,

Kresimir.

[POCEH]

Could you upload logs from failed convertion?