HP Insight Control - Manual (Page 7)

Large volumes fail with server thread error..............................................................................66
Suggested action...................................................................................................................66
Migrating a Linux source server with very large storage fails when the migration is
initiated.......................................................................................................................................66
Suggested action...................................................................................................................66
Partitions created with third-party partitioning tools do not show proper file system type in
the server migration wizard.......................................................................................................67
Suggest action.......................................................................................................................67
Migration fails to terminate if source server is shut down........................................................67
Suggested action...................................................................................................................67
NTFS resize error message.........................................................................................................67
Cause.....................................................................................................................................67
Suggested action...................................................................................................................67
ReiserFS volumes are blocked for Linux migration...................................................................67
Cause.....................................................................................................................................67
Suggested action...................................................................................................................67
The File System on Source Disk \\.\PhysicalDrive0, Partition 0 Could Not Be Resized During
the Migration..............................................................................................................................68
Cause.....................................................................................................................................68
Suggested action...................................................................................................................68
Migration fails during the disk cloning phase...........................................................................68
Cause.....................................................................................................................................68
Suggested action...................................................................................................................68
Failed: Drivers Could Not Be Injected Into Boot Disk in the logs.............................................68
Suggested action...................................................................................................................69
Destination VM not powered off on HP integrated Citrix XenServers.....................................69
Suggested action...................................................................................................................69
Starting a new migration after a current migration is stopped.................................................69
Suggested action...................................................................................................................69
Unrecoverable sector-read errors on the source server hard drive are not supported and fail
a Windows P2P or P2V migration..............................................................................................69
Cause.....................................................................................................................................69
Suggested action...................................................................................................................69
Source agent fails to launch when source server reboots in migration agent mode.................69
Suggested action...................................................................................................................69
Error during data copy of Linux migration...............................................................................70
Cause.....................................................................................................................................70
Suggested action...................................................................................................................70
SAN-connected destination server displays blue screen...........................................................70
Suggested action...................................................................................................................70
Out of memory error occurs on the application station during migration................................70
Suggested action...................................................................................................................70
Destination server boots with an invalid IP address.................................................................70
Cause.....................................................................................................................................70
Suggested action...................................................................................................................70
Windows server migration Source Agent or PINT remote deployment fails with Agent is
already deployed or not required error.....................................................................................71
Suggested action...................................................................................................................71
Windows server migration Source Agent or PINT remote deployment is intermittent and
deployment fails with General failure occurred error..................................................71
Suggested action...................................................................................................................71
Post-migration ................................................................................................................................71
Destination server connected to SAN displays a blue screen after boot...................................71
Suggested action...................................................................................................................71
Table of Contents 7