Sponsored Content
Full Discussion: Solaris x86 extend disk
Operating Systems Solaris Solaris x86 extend disk Post 302808863 by jlliagre on Friday 17th of May 2013 04:13:01 PM
Old 05-17-2013
You need to extend the primary fdisk partition first.
 

10 More Discussions You Might Find Interesting

1. Solaris

Disk devices in solaris 10 x86

I'm trying to mirror 2 eide disks on a solaris 10 x86 system. Im trying to use the prtvtoc | fmthard command to mirror the vtoc. How do they represent the entire disk like in solaris 9 (c0t0d0s2 = entire device) 0. c0d0 <DEFAULT cyl 26497 alt 2 hd 16 sec 63> ... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

2. HP-UX

how to extend a vg on the same disk

on the disk array (EMC Clariion cx300): we added 3 disk and extended the LUN corresponding to HP-9000 (rp7410) on HP-UX 11.11: diskinfo /dev/rdsk/c10t0d0, show more disk space, but vgdisplay vg13 does not show more space So the problem is the disk had increased, but vgdisplay does not... (6 Replies)
Discussion started by: pedro_lezaeta
6 Replies

3. Solaris

Disk Mirroring for Solaris 10 x86

I am having an issue with setting up disk mirroring for Solaris 10 on an x86 server. My main problem is that the volumes and slices have already been setup and our proprietary software has already been installed and configured. The entire drive has been allocated in this configuration and the... (2 Replies)
Discussion started by: chuck43
2 Replies

4. Solaris

Installation of Solaris 10 on X86 Platform on the same Disk having XP SP2

Plz help me in installing solaris 10 11/06 on XP sp2 system having only one hard disk (1 Reply)
Discussion started by: skargarika
1 Replies

5. Solaris

How to utilize the 2nd hard disk space in x86 solaris 5.10

I have 2 hard disks ,one hard disk(40gb) completely for windows Os,and the other(120gb) for solaris Os. In the second hard disk.I have utilised around 10gb for the solaris installation and also partitioned with the available 10gb space for the solaris x86 OS. Now i need to utilise the... (8 Replies)
Discussion started by: jayaprakash
8 Replies

6. Solaris

Moving disk partition from Solaris sparc to x86

Hello Gurus, Im trying to migrate some SAN disks from sparc server to X86 one, and having issues with disks not getting mounted on the X86 server with " not this fstyp error" due to the different partitions lay out between the two OS. I have tried it from sparc to sparc server and it worked,... (10 Replies)
Discussion started by: aladdin
10 Replies

7. Solaris

Create a boot disk mirror on Solaris 10 x86

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

Solaris 11 x86 installation troubles - 8G disk limit

Hi, I am trying to install Solaris 11 on an X86 machine. I am using the text install iso image burned to an optical disk. The system contains a single 500G SATA drive. When the system attempts to detect local disks, it reports that the disk only has a capacity of 8GB. How do I get... (2 Replies)
Discussion started by: jpoc
2 Replies

9. Red Hat

How to extend disk space?

Hi All, I am working with a virtual machine of redhat and hard-disk is 100g in all, and the system free size is about 60g. while the problem is when i run command: df -h, the root path seems already full. So i am wondering, is there any command i can work with to extend space for mounted... (2 Replies)
Discussion started by: ivyyoung
2 Replies

10. Solaris

Solaris 9 x86 check disk mirror status

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
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)
All times are GMT -4. The time now is 05:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy