Thanks for wonderful explanation. Here is my current setup.
There are 6 x 1TB disks. I installed Solaris 11.4 on the first entire disk and then mirrored it in rpool with the second disk. That gives me 4 disks of 1 TB each.
When I login to OVM Manager, select "create repository", select this server, select "physical disks", it gives me 4 disks in below format to select from. Here I can choose any disk and create a repository
Hi all,
I would like to know how to make new partitions....
I currently have allocated 60G for various slices (I have totally used 4 out of 7 available slices...
I am running only solaris on my box.
My plan is to have entire disk dedicated to solaris and run other OS from within... (19 Replies)
I have to do this exercise:
Create a virtual disk
Partition this disk
Create File system
Mount File System
I'm using Minix (which runs by Qemu as guest machine) on Linux (Host)
Is there anybody who knows how to solve first three point? :confused:
Thanks (4 Replies)
Hi All,
does any body know how to create Virtual NIC in Solaris 10
if any one have good article or reference
kindly provide me
i try to Google
but i didn't find good one (7 Replies)
Hi,
I have installed oracle 10g release 2 on solaris 10 Zone. I want to configure ASM in local Zone using virtual disks in place of real disks.
I have configured ASM using virtual disks in place real disk in Solaris 10 Global zone. How i can do in local Zone
Kindly guid me with proper... (1 Reply)
Hi, my root pool is as follows. How can I create a metadb if I want to create SVM volumes?
zpool status
pool: rpool1
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
rpool1 ONLINE 0 0 0
c4t1d0s0 ... (10 Replies)
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)
Hi,
Quick question.
I have a data zpool that consists of 1 disk.
pool: data
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
c0t50002AC0014B06BEd0 ONLINE... (2 Replies)
have been trying to create a 2 GB ramdisk (virtual) to run on my T-2000 simulator (Legion) which has sun4v architecture. I have a SPARC workstation which runs on sun4u architecture with Solaris 10.
I have created a ramdisk image using dd command, newfs, then used ufsrestore to restore the... (3 Replies)
issue,
I had a zpool which was full
pool_temp1 199G 197G 1.56G 99% ONLINE -
pool_temp2 199G 196G 3.09G 98% ONLINE -
as you can see, full
so I replaced with a larger disk.
zpool replace pool_temp1 c3t600144F0FF8BA036000058CC1DB80008d0s0... (2 Replies)
Discussion started by: rrodgers
2 Replies
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)