Sponsored Content
Full Discussion: Solaris 11 disk issue
Operating Systems Solaris Solaris 11 disk issue Post 302818539 by cbtshare on Friday 7th of June 2013 05:05:00 PM
Old 06-07-2013
@GP81

Yes, as I said in my previous post, I was able to create the pool again, and it is now online. I can destroy the pool again and then be able to access the disk, but still am stuck at how to partition the disk.

Yes, I used fdisk subcommand, this is the disk after I created a label:
Code:
 Total disk size is 9725 cylinders
             Cylinder size is 16065 (512 byte) blocks

                                               Cylinders
      Partition   Status    Type          Start   End   Length    %
      =========   ======    ============  =====   ===   ======   ===
          1                 EFI               0  9725    9726    100

I want to know how can I create a couple partitions.

Last edited by Scott; 06-07-2013 at 06:46 PM.. Reason: Code tags
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris 8 disk/mirroring issue

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)
Discussion started by: ghuber
5 Replies

2. AIX

disk issue

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)
Discussion started by: karthikosu
2 Replies

3. Solaris

Disk Mirror in Solaris 9 via Solaris Volume Manager

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)
Discussion started by: deal732
3 Replies

4. UNIX for Advanced & Expert Users

partition disk issue

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)
Discussion started by: moustik
10 Replies

5. AIX

Disk I/O Issue

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)
Discussion started by: ukatru
3 Replies

6. Solaris

root disk mirroring in solaris volume manager for solaris 10

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)
Discussion started by: ramareddi16
1 Replies

7. Solaris

Solaris 10 installation issue Error 25: Disk cannot be read - Solved

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)
Discussion started by: admin_xor
1 Replies

8. Solaris

Convert from raw disk to solaris volume manager disk

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)
Discussion started by: fretagi
0 Replies

9. Solaris

Convert from raw disk to solaris volume manager disk

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)
Discussion started by: fretagi
4 Replies

10. Solaris

Server disk issue need help

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
idisk(1M)																 idisk(1M)

NAME
idisk - create partitions for disks on an Integrity system SYNOPSIS
partition_description_file}] device DESCRIPTION
creates operating system partitions for disks on an Integrity system. It reads in the partition information from a data file that may be specified in the command string or redirected from stdin. By default, operates in read-only mode and displays the partition information that is currently on the disk. To write new partition infor- mation on the disk the user must specify the option. Options recognizes the following options: Print the primary EFI partition header and partition tables. Print the alternate EFI partition header and partition tables. Print the legacy partition table that resides in the master boot record. writes partition information for the first four partition in the partition table in used by legacy DOS and Win- dows. This information is used as a backup in the event all the EFI information is corrupted. Print the first usable and last usable block numbers that are available to create partitions. First usable is the first block a partition can start on. Last usable is the last block that can be contained in a partition. These numbers are relative to the whole disk and do not take into account any partitions that may exist. They represent the total disk space that can be partitioned. Use the option to only print the values without headings. Work silently. No user prompts or warnings. For use in shell scripts. Validate EFI partition information. Does the same checks the driver does verifying that both the primary and alternate EFI partition headers and tables are correct. Returns two if either is bad and zero if both are correct. Restore the EFI partition headers and tables. This option checks both the primary header and tables and the alternate header and tables. If one is found bad it is restored from the other good ver- sion. One of either the primary or alternate header and tables must be good for this option to succeed. The option must be specified for information to be written to the disk. Remove all EFI partition headers and tables from the disk. This option also destroys the information contained in the MBR (master boot record). The option must be specified for information to be written to the disk. The partition_description_file contains the number of partitions to be created and the type and requested size of each partition. The filename may be specified here or redirected from stdin when the dash is used. Enable write mode. By default operates in read-only mode. To create and write partition information to the disk you must specify the option. Partition Description File The first entry in the partition description file is the number of partitions to create. The maximum number of partitions allowed is 12. This is followed by a line containing the type and size for each of the partitions. Recognized partition types are: and At least one EFI partition is required to create a valid partition table. Size may be specified in megabytes or as a percentage of the whole disk. Internally, creates the partitions whose size is specified in MB first then creates those whose size was specified as a percentage. Those partitions specified as a percent are assigned space from what is available after the MB partitions are created. If the size of a parti- tion is specified as 100% then all space remaining is assigned to that partition. An example partition description file is shown below: The first entry specifies the number of partitions to create. The second specifies an EFI partition of 100 megabytes. The last entry specifies a HPUX partition consisting of all the remaining space on the disk after the EFI partition has been created. When creating partitions, the device file name must be that of the whole disk. Legacy device files must not have any partition number bits set in the minor number. For legacy disk devices, the last eight bits of the minor number represent the option bits. For Integrity system disks, the last four option bits are used to indicate the partition number. Since there are only four bits for parti- tion number, only one to fifteen partitions are supported. For example, a device node with a minor number of 0x008001 would indicate a disk at target eight, partition number one. A minor number of 0x00500F would indicate a disk at target 5 partition fifteen. A minor num- ber with no partition bits set would indicate the whole disk (for example, 0x008000 would be the same disk as above but represent the whole disk and not a partition). Persistent device special files do not use or contain minor number information. A detailed description on persistent device special files can be found in intro(7). Note: For partitions created by device special files must be created for each legacy hardware path to the disk and for the LUN hardware path using or (see intro(7) for details on legacy and agile modes). If legacy mode is disabled (see the descrip- tion of the option in rmsf(1M)), device special files must only be created for the LUN hardware path. Note has been ported to Windows NT 4.0 and 2000. RETURN VALUE
Exit values are: Successful completion. Error condition occurred. EXAMPLES
Create the partitions specified in the above description file, printing only the primary partition information: Create the partitions specified in the above description file, printing only the primary partition information using a persistent device special file (see intro(7)): Create the partitions specified in the above description file, printing all available information (default), redirecting input from stdin: Only read the disk, printing all tables (default) on the disk: Get the first and last usable block for partitioning on the disk: Destroy all partition information on the disk: Restore partition information from either a good primary or alternate header or table to the header or table that is bad: AUTHOR
was developed by HP. SEE ALSO
insf(1M), mksf(1M), efi(4), intro(7). Integrity Systems Only idisk(1M)
All times are GMT -4. The time now is 04:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy