Sponsored Content
Operating Systems Solaris Solaris 10 booting from EMC SAN DISK Post 302756241 by DukeNuke2 on Tuesday 15th of January 2013 12:40:23 PM
Old 01-15-2013
because there is no such thing as "- r" as an argument for the boot command. after setting the bootdevice try to use
Code:
init 6

to reboot the server.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris 10 not booting with mirrored disk

Hi all, I have a V490 running with Solaris 10. The OS disk was mirrored. I wanted to break the mirror, boot with the secondary mirror, and re-mirror the OS with a new disk. This is what I did, detached the metadevices of the secondary mirror disk (disk 1) metaclear-ed the metadevices,... (1 Reply)
Discussion started by: nitinp82
1 Replies

2. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies

3. AIX

Configurin EMC SAN disks on AIX

This may sound like an absolute rookie question, and it is. I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards. Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch. Can someone... (1 Reply)
Discussion started by: ronellevan
1 Replies

4. AIX

hard disk and san

Hello everyone I got several aix boxes with aix 5.3 I got a ibm san ds4500 My question is How can I do a match between my disks on aix and the san? I try to do a match with the LUN but for example. In my san I got several 1 LUN and on one of my aix box I got this If I type lscfg... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies

5. Solaris

SAN disk failure

hi all, have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ?? thanks in advance. (3 Replies)
Discussion started by: cesarNZ
3 Replies

6. UNIX for Dummies Questions & Answers

Booting off of a SAN

Hello, I'm posting this in the "Unix for Dummies" forum, since it is more of a theoretical question than an exact problem/fix I'm inquiring about. I have a SunFire T2000 server with 4 internal hard drives, running Solaris 10. (So far so good :) The company just purchased a large EMC SAN. ... (5 Replies)
Discussion started by: FredSmith
5 Replies

7. Solaris

How to read EMC disk space

Hi I am using Solaris8.I want to find the total disk space of my server.Can anyone please tell that which field in below mentioned code signifies the disk space and whether this space is in Mb or GB. c11t0d52 <EMC-SYMMETRIX-5264 cyl 4 alt 2 hd 15 sec 64> ... (4 Replies)
Discussion started by: sharmaankur85
4 Replies

8. Solaris

Installing Solaris OS on LDOM SAN Disk

I have viewed a few previous posts regarding this, but none of them quite described or worked with my issue. I am out of local disk space on my LDOM Manager but still have plenty of SAN vCPU and Memory available so I am trying to install a new LDOM OS on SAN. I have exposed the SAN to the... (0 Replies)
Discussion started by: MobileGSP
0 Replies
reboot(1M)																reboot(1M)

NAME
reboot - restart the operating system SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments] The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. -l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot. -n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync filesystems. -q Quick. Reboot quickly and ungracefully, without shutting down running processes first. The following operands are supported: boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot argument list. Example 1: Passing the -r and -v Arguments to boot In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M). example# reboot -dl -- -rv Example 2: Rebooting Using a Specific Disk and Kernel The following example reboots using a specific disk and kernel. example# reboot disk1 kernel.test/unix /var/adm/wtmpx login accounting file See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2), reboot(3C), attributes(5) The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of system services, use shutdown(1M) or init(1M) to reboot a Solaris system. 11 Apr 2005 reboot(1M)
All times are GMT -4. The time now is 12:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy