how to create multiple-boot system with disks mirrored(RAID1+0) and disk alone

10 More Discussions You Might Find Interesting

1. Red Hat

Booting 2nd mirrored boot disk

Hi guys, thanks for helping out. If you have two boot disk mirrored and your primary boot disk fails, how will you boot the system from the second disk? Thank you very much for your assistance on this matter. Arrey

2. Solaris

Need help replacing a mirrored boot disk

I have a v480 with a mirrored boot disk c1t0 and c1t1. The drives themselves don't show a failure but the mirror's need maintenance. This is my plan for replacing the drive. I would love feedback to point out what I"m missing or where my steps are incorrect. Two things I believe I'm...

3. Solaris

Boot from Mirrored disk

So I have mirrored disk already set up from c1t0d0 to c1t1d0. Is there some special procedures that I need to do before I do and then try to boot from the mirrored disk? I am using a V490 if that helps...

4. Solaris

Are my disks mirrored ?

# metastat d1: Mirror Submirror 0: d11 State: Okay Submirror 1: d12 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 14582208 blocks (7.0 GB) d11: Submirror of d1 State: Okay Size: 14582208 blocks...

5. HP-UX

To identify if local disks are mirrored

Hello All, Am trynig to identify if the local HD's on our BL860 (running 11v3) are indeed mirrored to each other. Cheers, Cameron

6. Solaris

Backup for HW Mirrored Disks

We use SW mirroring (RAID1) using SVM for our SUN servers (which we OEM to end clients with our application on). When I need to make a tape backup for the server (disk), I disable mirroring and perform backup of the entire disk to tape using ufsdump. This process requires an outage and sensitive as...

7. Solaris

Migrate VxVM boot disks to higher capacity disk

Hi, Im getting a downtime of 4 hrs to do porting of bootdisks. Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage. We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl....

8. Solaris

Creating an image of a mirrored disks

Hi guys, I havent done this before but iam trying to create an image of a mirrorred drive. Correct me if iam wrong, but when i have two disks setup in raid configuration and have them mirrored in solaris. It then defines at one entity. How would i create a "flar" image of that one entity...

9. UNIX for Dummies Questions & Answers

Creating create mirrored disk files systems using mkfs command

What is the correct mkfs syntax to create mirrored disk files systems? I need to make the file system 20gb. For example: machine# mkfs -F ufs /dev/md/dsk/d40 size not specified ufs usage: mkfs special size(sectors) \ -m : dump fs cmd line used to make this partition -V : print this...

10. AIX

checking to see if logical disks are mirrored.

I have AIX 5.1 I ran these commands and was not able to see what disk were mirrored to what. I thought this is what I should do? lslv -m rd |more lslv -m db |more I get a error stating that it can't find or in the device configuation databse. Is there another way to look? I have a physcal...

LEARN ABOUT HPUX

bootconf

bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME

       bootconf - boot device configuration table

DESCRIPTION

       The file contains the address and disk layout type of the system's boot devices or lif volumes.	It is used by the and HP-UX kernel control
       scripts (fileset to determine how and where to update the initial boot loader.  Normally the kernel's script queries the system's  hardware
       and creates the file.  In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
       boot devices should be automatically updated, the administrator must edit the file manually.

       There is one line in the file for each boot device.  Each line contains the following blank-separated fields in the order shown:

       disk type   A flag indicating how the file system(s) on the disk are laid out.  The flag must be one of the following:

		   Indicates that the root disk is in LVM or VERITAS Volume Manager
			  (VxVM) format.  If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.

		   Indicates that the root disk is in the
			  "whole disk" format with no partitions, but boot and swap space are reserved outside the file system.

       device file The absolute path of the device special file that accesses the physical device where the boot area is located.   For  LVM  root
		   disks,  the	device	special file is the physical volume(s) returned by the command.  For "whole disks" this is the device file
		   that references the entire disk.

       Blank lines are permitted.  Any line beginning with a is considered to be a comment.

DIAGNOSTICS

       The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect.  Most of the messages are  self-
       explanatory; a few warrant additional explanation:

       If there are no other messages about
	      the  file  is probably empty.  Otherwise, the file is not in the proper format, and the other messages will explain what the problem
	      is.

       The specified device file does not point to a disk where there is a
	      lif which contains the file

       Some character other than
	      or is in the first field of a line.

       As of release 10.0, the boot areas in
	      must all be on the same type of disk layout.

       There are characters after the
	      device file specification.

EXAMPLES

       The boot area is on an LVM root disk:

	      l /dev/disk/disk7_p2

       The boot area is on a whole disk layout:

	      w /dev/disk/disk7

WARNINGS

       All of the boot devices in the file must have the same disk layout.

AUTHOR

       was developed by the Hewlett-Packard Company.

FILES

SEE ALSO

       mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).

       documentation.

																       bootconf(4)

UNIX for Advanced & Expert Users