11-08-2006
try to boot the system from the "ok" prompt with the option "boot -rs". if you reach the single user mode, type ctrl+d to go on to runlevel 3.
hth
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
When I came officce this morning I saw this error messages on the screen
-----
PANIC:srmountfun - Error 6 mounting rootdev hd (1/42)
Cannot dump 32639 pages to dumpdev hd (1/41) : space for only 0 pages
Dump not completed
--------
and machine was reboot mode. Why this problem... (3 Replies)
Discussion started by: alisev
3 Replies
2. UNIX for Dummies Questions & Answers
Hallo together,
I have a litle problem with some of my external devices.
If I type mount there are some "panic" massages.
Is this a real mistake or is this a normal behavior of a Solaris 8 system ?
/export/jumpstart on /dev/dsk/c5t4d0s7 read/write/setuid/intr/largefiles/onerror... (4 Replies)
Discussion started by: joerg
4 Replies
3. Filesystems, Disks and Memory
It happened twice this day. Suddenly SCO server display next message:
PANIC ktrap -kernel mode trap type 0X000000E
cannot dump 262045 pages to dump dev hd(1/41) space for only 131072 pages
Dump not completed
Then, server just wait to turn it off.
Why is it happening? :confused: (1 Reply)
Discussion started by: xto_r
1 Replies
4. UNIX for Advanced & Expert Users
I've got htis message on our sun U60 machine:
"Reboot after panic:errID 0x000004eff........." ,this message have been issued on the /var/adm/messages file & cause system rebooting randomly.
Any comment.
Thanks,
--Nikk (1 Reply)
Discussion started by: nikk
1 Replies
5. SCO
Hi Friends ,
i am getting the following error when iam booting a sco unix system.
------------------
H init
PANIC : srmountfun --Error 22 mounting rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages.
Dump not completed.
Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies
6. Programming
Hii can anyone pls tell how to limit the max no of message in a posix message queue. I have made changes in proc/sys/fs/mqueue/msg_max
But still whenever i try to read the value of max. message in the queue using attr.mq_curmsgs (where struct mq_attr attr) its giving the default value as 10.... (0 Replies)
Discussion started by: mohit3884
0 Replies
7. Solaris
Hi Guru's,
My Sun Fire v490 PRODUCTION server(Sol 5.9) has rebooted twice - on Apr'30 & May'08 2009.
And i found the following Error messages in /var/adm/messages file:
Apr 30 11:36:42 mumux201 unix:
Apr 30 11:36:42 mumux201 ^Mpanic/thread=2a1000c5d20:
Apr 30 11:36:42 mumux201 unix: ... (4 Replies)
Discussion started by: Hari_Ganesh
4 Replies
8. Red Hat
Hi,
one of our linux server got panic with the following messages
Jun 2 17:09:57 inchesfttu006 kernel: ------------------------
Jun 2 17:09:57 inchesfttu006 kernel: kernel BUG at kernel/exit.c:904!
Jun 2 17:09:57 inchesfttu006 kernel: invalid operand: 0000
Jun 2 17:09:57 inchesfttu006... (1 Reply)
Discussion started by: rajasekg
1 Replies
9. Solaris
A server that I am working on (SUN FIRE V240 , SOLARIS 10) doesn't boot because of a corrupted files system.
I tried to repair de file system, I also tried to to restore all the files systems with a backup of the server that I have but the message bellow appear
panic/thread=30002fc2060:... (8 Replies)
Discussion started by: feg
8 Replies
10. AIX
Dear all
i have two aix system
-Model : P770
-OS version: AIX 6.1
-patch level : 6100-07-04-1216
-ha version : HACMP v 6.1.0.8
-host : A, B
last Wednesday, my B system suddenly went down with crash dump. after 1 minute, A system went down with crash dump. I checked the dump of A-system... (6 Replies)
Discussion started by: tomato00
6 Replies
LEARN ABOUT POSIX
runlevel
RUNLEVEL(8) runlevel RUNLEVEL(8)
NAME
runlevel - Print previous and current SysV runlevel
SYNOPSIS
runlevel [options...]
OVERVIEW
"Runlevels" are an obsolete way to start and stop groups of services used in SysV init. systemd provides a compatibility layer that maps
runlevels to targets, and associated binaries like runlevel. Nevertheless, only one runlevel can be "active" at a given time, while systemd
can activate multiple targets concurrently, so the mapping to runlevels is confusing and only approximate. Runlevels should not be used in
new code, and are mostly useful as a shorthand way to refer the matching systemd targets in kernel boot parameters.
Table 1. Mapping between runlevels and systemd targets
+---------+-------------------+
|Runlevel | Target |
+---------+-------------------+
|0 | poweroff.target |
+---------+-------------------+
|1 | rescue.target |
+---------+-------------------+
|2, 3, 4 | multi-user.target |
+---------+-------------------+
|5 | graphical.target |
+---------+-------------------+
|6 | reboot.target |
+---------+-------------------+
DESCRIPTION
runlevel prints the previous and current SysV runlevel if they are known.
The two runlevel characters are separated by a single space character. If a runlevel cannot be determined, N is printed instead. If neither
can be determined, the word "unknown" is printed.
Unless overridden in the environment, this will check the utmp database for recent runlevel changes.
OPTIONS
The following option is understood:
--help
Print a short help text and exit.
EXIT STATUS
If one or both runlevels could be determined, 0 is returned, a non-zero failure code otherwise.
ENVIRONMENT
$RUNLEVEL
If $RUNLEVEL is set, runlevel will print this value as current runlevel and ignore utmp.
$PREVLEVEL
If $PREVLEVEL is set, runlevel will print this value as previous runlevel and ignore utmp.
FILES
/run/utmp
The utmp database runlevel reads the previous and current runlevel from.
SEE ALSO
systemd(1), systemd.target(5), systemctl(1)
systemd 237 RUNLEVEL(8)