06-09-2011
Did u checked whether your disks (sd [b|c] ) are available after the reboot...
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Percent complete SCO 5.0.6 / No longer an issue (0 Replies)
Discussion started by: Henrys
0 Replies
2. AIX
I created a RAID 5 array and when I list out the attributes of the "hdisk" it reports back raid_level = 5 but the RAID level of the array = false. What does this actually indicate about my array? I've never paid much attention to this until now since I have a disk reporting failure I want to make... (0 Replies)
Discussion started by: scottsl
0 Replies
3. UNIX for Advanced & Expert Users
Hi guys,
i must install an old old old ml370 server...
I must create a RAID 5 with my 4 SCSI disk.
I need a SmartStart disk for create it or a Floppy Disk called "Array configuration Tool". I don't find it on the hp website...:mad::mad::mad:
Anyone have it??
Thanks in advance.
Zio (0 Replies)
Discussion started by: Zio Bill
0 Replies
4. Solaris
Hi Peeps,
Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it.
Anyone got any ideas on how to remove the EFI label?
Thanks in advance
Martin (2 Replies)
Discussion started by: callmebob
2 Replies
5. Emergency UNIX and Linux Support
One of my very old drive farm servers had an OS fault and can't boot now but I'd like to restore some files from it. I tried booting Ubuntu from a CD, but it couldn't see the drives -- possibly because they're RAIDed together. Is there a good way to get at my files?
The data in question is a... (2 Replies)
Discussion started by: CRGreathouse
2 Replies
6. Solaris
Hi, Here is the issue: There are 4 disks on this Sun x4150 system under Solaris 10, but only 1 disk can be seen by the OS. I've tried commands disks and devfsadm but not working. It's an important production server, so 'reboot -r' is not a choice.
# format < /dev/null
Searching for... (6 Replies)
Discussion started by: aixlover
6 Replies
7. Fedora
Hello world,
One of the servers, a Fedora one,rebooted today (Luckily, a testbox).
I tried to get the reason the server rebooted. After going through the messages, I think that the log entries just before and after reboot are missing.
Please below: (****** is the server name, for privacy... (0 Replies)
Discussion started by: satish51392111
0 Replies
8. Solaris
Hey everyone. First, let me start by saying I'm primarily focused on linux boxes, and just happened to get pulled into building two T5220's. I'm not super educated on sun boxes.
Both T5220's have 8 146GB 15k SAS drives. Inside the service processor, I can run SHOW /SYS/HDD{0-7} and they all come... (2 Replies)
Discussion started by: msarro
2 Replies
9. UNIX for Advanced & Expert Users
Thank you in advanced,
I had a Buffalo DUO crap out on me that was setup as RAID 0. I dont belive it was the drives but rather the controller in the DUO unit. I bought another external HDD enclosure and was able to fireup the two older DUO drives in it and I think I resembled the RAID... (12 Replies)
Discussion started by: metallica1973
12 Replies
LEARN ABOUT ULTRIX
reboot
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)