HP Insight Foundation Software for ProLiant - Manual (Page 62)

Migration fails during the disk cloning phase
The following message might appear on the application station log (hpsmpsvc.log) if the
destination server disk has a Windows Logical Partition configured on it:
com.hp.mx.smp.vmdisk.api.APIException: Not enough space for partition!
Cause
An existing disk that already contains some Windows partitions is being used as the destination
for migration.
Suggested action
To resolve the issue, format the destination disk before you use it as a destination disk.
1. Reboot the destination server and press F9 to enter the BIOS settings of the destination server.
2. In the Advanced Options section, select Erase Boot Disk.
3. Rerun the migration process.
Starting a new migration after a current migration is stopped
If a migration is stopped by means other than a cancellation or failure, the application station,
source server, and destination server might not recognize that the migration has stopped.
Suggested action
To start a new migration:
1. Restart the migration agent on the source and destination servers.
2. On the application station, close the migration wizard.
3. Restart the Insight Control application service and the Insight Control server migration Web
Service.
4. Reopen the migration wizard.
Unrecoverable sector-read errors on the source server hard drive are not supported
and fail a Windows P2P or P2V migration
The following error message might appear if a volume that has unrecoverable sector-read errors
is migrated: Server Migration failed. ReadFile failed.
Cause
Hard drives automatically take corrective action when they have difficulty reading a sector. These
sectors are marked as “bad sectors” and relocated to one of the sparse sectors in a reserved area
of the hard disk. In these cases, no read error is produced, and the drive continues to function
properly. The data is lost and a read error is propagated to the operating system only if the surface
error rate is too high and additional sparse sectors are not available, or when the sector is
completely unreadable from the beginning.
If file system tools are used to detect these failing sectors (for example, CHKDSK /p /r), the
clusters are marked as “bad.” However, the data usually cannot be recovered. In such cases, the
system is not consistent, and proper migration is not possible.
Suggested action
Insight Control server migration does not support the migration of volumes that have unrecoverable
bad sectors.
62 Troubleshooting