Technical data

An Overview of nPartition Boot and Reset
Troubleshooting Boot Issues
HP System Partitions Guide: Administration for nPartitions, rev 5.1 192
Troubleshooting Boot Issues
On HP nPartition servers, you might encounter different boot issues
than on other HP servers.
The following boot issues are possible on nPartition servers.
• Problem: Not all cells boot to join (rendezvous) an nPartition.
Causes: Some cells may have their use-on-next-boot value set to “n”
(do not use), or the cells may have been powered off, or the cells may
have booted too late to participate in partition rendezvous, or the
cells have failed self-tests and cannot be used.
Actions: Check the cell use-on-next-boot values and change them to
“y” as needed then reboot for reconfig (shutdown -R). Check cell
power (frupower -d -C) and power on any cells as needed, then
reboot for reconfig.
As the nPartition’s cells reboot, observe the boot progress from the
nPartition’s VFP and note any problems the cells have proceeding
from one boot state to the next; as needed review chassis logs and
error logs using the service processor Show Chassis Logs (SL) menu.
• Problem: An nPartition takes a long time to boot (over ten minutes).
Causes: One or more cells assigned to the nPartition that have a “y”
use-on-next-boot value has not booted to participate in partition
rendezvous, thus causing the rest of the nPartition’s cells to wait for
ten minutes for the cell to report.
For example, the cell might not be installed, might be powered off, or
might have been powered on or reset too late to rendezvous with the
other cells.
Actions: You can avoid the delay by performing any of the following
actions, as needed. Perform a reboot for reconfig following any
changes you make.
— Set the cell’s use-on-next-boot value to “n” (do not use).
— Power on the cell.
— Unassign (remove) the cell from the nPartition.