06-02-2010
Hi Reboot,
thanks for the info
10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I am trying to do mirror in solaris 9. I have total 0-7 disks
4 5 6 7
0 1 2 3
Drive 0 and Drive 4 = Boot Drives
Need to Mirror following drives.
Drive 1 and Drive 5 = Need to mirror
Drive 1 was mounted on: /prod1, /prod2, /prod3, /prod4, /prod5.
Then i... (3 Replies)
Discussion started by: deal732
3 Replies
2. Solaris
Hi,
am a newbie at solaris. Need advice and help on this.
1) How do I break the mirror between 2 hard disks. (wish to keep 1 good hard disk as backup)
2) After remove 1 hard disk and put in new hard disk, how do I initialise or fomat the new hard disk?
3) How do I put back the backup... (3 Replies)
Discussion started by: chongkls77
3 Replies
3. Solaris
I have two 72GB disks that are mirrored and mounted (/backup). I have a 18GB drive in an array I just attached to the server, which is running Solaris 9.
I need to create a new logical volume partition and make the existing mirror device (/dev/md/dsk/d34) and the array's 18GB drive a member of... (3 Replies)
Discussion started by: dotcom75
3 Replies
4. Shell Programming and Scripting
Hi,
I have a question regarding finding free space on the disk of a solaris machine.
Many mount points are available in my machine. Right now i am using
df -b option to get the free disk space available.
I have an assignment to check free space on the disk.
I pass the directory as a... (3 Replies)
Discussion started by: raghu.amilineni
3 Replies
5. Solaris
Hi everyone,
Normally it always easier in Sparc machine, i can set or manually use the boot-device in NVram to boot the mirrored disk. However I have a big trouble about x86 mirror for a long time. I have been doing anything i can: search document, google, ask the others.
Recently i did as... (5 Replies)
Discussion started by: tien86
5 Replies
6. Solaris
Hello:
I have a machine built on 2 drives and mirrors have been created to a second set of 2 drives (4 total) on the same platform. SVM.
Might anyone provide guidance to create a second machine by breaking the mirrored set, moving the two mirrors (2) to another machine (same platform type),... (1 Reply)
Discussion started by: 4dailyrunner
1 Replies
7. Solaris
I’m setting up a boot disk mirror on Solaris 10 x86. I’m used to doing it on SPARC, where you can copy the partition table using fmthard. My x86 boot disk has 2 primary partitions, a Solaris one and a diagnostic one. Is there a way to copy those 2 primary partitions to the second disk without... (6 Replies)
Discussion started by: TKD
6 Replies
8. Solaris
hi friends, need help.. it is my first time patching using mirror disk backup approach, not so sure about the steps :confused: how do you detach, patch it, boot it and reattach it ? any kind soul here can advise ? thanks in advance..:)
below is the information from my machine:
Filesystem ... (3 Replies)
Discussion started by: Exposure
3 Replies
9. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
10. Solaris
We have Proliant DL380 G2 running Solaris 9 x86
There are 6 physical disks installed which I believe are mirrored at hardware level to 3 sets to present 3 disks to the OS.
Is there any way to check the mirror status at OS level ?
I am guessing not and it may need a trip to site as we have no... (4 Replies)
Discussion started by: frustrated1
4 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)