09-26-2008
the "reboot-on-error" has nothing to do with an hardware error... this stops the mashine from rebooting if it wasn't shut down cleanly!
so, after a panic the mashine won't boot if "reboot-on-error" is set to false...
10 More Discussions You Might Find Interesting
1. Solaris
My Solaris10 cannot boot after I made an error when apending the vfstab to:
dev to mount======/dev/dsk/c0d0p1:1
device to fsck====== <blank>
mount pt=========/Data
FS Type==========pcfs
fsck pass=========-
mount at boot=====yes
mount options===== <blank>
My 'Data' partition is a... (3 Replies)
Discussion started by: maag
3 Replies
2. Solaris
I modified the partitions on my Solaris 10 disk using format command in "boot cdrom -s" mode and then tried rebooting with "reboot". It said "Boot load failed".
Why does this happen?
I have faced this error before:( and I went in for a fresh installation of the OS.Can anyone tell me the reason as... (1 Reply)
Discussion started by: lydiaEd
1 Replies
3. UNIX and Linux Applications
Hi everybody.
I have an old IBM RS6000 Model 7025 F80 with AIX 4.3.3 installed with 2 primary scsi disks. I want to install linux (any flavor) on it. I downloaded and burned an iso image of debian (http://cdimage.debian.org/debian-cd/4.0_r4a/powerpc/iso-cd/debian-40r4a-powerpc-netinst.iso),... (3 Replies)
Discussion started by: pitagoras
3 Replies
4. Solaris
Hi all,
I'm freshman in this forum. I'm here to ask for your help. A case about Sun Fire V490. But, before starting to ask, I want to tell you the story.
Last week, I was told about a failed V490 in Da Nang City (Vietnam). It could NOT boot. After diagnosing it remotely, I found that the... (6 Replies)
Discussion started by: nam.nguyen
6 Replies
5. Solaris
Hi all,
when am rebooting the server (SF v890) we are facing
"open boot diagnostic failed".
Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies
6. Solaris
Hi guys. I have an old Netra T1 that I'm hoping to recover here so I can twiddle around with Solaris 10.
It's been unable to power on despite issuing the "poweron" command or hitting the switch at the back of the server for some time. The LOM command "env" reports ALARM3 ON and everything else... (8 Replies)
Discussion started by: detach8
8 Replies
7. Solaris
Good evening all,I'm new to your site, so please bear any infringements or transgressions on my part.I'm new to the whole Solaris boot install over the net scenario, but here's where I'm stuck:I have an M5000 with 2 domains (running unimode). Domain 0 is configured and running Solaris 10. Domain 1... (9 Replies)
Discussion started by: RandomSun
9 Replies
8. Solaris
Hi Everyone.
What is the differece b/n ALOM and ALOM CMT Service processor.
I am trying reset ALOM login/passwd using scadm utility on T2000, while I am googling I came cross ALOM CMT doesnt support scadm utility, but ALOM supports.
Not sure how different are these.
Thanks, (0 Replies)
Discussion started by: bobby320
0 Replies
9. Solaris
Dear all,
I have a solaris 10 in my environment (VMware virtual machine). recently I increased the harddisk size from the VMware and reboot my server. after reboot the os is unable to boot and gives the below error message.
exec(/sbin/init) file not found
press any key to restart
... (3 Replies)
Discussion started by: krishna001
3 Replies
10. Solaris
I have M10-1. Installation OS 10 from cdrom external.
Here message from OK Prompt
{0} ok probe-scsi-all
/pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1/cdrom@1
Unit 0 Removable Read Only device HL-DT-STDVDRAM GP65NB60 PF00
But..
{0} ok boot... (3 Replies)
Discussion started by: mbahjiman
3 Replies
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - stopping and restarting the system
SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ]
/sbin/halt [ -lqndars ]
/sbin/fastboot [ -lqndarsRD ]
DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is
necessary to read it in from disk or tape each time it is to be boot strapped.
Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put
the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first.
Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware
time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk
check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation.
Options to reboot are:
-l Don't try to tell syslogd(8) what's about to happen.
-q Reboot quickly and ungracefully, without shutting down running processes first.
-n Don't sync before rebooting. This can be used if a disk or the processor is on fire.
-h Don't reboot, simply halt the processor.
-d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic.
-a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix).
-r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD.
-s Don't enter multi-user mode after system has rebooted - stay in single user mode.
-f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by
passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt)
flag.
-D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program.
-R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the
root/swap/pipe/dump device.
Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are
present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this
case.
Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively.
Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are
intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user
operations.
SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8)
3rd Berkeley Distribution May 24, 1996 REBOOT(8)