HP Virtual Connect Enterprise Manager Software manual Error during data copy of Linux migration

Page 58

Suggested action

Restart the application station and retry the migration.

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 with unrecoverable sector-read errors is migrated: Server Migrationfailed. 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 cannot usually be recovered. In such cases, the system is not consistent, and proper migration is not possible.

Suggested action

Insight Control does not support the migration of volumes with unrecoverable bad sectors.

Source Agent fails to launch when source server reboots in migration agent mode

Suggested action

1.To return to the original configuration, reboot the source server to Profile 1 Hardware Profile.

2.Remove server migration Source Agent Mode manually.

a.Right-click My Computer, and then select Properties.

b.Click the Hardware tab, and then select Hardware profiles.

c.Select server migration Source Agent Mode, and then click Delete.

3.Before starting a new migration, verify that all antivirus and firewall software is properly reconfigured or disabled.

Error during data copy of Linux migration

An Error during data copy offset=offset srcPos=source sector dstPos=destination sector amount=number of sectors message appears in the source or destination log followed by a I/O Exception.

58 Troubleshooting

Image 58
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPost-migration tasks ISO Contents Contents Applying old server migration standalone licenses Support and other resourcesGlossary Index Part I Overview and concepts Overview Installing and configuring server migration softwareServer migration introduction Related productsProduct Description Server migration components Migration checklistServer migration concepts Overview of migrating a serverHP Insight Control server migration software tabs Migration screenServer migration concepts Part II Pre-migration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying application station system requirements Planning the migration Resizing Linux file systems Migration Security Preparing software for migrationVerifying licenses for software to be migrated Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksGenerating static or dynamic certificates Part III Migration Verifying Linux source server requirements Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Preparing a Microsoft Hyper-V source serverDeploying server migration Agents Uninstalling guest toolsChoosing server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install dialog Navigate to server migration Source Agent Linux Source Agent screen Physical destination servers PrerequisitesLinux destination size requirement Virtual machine hostsBooting the destination server Manually creating and booting a virtual destination server ILO boot prerequisitesPrerequisites for VMware ESX migration Page Migrating the servers Minimum source server prerequisites for all migrationsPreparing for a Windows server migration If you use a firewall, see Disabling firewallsPreparing for a Linux server migration SAN migrations in Windows Launching server migrations using the Deploy menu Starting the migration wizardVerify Source Physical server Launching server migrations using Quick Launch Quick LaunchAvailable operations X2P post-migration tasks Windows Installing ProLiant Support Packs after migrationPost-migration tasks X2V post-migration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2P post-migration tasks LinuxValidating the migration X2V post-migration tasks LinuxViewing migration logs Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support Source preparation TroubleshootingUser interface Server migration wizard hangsSource server identification fails Migration Agent deployment failsLinux Source Agent window does not appear on Rhel 64-bit Suggestion actionIncorrect LUN size detected in of the migration wizard Destination preparationDestination server identification fails Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Large volumes fail with server thread error Drivers cannot be installed or injected onto boot diskMigration process Java.lang.OutOfMemoryError Java heap space ReiserFS volumes are blocked for Linux migration Ntfs resize error messageMigration hangs if source server is shut down Migration fails during the disk cloning phase Error during data copy of Linux migration Destination server boots with an invalid IP address SAN-connected destination server displays blue screenPost-migration Perform one of the followingHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Destination virtual machine fail to boot after X2V migration Server is unresponsive during PSP installationReboot the server and then reinstall PSP manually Support and other resources How to contact HPInformation to collect before contacting HP Documentation feedback HP authorized resellersRelated information Typographic conventions Related documentationTIP Applying old server migration standalone licenses Pre-migration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Glossary Index Index SIM Websites