Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

Rapid Deployment Pack

Knowledge base
» 

Server management

» Rapid Deployment Pack
Resources
» Evaluation license
» Training
» Altiris
» Unified Infrastructure Management
» HP Systems Insight Manager
» HP BladeSystem Management
» Integrity Essentials
» ProLiant Essentials
» Storage Essentials
Related products
» ProLiant servers
» ProLiant clusters
» ProLiant Essentials services
» ProLiant services
» New products
» Retired products
» ProLiant IT consolidation
» Special promotions
» Site map
announcing new products
What's new in IT? HP Virtual IT Center
IDC Business Value of Virtualization
 
Content starts here
The Target Server During A Linux Scripted Install Halts With "Error 22: No such partition" Shown On The Target Console

Article: 164

Applies to: Release 3.00 or greater

At the target server console, the following message may be observed:

   Booting 'Admin (not valid boot option)'

kernel (hd0,1)/init/kernel autoyast=nfs://0.0.0.0/usr/rdp/osconfig/default.cfg install=nfs://0.0.0./usr/rdp/osdist/osname pci=noacpi textmode=1

Error 22: No such partition

Press any key to continue...

This issue is seen when the target server is trying to boot to the default GRUB.IMG image landed by the Distribute Disk Image task in the Linux scripted install job. This is caused by either the Run Script - Create Boot Environment task failed with an error or the one-time boot to PXE functionality was not successful in Linux automation in order to start the Run Script - Create Boot Environment task.

To resolve this issue,

1. Check the Deployment Server console for an error with the job and correct accordingly. If the Run Script - Create Boot Environment task did not start and the server contains an iLO2 adapter, verify the minimum iLO2 firmware requirement is met. Refer to Knowledge Base article Minimum Firmware Requirements for Target Servers (Article 200).
2. If the job had a failure, either start the job over or retry the task. If the job had no failure, restarting the job or task is not necessary.
3. Manually reboot the target server and press F12 to have it boot to PXE.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.