setboot.1m (2010 09)

s
setboot(1M) setboot(1M)
setboot can’t set the specified boot path. type may be
primary, HA_alternate,oralter-
nate.
error accessing boot path - message
The message explains why. For example, you may not have permission (not be superuser) to change
parameters.
error accessing firmware - message
The firmware could not be read or written. The message explains why.
Failed to retrieve lun token
An error occurs when one of the boot paths is invalid (when running
setboot -r or
/sbin/init.d/setboot
). This kind of error occurs when there is no valid LUN entry
corresponding to the boot path or lunpath.
No dsf found
An error occurs while displaying boot paths when there is no valid LUN entry corresponding to the
boot path. For example, one or more of these situations has occurred regarding the persistent LUN
dsf entry:
• The persistent LUN dsf corresponding to the boot path (lunpath in stable storage) has been
removed (most likely with the
rmsf command).
• The boot path is set to a lunpath, but the associated HBA to that lunpath has been removed or
disabled.
• The boot path is set to a non-existent or invalid boot device in the I/O system.
• The session is run by non-privileged user, while some drivers require superuser privileges.
Invalid Arguments Passed to the invoked PDC routine
This is an internal error.
test not found in /etc/setboot_tests file
The test you specified is not defined for your system.
The firmware of your system does not support querying or changing SELFTEST
and FASTBOOT settings except through the boot-time console interface, ie,
BCH menu. Invoked PDC routine [option] not implemented. (On PA-RISC Platform
only.)
or
The firmware of your system does not support querying or changing the
SpeedyBoot settings. (On Integrity platform only.)
You have specified a SpeedyBoot option (
-t, -T,or-v) and your system does not have the firmware
to support SpeedyBoot. Currently, the Integrity platform does not support -t options.
Unknown error errno encountered by setboot(1M)
An unexpected error, number errno , was encountered while setboot was updating boot variable.
Warning: Autoboot flag must be on for autosearch flag to have effect
If the autoboot flag is off, automatic searching for a bootable system cannot occur, even if the
autosearch flag is on.
warning: invalid data in /etc/setboot_tests
The /etc/setboot_tests file contains tests that are not supported by setboot on your sys-
tem. Do not modify this file.
EXAMPLES
General
1. Set the primary path to
2/4.1.0 and enable the autoboot sequence:
setboot -p 2/4.1.0 -b on
2. Set the alternate path (using a persistent device special file) to /dev/disk/disk2 and enable the
autoboot sequence:
HP-UX 11i Version 3: September 2010 − 5 − Hewlett-Packard Company 5