How to Get Out of Single User Mode on HP-UX 11.0 K360

[Laurie_2]

Hi All,

I was having some problem and I converted
to a TRUSTED SYSTEM and then converted Back
and a co-worker powered down my server.

Now the box keeps coming up in single user
mode and I can't get it into mult user mode.

When I reboot (shutdown -ry 0) it keeps coming
up in single user mode. I think a co-worker
was playing with the keyboard trying to fix
the system console which is not hook up right.

HELP... What command do I need to do to get out
of this stupit single user mode...

Laurie

[Helen French]

Hi Laurie:

You need to investigate why it's going to single user mode ? Any warnings/errors ?

# init 3 - will take the system to run level 3 (multiuser mode)

Check system default init level in /etc/inittab

HTH,
Shiju

[James R. Ferguson]

Hi Laurie:

The 'init' level is specified in the first line of '/etc/inittab'. It should look like:

init:3:initdefault:

This will bring the system to run-level 3.

You can manually move to a level with 'init [n]'.

Have a look at the man pages for 'inittab(4)' and for 'init(1M)'.

Regards!

...JRF...

[James R. Ferguson]

Hi (again) Laurie:

Make sure you are trully stuck in single-user mode.

Do '/sbin/who -r' to determine the run level.

Are any of your filesystems mounted?

Regards!

...JRF...

[Pete Randall]

Laurie

Do a "/usr/sbin/setboot" to see what your boot parameters are set to. Interrupt the boot process and see what the AUTO file contains (if it had "hpux -is" that would be the culprit). That's all I can think of for now.

Good luck,
Pete

[MANOJ SRIVASTAVA]

Hi Laurie


init 2 will take you to multiuser mode with network disabled and init3 will take you to the multiuser mode with netwrok enabled . That should be initdefault in /etc/inittab file.


Manoj Srivastava

[Jeff Schussele]

Hi Laurie,

init 3
will take you into multi-user mode but before you do you need to see if you have any HW or other issues preventing atuoboot into multi.
Do a ctrl-b on the console then do a
ps
at the prompt - then
e
for errors
Look thru the list - you can sort if necessary & see if there any failures stopping the boot.
If you see nothing then
ma
back to main menu
and do
co
back to console & do the
init 3
When boot complete check the /etc/rc.log for any boot errors.

HTH,
Jeff

[Laurie_2]

Control B doesn't break the console...

I typed init 3 and nothing is happening...so
I figured I would wait...

It's a K360...are you sure it's Control B to
get into the GSP?

Laurie

[Pete Randall]

I don't believe there is a GSP on the K class models.

Pete

[James R. Ferguson]

Hi Laurie:

On K-class machines turn the KEY to the maintenance position. Then you should be able to do CTL_B ...

Regards!

...JRF...

[MANOJ SRIVASTAVA]

Laurie


type in co to get into the console mode , then try command like ls etc ? In you can see that then may be try mount -a and then init 2 or init 3.


Manoj Srivastava

[Darrell Allen]

Hi Laurie,

Any messages on the console?

Have you checked /etc/rc.log for clues?

Does mount or bdf show all the filesystems that should be mounted?

Does ioscan -fn show everything it should?

Have you any disks, etc that did not get powered up after the server was powered down? You need to always bring up peripherals before the CP.

I'm not sure but James makes me think: is the key in the correct (run?) position?

Darrell

[Pete Randall]

I stand corrected. Thanks JRF - I learn something new everyday around here.

Pete

[Jeff Schussele]

Dooooh.....I forgot that you stated K in the title.
Absent minded today I guess.....
Sorry, Pete's right - no GSP on K.
You should get the CM> prompt from ctrl-B though where you can enter
rs
to restart the system if init 3 is doing nothing.

Sorry,
Jeff

[Laurie_2]

OK i put the key back to service mode and
now I can do a CNTRL B.

However there is no PS otion.

Would RS be OK? I don't see a choice to look
at logs..RS seems the best choice.

It's still stuck in init 3 and nothing
is happening...

[Pete Randall]

Yeah, it's not a GSP but an "Integrated Access Port" and doesn't seem to offer much in the way of log access other than re-displaying the last 50 front panel status codes. At this point, do a reset.

[Jeff Schussele]

Hi Laurie,

Appears rs is your only choice at this point.
I'd follow the POST to see if there are any console warnings.

Rgds,
Jeff

[James R. Ferguson]

HI Laurie:

Do you have the /etc/rc.log checklist on the console? If so and if hung in a startup script do a CTL + pipe (|) to kill that script.
Have you changed a network component? DNS, NIS, NFS, etc?

Regards!

...JRF...

[Laurie_2]

OK I'm in init 3 (single user ?) can't telnet
to the box.

I mounted all the file systems..but the informix files won't mount. I run fsck and it
complains.

I can do a basic bdf command and see the OS.

What do I do now?

By the way, I forgot to power off and on
the drives, so that is why the disks are
corrupted.

Laurie (I'm glad this is a test system but
I didn't expect it to break so soon)

[Jeff Schussele]

Did you use the
-o full
option in the fsck command?
If not try it again.
Also be sure to use the raw disk device
i.e. /dev/rdsk/cxtydz
in the command.

Rgds,
Jeff

[MANOJ SRIVASTAVA]

Laurie

You may like to restart the inetd by just typing /usr/sbin/inetd ,. Also is it sensing the disks , incase not that then you need to powercycle them again .Once the disks are getting sensed then do a fsck -o full /dev/vgxx/rlvol* and then try to remount them using mount -a.


Manoj Srivastava

[Mark Vollmers]

Laurie-

you may need to umount the drives before you run fsck. depending on the mounts, you might actually need to go back to single user, since it won't check some file systems in multi-user mode.

Mark

[Laurie_2]

OK it's fixed now.

Control B:
I had to do a CM> rs then I interrupted
and BO PRI then I interrupted the ISL

ISL> hpux -is (I needed single user mode)

Then I did the following:

fsck -y
mount -a

I noticed that my /etc/inittab got wiped out
so I recreated that. I had to cp from
/usr/newconfig/etc/inittab to /etc/inittab.

init 2
then I went into init 3
and everything looks good now.

THANKS EVERYONE FOR YOUR HELP!
Laurie