HP Insight Control Software for Linux - Manual (Page 61)

Suggested action
Perform the following procedure:
1.
Close the server migration wizard.
2. Open Windows Services Manager, and then restart the Insight Control application service
and the Insight Control server migration Web Service.
3. Retry the migration.
NTFS resize error message appears
The following message might appear during the migration of certain NTFS volumes:
The file system on source disk x, partition y could not be resized
during migration. The NTFS volume information could not be read. Retry
the migration without resizing this volume. Defragmenting the NTFS
volume or performing a "chkdsk /f" prior to the migration may resolve
this condition.
Cause
This message appears when Insight Control server migration cannot process the NTFS meta
information for this volume, and the volume cannot be resized during migration.
Suggested action
Do not resize the volume. Instead, perform a disk defragmentation or run CHKKDSK /F to resolve
the issue. However, performing a successful defragmentation and disk check does not guarantee
the ability to resize. In this case, the volume can only be migrated without resizing.
ReiserFS volumes are blocked for Linux migration
A ReiserFS might be blocked during migration.
Cause
Any Linux partitions that are not yet written to the disk will be detected by server migration as RAW
in step 2 of the migration wizard.
Suggested action
Reboot the source server to force the partitions to be written. Alternatively, perform the following
steps:
1. Execute the following command on the source server and note the output:
cat /proc/sys/vm/drop_caches
2. Execute the following commands on the source server:
echo 3 > /proc/sys/vm/drop_caches
echo > /proc/sys/vm/drop_caches
Filesystem on source disk \\.\PhysicalDrive0, Partition 0 could not be resized during
the migration
The migration might fail with the following error: The file system on source disk
\\.\PhysicalDrive0, partition 0 could not be resized during the migration
in the logs.
Cause
One reason for the error could be that the migration wizard changes the Minimum Destination
Size and Destination Size fields to display 1 MB more than the Source Size field, even though a
Migration process 61