10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I got stuck in a very messy situation yesterday after attempting to resolve a filesystem full issue. The user reported that their filesystem (/var/DWS) was 100% full even after moving few files of sizes 14G, 30G and 50G out of the directory. I checked the filesystem once more after this... (5 Replies)
Discussion started by: anaigini45
5 Replies
2. UNIX for Dummies Questions & Answers
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies
3. AIX
Hello Forum,
I am very newbie with AIX.
We have 2 AIX 9111-285 servers. The OS version is 5.3.
After the power outage, they did not come up.
I try to unplug the power cable and re-connect after 1 minutes but do not help.
Both display the same reference code 110000AC on the front panel... (6 Replies)
Discussion started by: lilyn
6 Replies
4. Red Hat
Hi
im using centos 6.4
starting yesterday i have a strange issue that im unable to resolve. the system is booting to GRUB menu and the os is not starting. i tried to run a repair install and the message attached is what i get, what can cause this?
thanks, (1 Reply)
Discussion started by: guy3145
1 Replies
5. Solaris
We have a system that won't boot. It is Sun V245 that was patched yesterday with the latest Recommended 10 patch cluster. I will post what we get during the boot at the end of the email message. We have tried rebuilding the bootblk, booting from the cdrom, and running an fsck, booting into failsafe... (2 Replies)
Discussion started by: brownwrap
2 Replies
6. AIX
Hello:
Hope someone can help. Yesterday we did a mksysb backup of one of our AIX boxes and now the server is hanging at "Multi-User initialization completed" prompt.
Can someone help in troubleshooting this error? If you need more info please just let me know what you need. I'm not that... (17 Replies)
Discussion started by: bbbngowc
17 Replies
7. Solaris
Hi,
where can I check the system boot up log file like those message when the system booting up....
Thanks. (14 Replies)
Discussion started by: efang
14 Replies
8. UNIX for Dummies Questions & Answers
being nosey on sons laptop and set a password and now need to undo this but its in the boot system :eek::eek::eek: (4 Replies)
Discussion started by: hempel
4 Replies
9. UNIX for Dummies Questions & Answers
I have a diskless work station.
i want to boot from a remote linux machine.
what changes i will have to do in configuration.
Plz tell me
thanks (1 Reply)
Discussion started by: hemant29
1 Replies
10. UNIX for Dummies Questions & Answers
On my PC I have two hard disks, the first with Windows 98 SE and the second with Linux Mandrake 8.0 (Traktopel). When I have installed Linux, it has modified the boot record of the 1st HD and it has added a graphic menu (LILO) for selecting the OS to use. By default, if I don't press a key, Linux... (2 Replies)
Discussion started by: robotronic
2 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)