Partitions created with third-party partitioning tools do not show proper file system type in the server migration wizard

Partitions created with third-party partitioning tools such as Gnome might not show the proper file system type in the server migration wizard. This does not affect migration.

Suggest action

Proceed with the migration.

Migration hangs if source server is shut down

In some network, firewall, or router configuration scenarios, Insight Control might fail to recognize that the source server is no longer available during a migration and remain in migration mode.

Suggested action

Perform the following procedure:

1.Close the server migration wizard.

2.Open the 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

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 cannot process the NTFS meta information for this volume, and the volume cannot be resized during migration.

Suggested action

To resolve this issue, 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 may 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:

56 Troubleshooting