HP PART NUMBER: 461487-401A manual Error occurs during data copy of Linux migration

Page 63

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.

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

Suggested action

Try the following:

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 you start a new migration, verify that all antivirus and firewall software is properly reconfigured or disabled.

Error occurs 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 an I/O exception.

Cause

Bad blocks might exist on the source or destination disk.

Suggested action

Insight Control does not support migrations of disks that have bad blocks. If the bad block is on the destination disk, change the destination disk.

SAN-connected destination server displays a blue screen

Suggested action

To migrate Windows Server 2003 to a SAN-connected destination server, install the following on the source server:

Service Pack 1

Service Pack 2

Updated Storport storage driver (for more information, see http://support.microsoft.com/kb/ 932755)

Migration process 63

Image 63
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents IV Troubleshooting and support Migrating the serversPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Related products Installing and configuring server migration softwareServer migration introduction OverviewRight configuration Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsHP Insight Control server migration software tabs Part II Premigration tasks Preparing hardware for migration Verifying hardware and operating system supportVerifying system requirements for the application station Planning the migration Resizing Linux file systems Disabling firewalls Preparing software for migrationVerifying licenses for software to be migrated Migration securityGenerating static or dynamic certificates Installing ProLiant Support PacksInstalling Service Pack for ProLiant Disabling antivirus softwarePreparing software for migration Part III Migration Preparing a Microsoft Hyper-V source server Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Verifying Linux source server requirementsDeploying Agents Removing guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install screen Navigate to server migration Source Agent Linux Source Agent screen Virtual machine hosts PrerequisitesLinux destination size requirement Physical destination serversBooting the destination server ILO boot prerequisites Manually creating and booting a virtual destination serverPrerequisites for VMware ESX migration Page Minimum source server prerequisites for all migrations Migrating the serversIf you use a firewall, see Disabling firewalls Preparing for a Windows server migrationSource virtual machine prerequisites Preparing for a Linux server migrationSource physical server prerequisites SAN migrations in Windows Starting the migration wizard Launching server migration by using the Deploy menuIdentify the source server Launching server migration by using Quick LaunchQuick Launch Starting the migration wizard X2P postmigration tasks Windows Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration Postmigration tasksX2V postmigration tasks Windows Edit the boot.ini file to activate a graphical boot processX2V postmigration tasks Linux X2P postmigration tasks LinuxValidating Windows migrations Viewing migration logsValidating the migration Validating Linux migrationsPart IV Troubleshooting and support Troubleshooting User interfaceServer migration wizard hangs HP SIM Source server identification fails Source preparationLinux Source Agent window does not appear on Rhel 64-bit Migration Agent deployment failsPerform any one of the following on the source server Incorrect LUN size is detected in of the migration wizardUnable to boot Windows due to unsigned or corrupt drivers Destination preparationDestination server identification fails Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Drivers cannot be installed or injected onto a boot disk Large volumes fail with a server thread errorMigration process 2011/03/14 141934 The job failed Migration hangs if the source server is shut downReiserFS volumes are blocked for Linux migration Ntfs resize error message appearsMigration fails during the disk cloning phase SAN-connected destination server displays a blue screen Error occurs during data copy of Linux migrationHP Smart Array B320i controller name is not displayed Destination server boots with an invalid IP addressPostmigration Linux migration to servers with iSCSI storage fails to bootHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Guest OS ID guest name is not valid Server is unresponsive during PSP installation Multiboot kernel must be loaded before modules Suggested action Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesWebsites HP authorized resellersRelated information DocumentsRelated documentation Typographic conventionsTIP Documentation feedback Applying old server migration standalone licenses Basic hardware design of a three-node duster Premigration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter