I think that you confuse partition and slice. Partition is for DOS system where we have primary and extended partition and so on.
Now when you destroy your zpool you have that kind of partition but you must to divide it to slices.
You can see the current slice structure by using
I'm not sure suffix s2, so test it with or without.
To create new slices you must use subcommand partition from format.
Procedure is as follows:
1. execute format
2. select your disk c8d1
3. select partition or abbreviation p
4. select print or p to see how is now disk divided
5. select 0 and change parameters of slice 0
- name
- mode
- start sector
- length
5.a. Repeat this steps with next slices.
6. after you create all new slices select label or l to write new label to disk.
7.after all nescessary confirmation exit from format with double q.
Now you should have some slices on your disk.
Use prtvtoc to see the difference between previous and current state.
You can use that slices to create zpools.
For example:
Last edited by GP81; 06-08-2013 at 04:33 AM..
Reason: icode tags
Hello!
I recently inherited system administration duties for a SUN v880 box. The system has 6 physical hard disks.. In doing some basic maintenance, I found they're configured for mirroring. I ran the metastat and metadb commands, and many of the mirrors are showing they are in need of... (5 Replies)
Hi, I have a AIX 4.3 box here with problems cause of a disk in below VG.
volume group: workvg
lspv
hdisk4 000166789869ab2d workvg
hdisk5 000166789869b96b workvg
now hdisk4 disk has failed and cause the quorum was set, workvg became varied off.
I have to replace the... (2 Replies)
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)
hi guys,
I've got a strange issue, may be one of you has experienced this.
SunOS 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Fire-V440
everything is mirrored.
My issue is that I have a umpty directory but seems to have data on. Let me show you
# df -h /data
Filesystem size used... (10 Replies)
We have a filesystem which contains 8 hard disks but i am facing disk I/O issue becuase data is not spreading across all the disks.Is there any way i can check how data is spreading and any parameter we need to change to spread ata across all disks.
OS--AIX 5.3 (3 Replies)
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Hi all,
I guess most of you have seen this error message while installing Solaris 10 on an x86 platform. I got the error message while installing from DVD ISO on my home VMWare ESXi server.
It took me a long time to figure the exact issue and a subsequent solution. the solution is very... (1 Reply)
I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below:
root@moneta # df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 9.8G 513M 9.3G 6% /
... (0 Replies)
I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below:
root@moneta # df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Hello all,
Our Solaris 9? Sun Fire 480R backup server(in another city) is throwing disk errors such as these repeatedly.
WARNING: vxvm:vxio: Subdisk rootdisk-02 block 24037056: Uncorrectable read error
WARNING: vxvm:vxio: Subdisk rootdisk-02 block 7767072: Uncorrectable write error
... (18 Replies)
Discussion started by: RyanV
18 Replies
LEARN ABOUT MOJAVE
fmthard
fmthard(1M)fmthard(1M)NAME
fmthard - populate label on hard disks
SYNOPSIS
SPARC
fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2
fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2
The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk
partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To
print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new
label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard.
If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do
not confuse the partitions created by fmthard with the partitions created by fdisk.
The following options are supported:
-d data The data argument of this option is a string representing the information for a particular partition in the current
VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID
TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition,
and size is the number of sectors in the partition. See the description of the datafile below for more information
on these fields.
-i This option allows the command to create the desired VTOC table, but prints the information to standard output
instead of modifying the VTOC on the disk.
-n volume_name This option is used to give the disk a volume_name up to 8 characters long.
-s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-",
fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par-
tition timestamp fields to be set to zero.
Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If
the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto-
matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk.
The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited
by a new-line character (
). If the first character of a line is an asterisk (*), the line is treated as a com-
ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol-
lowing format:
partition tag flag starting_sector size_in_sectors
where the entries have the following values:
partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even
though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to
allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices.
tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1
(V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME).
flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT
0x01, and V_RONLY 0x10. For mountable partitions use 0x00.
starting_sector The sector number (decimal) on which the partition starts.
size_in_sectors The number (decimal) of sectors occupied by the partition.
You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the
-s option.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
uname(1), format(1M), prtvtoc(1M), attributes(5)
Only
fdisk(1M), installgrub(1M)
Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible.
As a precaution, save the old VTOC.
For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose.
11 Apr 2005 fmthard(1M)