Sponsored Content
Operating Systems Solaris Unable to add disk to VG group. Post 302538735 by jpkumar10 on Thursday 14th of July 2011 04:45:51 AM
Old 07-14-2011
saurabh84g thanks for the reply. I am able to see the disk on vxdisk list.
But the thing is When I am trying to initialize the disk using /etc/vx/bin/vxdisksetup -i emcpower65s2 I am
I am getting error. following error.
bash-3.00# vxdisksetup -i emcpower65s2
VxVM vxdisksetup ERROR V-5-2-2206 emcpower65s2: An invalid device address was specified; it must be of
the form cCtTdD, mcCtTdD or <enclosurename>_<diskno> where

C = host bus adapter controller number
T = target device controller number, if used
D = logical unit (disk) number within target device controller

<enclosurename> is the logical name of the enclosure to which the
disk belongs
<diskno> is the logical number of the disk
bash-3.00#

Please let me know if I am doing it the right way. I think I am missing the correct disk ip. Please help in finding the correct disk id.

 

9 More Discussions You Might Find Interesting

1. AIX

Unable to create a group

Hi, I'm trying to create a new group on an AIX 5.2.0.0. server but am getting the following error: root:/root $ mkgroup debt 3004-698 Error committing changes to "debt" : Value is invalid. I've change the group name to no affect. Does anyone have any ideas what could be causing this? ... (0 Replies)
Discussion started by: m223464
0 Replies

2. Solaris

( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by #vxdg -g testdg -k rmdisk testdg02 But i got error when i -k adddisk bash-2.03# vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies

3. Shell Programming and Scripting

Merge group numbers and add a column containing group names

I have a file in the following format. Groups of data merge together and the group number is indicated above each group. 1 adrf dfgr dfg 2 dfgr dfgr 3 dfef dfr fd 4 fgrt fgr fgg 5 fgrt fgr (3 Replies)
Discussion started by: Lucky Ali
3 Replies

4. Shell Programming and Scripting

Merge group numbers and add a column containing group names

Hi All I do have a file like this with 6 columns. Groups of data merge together and the group number is indicated above each group. 1 1 12 26 289 3.2e-027 GCGTATGGCGGC 2 12 26 215 6.7e+006 TTCCACCTTTTG 3 9 26 175 ... (1 Reply)
Discussion started by: Lucky Ali
1 Replies

5. UNIX for Dummies Questions & Answers

Unable to deactivate a Volume Group

We want to deactivate a VG but failed, because one of the LVs created there is busy. When we are trying to unmount the LV, it is telling "not mounted" and if I execute mount command it will be informing us "already mounted". dmsetup info is indicating "Open Count = 1". Please help me, how we... (5 Replies)
Discussion started by: atanubanerji
5 Replies

6. Solaris

Unable to add new group in Solaris

I have installed Solaris 10 in VMware. Whenever I am trying to add new group using the command '/usr/sbin/groupadd/oinstall' while logged in as root , it is showing as '/usr/sbin/groupadd/oinstall can not execute'. It will be great to hear any inputs/advice here. (4 Replies)
Discussion started by: sandip250382
4 Replies

7. AIX

Unable to extend volume group(VG)

Would some help me on this below I am trying to extend file system on AIX and however unable to extend the file system. 0516-306 extendvg: Unable to find physical volume 20 in the Device Configuration Database. 0516-321 extendvg: Physical volume u01-lv is not configured. 0516-792... (15 Replies)
Discussion started by: murali969
15 Replies

8. HP-UX

Removing a VxVM disk from a Disk Group

Hello all, So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'` do rmsf -H $i done I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies

9. HP-UX

Unable to add 300gb secondary disk to running 11.11 HPUX system

This has got to be the system from hell. Once again, on the RP4440 (after the supplier replaced the entire box due to the bad RTC battery), finally have it all reloaded with the packages the developers need. The last thing is to add the secondary disk to the OS. BCH sees both OS and secondary... (2 Replies)
Discussion started by: mrmurdock
2 Replies
vxdisksetup(1M) 														   vxdisksetup(1M)

NAME
vxdisksetup, vxdiskunsetup - configure a disk for use with Veritas Volume Manager SYNOPSIS
vxdisksetup [-ifB] disk_address [attribute ...] vxdisksetup [-ifB] disk_address format=hpdisk [attribute ...] vxdisksetup [-if] disk_address format=cdsdisk [attribute ...] /etc/vx/bin/vxdiskunsetup [-C] [-F] disk_address... DESCRIPTION
The vxdisksetup command configures the disk for use by Veritas Volume Manager (VxVM). vxdisksetup is called by the vxdiskadd command as part of initial disk configuration. It is not typically necessary to call this command directly. Note: In release 4.0 of VxVM, the behavior of the vxdisksetup command has been changed so that it only creates auto-configured disks (with a disk access type of auto; see vxdisk(1M)), which can have one of the following formats: cdsdisk The disk is formatted as a CDS disk that is suitable for moving between different operating systems. This is the default format for non-EFI disks (provided that the -i option is used to write the disk header). It is not suitable for boot disks or EFI disks. Note: As the CDS format is applied to the entire disk and is unsuitable for boot disks, options and attributes that relate to partitions, slices or booting are not applicable. The CDS format is also incompatible with EFI disks. hpdisk The disk is formatted to include a private region that VxVM uses to store configuration information. Following the private region, the remainder of the disk forms the public region from which subdisks can be allocated. This format can be applied to disks that can be used to boot the system. If the disk is not initialized as a boot disk, space is reserved on the disk to allow it to be converted to cdsdisk format if required. The hpdisk format is the default for EFI disks. none The disk is unformatted. Note: This value may be displayed, but it cannot be set as a valid format. The vxdiskunsetup command reverses the configuration done by vxdisksetup and makes the specified disks unusable by VxVM. vxdiskunsetup can be applied only to VxVM-initialized disks that are not in use within an imported disk group. The disk_address argument passed to vxdisksetup or to vxdiskunsetup directs the command to the device that corresponds to the disk being operated upon. The address should be provided in the form c#t#d#, which define a controller number (c#), a SCSI target ID (t#), and a SCSI logical unit number (d#). Each number is specified in decimal and can be multiple digits. If the disks are named using the enclosure based naming scheme, the address usually takes the form enclosurename_diskno. The name must reference a valid disk under the /dev/vx/rdmp directory. The vxdiskunsetup command operates by removing the public and private regions that were created by the last invocation of vxdisksetup on the specified disks. After this operation, those disks are converted from the online to the error state state (as displayed by vxdisk list). The /etc/default/vxdisk file can be used to set the default values of the format and privlen attributes for the vxdisk and vxdisksetup com- mands. Values in this file override inbuilt values, and may themselves be overridden by values specified on the command line. For details, see the vxdisk(1M) manual page. Note: When vxdisksetup is executed on an HP IPF (IA64) system, the target disk is either configured or deconfigured as an EFI partitioned disk. The action that is taken depends on whether the -B option is specified, and whether the disk is already formatted as an EFI parti- tioned disk: o If the -B option is specified, and the disk is not already formatted as an EFI disk, the idisk(1M) utility is called to format the disk as an EFI partitioned disk. The partitioning creates an EFI header in the first 1K block, a 100MB partition (or slice) 1, and partition 2 (the HP-UX partition) on the remainder of the disk. If the vxbootsetup(1M) command is subsequently used to configure the disk as a boot disk, partition 1 is populated with an EFI file system, which contains the boot programs that are needed by an HP IPF system, and the HP-UX partition (partition 2) is set up as a logical simple VxVM disk with the same layout as a non-EFI disk. When vxdisksetup has completed setting up an EFI disk, the resulting disk must be addressed using the s2 suffix to select the logical sim- ple VxVM disk. o If the -B option is not specified and the target disk is currently formatted as an EFI partitioned disk, any EFI formatting is destroyed, and the disk is initialized as a non-EFI partitioned disk. OPTIONS
-B Initializes the Veritas Volume Manager private region to begin at block number 2144. This block is designated as the private region offset for a Veritas Volume Manager root disk. Without this option, the private region is initialized to start at the default block number 128. Note: This option is not supported for cdsdisk format disks. -C vxdiskunsetup usually does not operate on disks that appear to be imported by some other host (for example, a host that shares access to the disk). In this case, the -C option can be specified to force de-configuration of the disk, effectively removing the host locks that were detected by vxdiskunsetup. -f Forces a disk to be initialized even if it is a member of a deported disk group. -F By default, the vxdiskunsetup command only operates on online disks. It does not operate on disks that are imported or offline. This option forces an unsetup operation to be performed on such disks. -i Writes a disk header to the disk, initializes the private region of the disk and makes the disk directly usable (as a new disk in a disk group, for example). Note: A disk that is a member of an imported disk group cannot be initialized. The command also fails if the disk is a member of a deported disk group. The -f option can be used to override the latter restriction. ATTRIBUTES
You can specify attributes to affect the layout strategy used by vxdisksetup. CAUTION: Take great care when using these attributes as they can render a disk unusable by VxVM. config Sets up kernel logs or configuration databases on the disk. This attribute has the opposite effect to the noconfig attribute. This is the default behavior if the -i option is specified. Otherwise, the attribute is ignored. noconfig Prevents setting up kernel logs or configuration databases on the disk. The size of the default private region is set to 160 blocks, which is the minimum allowed private region size. noconfig is ignored unless the -i option is specified. noreserve Do not reserve space for conversion to other formats such as cdsdisk. privlen=length Specifies the length of the private region of the disk. The default size of this area is 32MB. The maximum possible size of the private region is 524288 blocks. For cdsdisk format disks, privlen is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. privoffset=offset Indicates the sector offset of the private region on the disk. The default value for the private region offset is block number 128 for non-boot disks and block number 2144 for boot disks. For cdsdisk format disks, privoffset is silently rounded up to the nearest multiple of 8KB that is larger than or equal to 128KB if it is not already a multiple of 8KB or if its value is less than 128KB. publen=length Specifies the length of the public region of the disk. This defaults to the size of the disk minus the private area on the disk. For cdsdisk format disks, publen is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. puboffset=offset Sets the offset on the disk where the public region starts. By default, this is past the end of the private region. For the hpdisk format, 128 blocks of disk space are reserved at the end of the private region unless this is overridden by the value of puboffset or the -B option is specified. The reserved space allows for later conversion to the cdsdisk format. For cdsdisk format disks, puboffset is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. EXAMPLES
To initialize a disk for regular use, enter: /etc/vx/bin/vxdisksetup -i c2t1d0 To initialize a disk for normal use, but set the private region size to 1MB instead of the default size of 32MB, enter: /etc/vx/bin/vxdisksetup -i c2t1d0 privlen=1m Force deconfiguration of a VxVM-initialized disk, c0f4d0: /etc/vx/bin/vxdiskunsetup -C c0t4d0 NOTES
The default private region size increased from 512KB to 1MB in release 3.2, and from 1MB to 32MB in release 5.0. FILES
/etc/default/vxdisk Defaults file used by the vxdisk and vxdisksetup utilities. SEE ALSO
vxcdsconvert(1M), vxdisk(1M), vxdiskadd(1M), vxintro(1M) VxVM 5.0.31.1 24 Mar 2008 vxdisksetup(1M)
All times are GMT -4. The time now is 02:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy