Filter
Top Products
Suggested action
Before you migrate, you must disable the AMD virtualization or Intel Hyper-Threading in the BIOS
of the destination server.
Migration process
Drivers cannot be installed or injected onto a boot disk
This error is reported if Insight Control fails to install or inject device drivers. In most cases, additional
information is reported on the destination server.
Suggested action
Possible causes and solutions for this error include:
• The boot partition was not migrated to the boot volume on the destination server. Verify that
the boot partition is selected for migration and placed on the boot volume of the destination
server.
• The network connection failed during driver installation.
• The destination server failed or was powered down during driver installation.
• The storage controller where the boot partition was placed is not supported. For a complete
list of supported controllers, see HP Insight Management Support Matrix at http://
www.hp.com/go/insightmanagement/docs.
• The iSCSI initiator failed to mount the disk. To resolve this issue, perform the following steps:
1. Clear the stale iSCSI session.
2. Restart iSCSI services.
3. Restart the server migration service, if required.
Large volumes fail with a server thread error
Migrating extremely large volumes (larger than 1 TB) can result in a failed migration with the
following message:
Server Migration failed. Error occurred in server thread; nested
exception is: java.lang.OutOfMemoryError
Suggested action
Server migration does not support the migration of volumes larger than 1023 GB. Reduce the size
of any partition that exceeds this size limit before you attempt migration.
Migrating a Linux source server that has large storage fails when the migration is
initiated
Migrating a Linux source server that has large storage might fail with the following error found in
the <Insight Control server migration Installation Folder>/log/
hpsmpsvc.log file:
java.lang.OutOfMemoryError: Java heap space
Suggested action
Increase the heap size on the source server, by performing the following:
1. Ensure that the source agent is not running.
2. Change the current working directory on the source server to the smpagent folder (for example,
/root/smpagent if the agent was automatically deployed).
Migration process 59