HP PART NUMBER: 461487-401A manual If expected volumes do not appear, try one of the following

Page 56

3.If the Insight Control server migration Boot CD ISO cannot detect the storage controller, you might need to reconfigure the storage controller environment variable.

a.Reboot the destination server to Rom-Based Setup Utility (RBSU) by pressing the F9 key during POST.

b.Select the Boot Controller Order option and verify the proper boot order for the storage controllers.

c.Press Esc to exit RBSU, and then press F10 to confirm the exit and to save your changes.

d.Reboot the destination server by using the Insight Control server migration Boot CD ISO. When the destination server boots, the Insight Control server migration Boot CD ISO will detect the storage controller.

Destination server displays a blank screen when it boots to server migration Boot CD ISO

The destination server might display a blank screen when it boots to the server migration Boot CD ISO if the server has more than 64 GB of RAM.

Suggested action

Try the following:

1.At the boot menu, press Esc to enter text mode.

2.At the text mode boot prompt, type sos mem=4G.

3.Press Enter.

Some storage volumes on the destination server are not available for selection

Some storage volumes configured on the destination server might not be available for selection in step 5 (Specify Destination Disks and Resize NTFS Partitions) of the migration wizard.

Suggested action

If expected volumes do not appear, try one of the following:

Verify that Insight Control server migration supports the storage controller. Volumes configured on an unsupported storage controller cannot be selected for migration. For more information about supported controllers, see HP Insight Management Support Matrix at http:// www.hp.com/go/insightmanagement/docs.

Run the Array Configuration Utility (if your storage controller is supported), and verify the status of the volumes on the Smart Array controller to be sure that the volumes are not in a failed state. Also, verify that all volumes on the controller are numbered sequentially beginning with Logical Drive 1, as required by the Insight Control server migration. If volumes are not numbered sequentially, clear the configuration and re-create the necessary volumes.

Static IP address cannot be assigned on the destination server while booting using the Boot CD ISO

Assigning a static IP address on the destination server might result in an error similar to the following:

The IP address xxx.xxx.xxx.xxx you have entered for this network adapter is already assigned to another adapter.

Cause

This issue might occur if the IP address is assigned to another network adapter on the destination server.

56 Troubleshooting

Image 56
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Postmigration tasks IV Troubleshooting and supportMigrating the servers Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Installing and configuring server migration software Server migration introductionOverview Related productsRight configuration Migration checklist Server migration conceptsServer migration components Overview of migrating a serverHP Insight Control server migration software tabs Migration screenHP Insight Control server migration software tabs Part II Premigration tasks Verifying system requirements for the application station Preparing hardware for migrationVerifying hardware and operating system support Planning the migration Resizing Linux file systems Preparing software for migration Verifying licenses for software to be migratedMigration security Disabling firewallsInstalling ProLiant Support Packs Installing Service Pack for ProLiantDisabling antivirus software Generating static or dynamic certificatesPreparing software for migration Part III Migration Preparing the source server and deploying the Source Agent Verifying Windows source server requirementsVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverRemoving guest tools Choosing server migration AgentsDeploying server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install screen Navigate to server migration Source Agent Linux Source Agent screen Prerequisites Linux destination size requirementPhysical destination servers 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 Source virtual machine prerequisitesSource physical server prerequisites SAN migrations in Windows Launching server migration by using the Deploy menu Starting the migration wizardLaunching server migration by using Quick Launch Identify the source serverQuick Launch Starting the migration wizard Installing ProLiant Support Packs after migration Installing Service Pack for ProLiant after migrationPostmigration tasks X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxViewing migration logs Validating the migrationValidating Linux migrations Validating Windows migrationsPart IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface HP SIM Source preparation Source server identification failsMigration Agent deployment fails Linux Source Agent window does not appear on Rhel 64-bitIncorrect LUN size is detected in of the migration wizard Perform any one of the following on the source serverDestination server identification fails Unable to boot Windows due to unsigned or corrupt driversDestination preparation Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Migration process Drivers cannot be installed or injected onto a boot diskLarge volumes fail with a server thread error Migration hangs if the source server is shut down 2011/03/14 141934 The job failedNtfs resize error message appears ReiserFS volumes are blocked for Linux migrationMigration fails during the disk cloning phase Error occurs during data copy of Linux migration SAN-connected destination server displays a blue screenDestination server boots with an invalid IP address HP Smart Array B320i controller name is not displayedLinux migration to servers with iSCSI storage fails to boot PostmigrationHidusb.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 How to contact HP Subscription serviceSupport and other resources Information to collect before contacting HPHP authorized resellers Related informationDocuments WebsitesTypographic conventions Related documentationTIP Documentation feedback Applying old server migration standalone licenses Premigration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter