Sponsored Content
Operating Systems Solaris Install boot required in SVM ?? Post 302408091 by jlliagre on Sunday 28th of March 2010 03:07:18 AM
Old 03-28-2010
Okay, interesting. So after all, the bootblk might to be part of the slice containing the filesystem and not to the label as I originally thought. In the former case, it is duplicated when mirroring is set up.
 

7 More Discussions You Might Find Interesting

1. Solaris

cant boot/install from CD

Hi all , I have an E2900 SPARC IV that has Solaris 10 installed , I am trying to replace solaris 10 with soalris 9/04 , But the installation is giving me an error: Cannot assemble drivers for root /ssm@0,0/pci@18,700000/pci@4/ide@2/cdrom@0,0:b Cannot mount root on... (3 Replies)
Discussion started by: ppass
3 Replies

2. Solaris

Help required to install packages

Hi All, I was told to install multiple packages on my solaris server. Is it possible to install multiple packages from a directory or CD. Or I need to install one by one. Please suggest. Thanks, Deepak (1 Reply)
Discussion started by: naw_deepak
1 Replies

3. Solaris

Creating A Solaris Zone - Unable to install - Are network settings required?

Hi i have created a solaris zone but have not yet connected any network cables for this new zone, can i set the zone up without running the command 'add net' and not adding an ip or physical interface? i tried to add dummy internet settings and get this zonecfg:coddr> add net... (4 Replies)
Discussion started by: newbiesolaris10
4 Replies

4. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

5. Red Hat

required resize /boot partition in linux

Hi, In my linux box I have installed /boot partition with 100MB. I have done compile for a newer kernel. The both kernels are required to me. Finally /boot partition has using 100%. I need to resize the /boot. Any body give the solution how to do resize the /boot partition without dusturbing the... (2 Replies)
Discussion started by: parsrigum
2 Replies

6. Solaris

Cannot Boot Cd TO Install Solaris 11

Recently our school acquired a number of Sun Blade 100 systems from a university that was previously using them as a computational cluster. We intend to rig them to do the same thing, but they failed to give us the head node, and all the machines we have are still configured to boot from network.... (16 Replies)
Discussion started by: Alphonse509
16 Replies

7. Programming

How to automatically install all modules required by a script from CPAN?

Having a script.pl how can I automatically download from CPAN all required modules and install and update as required? Something like "emerge -uDNav world" for the perl? ---------- Post updated at 05:38 PM ---------- Previous update was at 05:28 PM ---------- Doesn't matter I've found it ... (6 Replies)
Discussion started by: Tribe
6 Replies
vxrootmir(1M)															     vxrootmir(1M)

