Unable to boot into single user mode in Solaris 9

Hi, I am running Solaris 9 on one of my box.(Enterprise 2)

a)shutdown -i S -g 0 -y

b)shutdown -i s -g 0 -y

c)init 1

d)boot -s (from ok prompt)

e)boot -S (from ok prompt)

Tried Issuing the above mentioned commands brings the system to the below senerio:

******************************************************************************

INIT: New run level: S

......

Killing user process:done.

.......

INIT:SINGLE USER MODE

Type Ctrl-d to proceed with normal startup,

(or give root password for system maintenance):

<<Enter root password, press return>>

Entering System Maintenance Mode

ENTER RUN LEVEL(0-6,s or S):

======================================================

Enterting the below options at this point will bring the system to boot to default run level 3 (Multi-user mode)

a)1

b)s

c)S

However entering0 and3 works fine to bring the user to ok prompt and run level 3 (Multi-user mode) respectively.

****************************************************************************

Any help to advise on the get around solution for my above mentioned problem, solution as well as cause is greatly appreciated.

Thanks alot !

Regards

[1398 byte] By [AYukiea] at [2007-11-27 7:01:20]
# 1
's' is a startup mode. You should not try to enter that level after the machine has booted. You can move down to '1', but that may or may not be the same as booting into 's' on the way up for you.-- Darren
Darren_Dunhama at 2007-7-12 18:52:09 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 2
Hi guys,just 2 minor notes: 's' stands for single user mode. And for rebooting you should probably use init 6 (init 5 for machine shutdown).What's the reason you need to go into single user mode?Peter
Peter_Podsklana at 2007-7-12 18:52:09 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 3

ENTER RUN LEVEL(0-6,s or S):

is the big clue that something isn't right, like all the filesystems didn't fsck clean on boot

try another boot -s (either from ok prompt or reboot -- -s avoiding the shutdown scripts for now) and see if you're able to cleanly get into single

you obviously should be prompted to enter root password or control-d to multi, but once successfully authenticated, you *should* be presented with a shell

jeffrey.sa at 2007-7-12 18:52:09 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 4

> ENTER RUN LEVEL(0-6,s or S):

>

> is the big clue that something isn't right, like all

> the filesystems didn't fsck clean on boot

>

> try another boot -s (either from ok prompt or reboot

> -- -s avoiding the shutdown scripts for now) and see

> if you're able to cleanly get into single

>

> you obviously should be prompted to enter root

> password or control-d to multi, but once successfully

> authenticated, you *should* be presented with a shell

Erm i did try as stated in my post problem is i couldn;t get in .. i keep ending up in a loop ...

AYukiea at 2007-7-12 18:52:09 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 5

> Hi guys,

> just 2 minor notes: 's' stands for single user mode.

> And for rebooting you should probably use init 6

> (init 5 for machine shutdown).

> What's the reason you need to go into single user

> mode?

> Peter

Installation of Sun OS Patch Cluster

init 6 just reboot the machine I need to machine to go to run single user mode aka administration mode .

AYukiea at 2007-7-12 18:52:09 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 6

sounds like you had some sort of garble happen during patches

if you're able to boot to media or network -s, then try to mount up your /var partition and review the patch log summary from when you applied patches

in all reality, you need not go into single to apply patches, it's just Sun's way of stating "calm the box down" and stop all applications before patching as access to the machine can change and results (after patching) may vary......

I hope you were able to either take a backup or split a mirror "just in case" ....

jeffrey.sa at 2007-7-12 18:52:09 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 7

"ENTER RUN LEVEL(0-6,s or S):"

is not good. You've already told it what runlevel you want by typing init s.

what messages do you get with "boot -sv" from the OBP?

what were you doing before the problem?

Did you perform a clean boot before this to test that the server was 100% before doing whatever you did?

next thing would be to check the /etc/inittab file, otherwise it maybe looks like a DR restore.

Rob_BWa at 2007-7-12 18:52:09 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...