HP PART NUMBER: 461487-401A manual Multiboot kernel must be loaded before modules

Page 71

Unable to download the log files from the migration wizard when using IE 9

While using IE 9, you are unable to download the log files from the migration wizard.

Suggested action

Perform the following steps:

1.From the IE 9 browser, click Tools→Internet Options.

2.Click Advanced and navigate to Security section under Settings.

3.Clear the Do not save encrypted pages on disk check box.

4.Click OK.

This will enable you to download the log files.

Microsoft Windows 2008 R2 SP1 does not boot on ProLiant BL420c Gen8 with Emulex LPe1205A FC storage controller.

After a successful migration of Windows 2008 R2 SP1 to ProLiant BL420c Gen8 configured with Emulex LPe1205A FC storage controller, the OS does not boot up on the destination server.

Suggested action

Perform one of the following:

During migration, make PSP installation as the default option.

If a 'No Disk Error' is preventing the OS from booting after migration, reboot directly from the iLO console and disable the secondary storage controller driver - Emulex LPe1205A from the Windows Device Manager.

Migrate the OS with PSP uploaded in Upload Drivers tab.

Source server with SLES 11 SP2 x32 OS does not boot the operating system properly after successful migration

Source server with SLES 11 SP2 x32 OS does not boot the operating system properly after successful migration.

Suggested action

After the migration, restart the source server manually.

RHEL version 6.3 (x64) operating system does not boot after migrating to HP Dynamic Smart Array B120i/B320i Controllers

After performing a successful V2P migration of RHEL version 6.3 (x64), the operating system does not boot up on destination with HP Dynamic Smart Array B120i/B320i Controllers.

Suggested action

Perform the following:

1.Disable VT-d in RBSU.

2.Uninstall virtualization package before migration.

3.Remove the parameter "intel_iommu=on" in grub menu.lst.

RHEL version 6.3 (x64) operating system does not boot as destination after successful migration

After a successful X2V migration, the RHEL version 6.3 (x64) OS does not boot up on Hyper-V/ESX as destination and displays the following error message:

Multiboot kernel must be loaded before modules.

Postmigration 71

Image 71
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 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 Verifying system requirements for the application station Preparing hardware for migrationVerifying hardware and operating system support 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 Server migration wizard hangs TroubleshootingUser interface 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 wizardDestination 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 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