08-14-2007
Hi,
From what i remember of an HP9000 (K) running hp11.00:
- interrupt the boot process by pressing any key (when asked)
- type bo pri (BOot PRImary path)
- reply No when prompted to interact with IPL
- at ISL prompt, fire the single user mode by: hpux -is
There are lots of docs about that just use the search option here or you might google as well
Good luck
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
why "vi" acts differently is single user mode?
Does anyone help ?
I am using "x" to delete and it keeps messing up.
Please help
Thanks (2 Replies)
Discussion started by: guest100
2 Replies
2. UNIX for Dummies Questions & Answers
how do you boot into single user mode?
RedHat 7.1
Caldera 2.4 (2 Replies)
Discussion started by: zorro81
2 Replies
3. UNIX for Advanced & Expert Users
Is there another way of switching to single user mode except by typing
/usr/sbin/shutdown 0 ???
:rolleyes: (5 Replies)
Discussion started by: kekanap
5 Replies
4. UNIX for Advanced & Expert Users
How to diable the single user mode..
what i want is dat my users are unable to boot in single user mode via GRUB.. (1 Reply)
Discussion started by: ankit.jss
1 Replies
5. AIX
Hi All,
I have AIX 5.1 & I forgot the root password. I find out the solution is to boot in single-mode and remove the root password from the /etc/passwd file. My question is how to boot in single-mode? Also is there any password required when booting in this mode? (9 Replies)
Discussion started by: aldowsary
9 Replies
6. UNIX for Dummies Questions & Answers
How to enter single user mode when UNIX/LINUX system is starting? (1 Reply)
Discussion started by: gkreddy
1 Replies
7. UNIX for Dummies Questions & Answers
hello ppl, someone must be able to help with this --> I have an old NCR tower 32 with an ADDS terminal running a unix version 020102 (Im not sure if thats correct but its unix for sure). I have no user names and no passwords and need to login to read a tape. Is there any way to do that? I hear... (3 Replies)
Discussion started by: orestis
3 Replies
8. Solaris
I have Sun 240 server with Solaris 8 installed. I go to OBP and try to boot in single-user mode but it is getting hung in the middle and the only way to get out of this situation is by going to the LOM and resetting the server. Here is what is happening:
{0} ok boot -s
SC Alert: Host System... (18 Replies)
Discussion started by: StarSol
18 Replies
9. Solaris
Hi everybody, I'm running soalris 10, and I would like to know if it posible to boot on single user mode(init s), and then set up (may be manually or not) all the networks services, did someone try this before??
Tks (4 Replies)
Discussion started by: jespada
4 Replies
10. Solaris
Dear All
I am trying to install my os as :
ok>boot cdrom - install
but receiving the following :
"IDprom checksum error
getexecname() failed
/sbin/rcS /etc/vfstab cannot create
INIT:failed write utmpx enrty
INIT:single user mode
INIT:execle of /etc/sulogin failed
Enter run level"
Can you... (6 Replies)
Discussion started by: hadimotamedi
6 Replies
WIPE(1) LAM TOOLS WIPE(1)
NAME
wipe - Shutdown LAM.
SYNTAX
wipe [-bdhv] [-n <#>] [<bhost>]
OPTIONS
-b Assume local and remote shell are the same. This means that only one remote shell invocation is used to each node. If -b is
not used, two remote shell invocations are used to each node.
-d Turn on debugging mode. This implies -v.
-h Print the command help menu.
-v Be verbose.
-n <#> Wipe only the first <#> nodes.
DESCRIPTION
This command has been deprecated in favor of the lamhalt command. wipe should only be necessary if lamhalt fails and is unable to clean up
the LAM run-time environment properly. The wipe tool terminates the LAM software on each of the machines specified in the boot schema,
<bhost>. wipe is the topology tool that terminates LAM on the UNIX(tm) nodes of a multicomputer system. It invokes tkill(1) on each
machine. See tkill(1) for a description of how LAM is terminated on each node.
The <bhost> file is a LAM boot schema written in the host file syntax. CPU counts in the boot schema are ignored by wipe. See bhost(5).
Instead of the command line, a boot schema can be specified in the LAMBHOST environment variable. Otherwise a default file, bhost.def, is
used. LAM searches for <bhost> first in the local directory and then in the installation directory under etc/.
wipe does not quit if a particular remote node cannot be reached or if tkill(1) fails on any node. A message is printed if either of these
failures occur, in which case the user should investigate the cause of failure and, if necessary, terminate LAM by manually executing
tkill(1) on the problem node(s). In extreme cases, the user may have to terminate individual LAM processes with kill(1).
wipe will terminate after a limited number of nodes if the -n option is given. This is mainly intended for use by lamboot(1), which
invokes wipe when a boot does not successfully complete.
EXAMPLES
wipe -v mynodes
Shutdown LAM on the machines described in the boot schema, mynodes. Report about important steps as they are done.
FILES
$LAMHOME/etc/lam-bhost.def default boot schema file
SEE ALSO
recon(1), lamboot(1), tkill(1), bhost(5), lam-helpfile(5)
LAM 6.5.8 November, 2002 WIPE(1)