NAME
vxrootmir - create a mirror of a Veritas Volume Manager root disk SYNOPSIS
/etc/vx/bin/vxrootmir [-g diskgroup] [-t tasktag] [-p Pool_1,Pool_2,...] [[-v] [-b] [-R] root_mirror] DESCRIPTION
The vxrootmir command creates mirrors of all of the volumes on a Veritas Volume Manager (VxVM) rootable boot disk, and makes the new disk bootable. A disk to be used as a mirror can be specified either by its VM disk name (disk media name) or by its device name (disk access name). If a disk media name is specified, it is validated to make sure that it exists and that it has been properly initialized. This validation includes making sure that the private region is at the same location and has the same length as the private region on the primary root disk, and that the sum of the lengths of all of the subdisks located on the primary root disk will fit within the available space in the public region of the specified disk. If a disk access name is specified, it is validated to make sure it exists and is not in use, and that the total length of all the subdisks on the primary root disk will fit within the public region. The disk is then initialized to contain a private region with the same offset and length as the private region on the primary root disk. A new disk media name is assigned to the disk formed from the prefix rootdisk followed by the next available number (for example, rootdisk02, rootdisk03, and so on). All volumes that have a subdisk on the primary VxVM root disk are mirrored on the specified disk. When the root volume (rootvol) is mir- rored, the vxassist command executes vxbootsetup to set up the new disk as a boot disk. The -p option allows you to mirror the volumes on the root disk as stripe columns across several disks. The argument to this option is a list of disks that are to be used for the stripe column mirrors. If not enough disks are specified, vxrootmir prints a message to the standard error output, including information on how many disks are required, and then exits. When initialized for VxVM use, these stripe column disks are named with the prefix rootaux followed by the next available number (for example, rootaux01, rootaux02, and so on). OPTIONS
-b If the system was booted from the VxVM root disk that is being mirrored, this option uses the setboot command to set the alter- nate boot disk to the specified mirror. If the system was booted from another root disk (such as an LVM root disk), an alternate root disk is not set. If the -v option is also specified, information is displayed on the current setboot settings, and on whether the alternate boot disk is set to the specified mirror. -g diskgroup Specifies the boot disk group. -p Pool_1,Pool_2,... Specifies the disks that are to be used for stripe column targets when mirroring the VxVM root disk. The disks can be specified either as disk access names, or as disk media names if they have previously been initialized for use with VxVM. If specified as disk access names, the disks are checked for existence, correct size, and availability for use. -R Indicates that only the volumes required to boot successfully from the new mirror are to be mirrored. -t tasktag Marks any tasks that are registered to track the progress of an operation with the tag tasktag. This option is passed to vxas- sist when mirroring volumes, so any child tasks are also tagged with tasktag. -v Displays verbose output including timestamps for operations in progress. This option is useful as mirroring large volumes can take a long time. ARGUMENTS
daname Specifies the disk to be used as a mirror by its disk access name (such as c0t2d0). dmname Specifies the disk to be used as a mirror by its disk media name (such as rootdisk03). EXAMPLES
This example shows the vxrootmir command being invoked in its simpliest form: /etc/vx/bin/vxrootmir c5t1d0 The next example shows how to use the -R option with vxrootmir. # /etc/vx/bin/vxrootmir -v -b -R c5t10d0 vxrootmir: 10:10: Gathering information on the current VxVM root configuration vxrootmir: 10:10: Checking specified disk(s) for usability vxrootmir: 10:10: Preparing disk c5t10d0 as a VxVM disk vxrootmir: 10:10: Adding disk c5t10d0 to rootdg as rootdisk02 vxrootmir: 10:10: Mirroring only volumes required for root mirror boot vxrootmir: 10:10: Mirroring volume standvol vxrootmir: 10:11: Mirroring volume swapvol vxrootmir: 10:18: Mirroring volume rootvol vxrootmir: 10:20: Current setboot values: vxrootmir: 10:20: Primary: 0/4/0/1.11.0 vxrootmir: 10:20: Alternate: 0/4/0/1.13.0 vxrootmir: 10:20: Making c5t10d0 (0/4/0/1.10.0) the alternate boot disk vxrootmir: 10:20: Disk c5t10d0 is now a mirrored root disk The final example shows how to specify a list of disks for use as stripe column mirrors: # /etc/vx/bin/vxrootmir -v -p c5t11d0,c5t12d0,c5t13d0 c5t10d0 vxrootmir: 12:11: Gathering information on the current VxVM root configuration vxrootmir: 12:11: Checking specified disk(s) for usability vxrootmir: 12:11: Preparing disk c5t10d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t10d0 to rootdg as rootdisk02 vxrootmir: 12:11: Preparing disk c5t11d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t11d0 to rootdg as DM rootstpm01 vxrootmir: 12:11: Preparing disk c5t12d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t12d0 to rootdg as DM rootstpm02 vxrootmir: 12:11: Preparing disk c5t13d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t13d0 to rootdg as DM rootstpm03 vxrootmir: 12:11: Mirroring all volumes on root disk vxrootmir: 12:11: Mirroring volume standvol vxrootmir: 12:12: Mirroring volume swapvol vxrootmir: 12:19: Mirroring volume rootvol vxrootmir: 12:21: Mirroring volume optvol vxrootmir: 12:24: Mirroring volume usrvol vxrootmir: 12:27: Mirroring volume homevol vxrootmir: 12:28: Mirroring volume tmpvol vxrootmir: 12:28: Mirroring volume varvol vxrootmir: 12:36: Disk c5t10d0 is now a mirrored root disk NOTES
If the vxrootmir command aborts for any reason, or if you interrupt the command during execution, an attempt is made to clean up the VxVM objects that had been generated up to the time of the abort or interruption. All mirror plexes that had already been added, or that were in the process of being added when the interruption occurred, are removed. All Data Media (DM) objects that were created are also removed. If a plex or a DM object cannot be removed, an explanatory message is displayed. SEE ALSO
setboot(1M), vxassist(1M), vxbootsetup(1M), vxintro(1M), vxmirror(1M), vxtask(1M) VxVM 5.0.31.1 24 Mar 2008 vxrootmir(1M)
All times are GMT -4. The time now is 04:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy