Suggested action

61

Filesystem on source disk \\.\PhysicalDrive0, Partition 0 could not be resized during the

 

migration

61

Cause

61

Suggested action

62

Migration fails during the disk cloning phase

62

Cause

62

Suggested action

62

Failed: Drivers could Not Be Injected Into Boot Disk in the logs

62

Suggested action

62

Starting a new migration after a current migration is stopped

62

Suggested action

62

Unrecoverable sector-read errors on the source server hard drive are not supported and fail

 

a Windows P2P or P2V migration

62

Cause

63

Suggested action

63

Source Agent fails to launch when source server reboots in migration agent mode

63

Suggested action

63

Error occurs during data copy of Linux migration

63

Cause

63

Suggested action

63

SAN-connected destination server displays a blue screen

63

Suggested action

63

Out of memory error occurs on the application station during migration

64

Suggested action

64

Destination server boots with an invalid IP address

64

Cause

64

Suggested action

64

Windows server migration Source Agent or PINT remote deployment is intermittent and

 

deployment fails with a General failure occurred error

64

Suggested action

64

Unable to detect HP FlexFabric 10Gb 2-port554FLR-SFP+ Adapter configured as iSCSI disk

 

in step 5 of migration wizard

64

Suggested action

64

HP Smart Array B320i controller name is not displayed

64

Suggested action

65

Unable to install Service Pack for ProLiant (SPP) on Windows 2008 SP2 operating system after

 

successful migration

65

Suggested action

65

Linux migration to servers with iSCSI storage fails to boot

65

Suggested action:

65

Postmigration

65

Migration does not start after confirmation. The event log continuously displays Operation

 

Migration waiting for connection to source

65

Suggested action

65

Destination server mouse and keyboard do not work after a Windows migration

65

Suggested action

65

USB mouse or keyboard drivers are not loaded after an X2P Windows migration

66

Cause

66

Suggested action

66

Mouse does not work on the iLO of the destination server after a Linux X2P migration

67

Suggested action

67

Mouse does not work on the destination ESX virtual machine after a V2V migration

67

Suggested action

67

Drive letters are not the same in the migrated virtual machine guest after migration

67

Contents 7

Page 7
Image 7
HP PART NUMBER: 461487-401A manual Contents