Sponsored Content
Operating Systems Solaris Solaris 10 upgrade exiting ( caught signal 11) Post 302404457 by incredible on Tuesday 16th of March 2010 02:19:25 PM
Old 03-16-2010
what model is the system? Is there amber LED seen ? Is the OS already installed and running? whats the obp from which you're upgrading to? what diagnostic? where is your output?
Smilie
Most of the time, OBP can be upgraded from multi-user but system will auto-reboot upon completion.
 

6 More Discussions You Might Find Interesting

1. AIX

process caught signal 5

Hello, We are using AIX 5.2 ML 7. One of the process in its log file said the following and stopped running. Caught signal=5, exiting. What would cause the signal 5 to be generated on an AIX box. Please advise. Thx Jerardfjay (2 Replies)
Discussion started by: jerardfjay
2 Replies

2. Solaris

Solaris 10 install issue - "Caught Signal 11"

Rebuilding a server (T2000) from a flash archive I created on another server. Using a Solaris 10/08 DVD to boot from the was going to point it tot he flash archive and pull it over NFS. I've done this many times with success until now. It initially boots off the DVD, you input the... (5 Replies)
Discussion started by: Probos
5 Replies

3. Solaris

Exiting signal 6

Hello all, I have a problem when installing Solaris 10 on Enterprise 450. I booted from dvd, then the installation was started. The error appeared after determining the installation method, F2-Standard, F?-Flash...... The error was Exiting signal 6. Please, need help. Thank you (4 Replies)
Discussion started by: Hardono
4 Replies

4. Solaris

Solaris 10 "Exiting (caught signal 11)"

I get an error after the initializing screen. I am using a DVD/ROM to boot up the installation on a Dell Inspiron 1520. Segmentation fault - core dumped. I have tried to restart multiple times. Please help (1 Reply)
Discussion started by: Jimasaurus
1 Replies

5. Solaris

Exiting (caught signal 11)

I created a new Virtual machine and was trying to install Solaris but keep getting this error.:confused: EXITING (caught signal 11) Type "install-solaris to restart" Can't find anything on Google. This is the iso image I am using "sol-10-u11-ga-x86-dvd" Followed all the instructions on... (5 Replies)
Discussion started by: newborndba
5 Replies

6. Shell Programming and Scripting

Continue Processing after a signal is caught

Is it possible to continue after signal is caught and control goes to function specified in the trap statement? (3 Replies)
Discussion started by: Soham
3 Replies
reboot(2)							System Calls Manual							 reboot(2)

Name
       reboot - reboot system or halt processor

Syntax
       #include <sys/reboot.h>

       reboot(howto)
       int howto;

Arguments
       howto   The howto argument is a mask of options passed to the bootstrap program.

	       The bits of howto are:

	       RB_HALT
		      the processor is simply halted; no reboot takes place.  RB_HALT should be used with caution.

	       RB_ASKNAME
		      Interpreted  by  the bootstrap program itself, causing it to inquire as to what file should be booted.  Normally, the system
		      is booted from the file "xx(0,0)vmunix" without asking.

	       RB_SINGLE
		      Normally, the reboot procedure involves an automatic disk consistency check and then multi-user operations.  RB_SINGLE  pre-
		      vents  the consistency check, rather simply booting the system with a single-user shell on the console.  RB_SINGLE is inter-
		      preted by the init(8) program in the newly booted system.  This switch is not available from the system call interface.

	       Only the superuser may a machine.

Description
       The system call reboots the system, and is invoked automatically in the event of unrecoverable system failures.	The system call  interface
       permits	only  RB_HALT or RB_AUTOBOOT to be passed to the reboot program; the other flags are used in scripts stored on the console storage
       media or used in manual bootstrap procedures.  When none of these options (for example, RB_AUTOBOOT) is given, the system is rebooted  from
       file in the root file system of unit 0 of a disk chosen in a processor-specific way.  Normally, an automatic consistency check of the disks
       is then performed.

Return Values
       If successful, this call never returns.	Otherwise, a -1 is returned, and an error is stored in the global variable errno.

Diagnostics
       The call fails under the following condition:

       [EPERM]	      The caller is not the superuser.

See Also
       crash(8v), halt(8), init(8), reboot(8)

																	 reboot(2)
All times are GMT -4. The time now is 08:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy