Forum Discussion

msleite's avatar
msleite
Level 3
10 years ago

failed to create a Veritas dg

Hi,

I'm creating a DG with 6 LUNs. The LUNs have 1 TB each. The disks are as below:
When you configure a disk error message appears:

emc_clariion0_264 auto            -            -            nolabel
emc_clariion0_265 auto            -            -            nolabel
emc_clariion0_266 auto            -            -            nolabel
emc_clariion0_267 auto            -            -            nolabel
emc_clariion0_268 auto            -            -            nolabel
emc_clariion0_269 auto            -            -            nolabel

root@ # vxdisksetup -i emc_clariion0_264 format=cdsdisk

c5t500601663EE00243d228s2
VxVM vxdisksetup ERROR V-5-2-5241 Cannot label as disk geometry cannot be obtained.
root@ #

root@ # vxdisksetup -i emc_clariion0_265 format=cdsdisk
c5t5006016F3EE00243d241s2
VxVM vxdisksetup ERROR V-5-2-5241 Cannot label as disk geometry cannot be obtained.
root@ #

...
...

root@ # vxdisk list emc_clariion0_264
Device:    emc_clariion0_264
devicetag: emc_clariion0_264
type:      auto
flags:     nolabel private autoconfig
pubpaths:  block=/dev/vx/dmp/emc_clariion0_264 char=/dev/vx/rdmp/emc_clariion0_264
guid:      -
udid:      DGC%5FVRAID%5FCKM00123600618%5F6006016025303100932DF87904C4E411
site:      -
errno:     Device path not valid
Multipathing information:
numpaths:   8
c7t5006016E3EE00243d228s2       state=enabled   type=secondary
c7t500601673EE00243d228s2       state=enabled   type=primary
c5t5006016F3EE00243d228s2       state=enabled   type=secondary
c5t500601663EE00243d228s2       state=enabled   type=primary
c6t500601663EE00243d228s2       state=enabled   type=primary
c6t5006016F3EE00243d228s2       state=enabled   type=secondary
c8t5006016E3EE00243d228s2       state=enabled   type=secondary
c8t500601673EE00243d228s2       state=enabled   type=primary
root@BMG01 #

Can someone help me solve the problem?
 
Thanks.
 
Marconi
business continuity
Configuring
Solaris
Storage Foundation
  • Marianne's avatar
    Marianne
    10 years ago

    If disk is bigger that 1TB,  use 'format -e' with the /dev/vx/rdmp name to set the size of partition 0 to 0tb and partition 2 to entire disk, then label the disk.

  • msleite's avatar
    msleite
    10 years ago
    OK Marianne,
     
    did the formatting as EFI and the problem was solved, see:
     

    EFI FORMAT

    root@ # vxdisk -e list emc_clariion0_265
    DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
    emc_clariion0_265 auto           -            -           nolabel              c5t5006016F3EE00243d241s2 lun RAID_6
    root@ #
    root@ # format -e c5t5006016F3EE00243d241s2
    selecting c5t5006016F3EE00243d241s2
    [disk formatted]


    FORMAT MENU:
            disk       - select a disk
            type       - select (define) a disk type
            partition  - select (define) a partition table
            current    - describe the current disk
            format     - format and analyze the disk
            repair     - repair a defective sector
            label      - write label to the disk
            analyze    - surface analysis
            defect     - defect list management
            backup     - search for backup labels
            verify     - read and display labels
            save       - save new disk/partition definitions
            inquiry    - show vendor, product and revision
            scsi       - independent SCSI mode selects
            cache      - enable, disable or query SCSI disk cache
            volname    - set 8-character volume name
            !<cmd>     - execute <cmd>, then return
            quit
    format> l
    [0] SMI Label
    [1] EFI Label
    Specify Label type[0]: 1
    Warning: This disk has an SMI label. Changing to EFI label will erase all
    current partitions.
    Continue? y
    format> q
    root@ #
    root@ # vxdctl enable
    root@#
    root@# vxdisk -e list emc_clariion0_265
    DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
    emc_clariion0_265 auto:none      -            -           online invalid       c5t5006016F3EE00243d241 lun RAID_6
    root@ #
    root@ # vxdisksetup -i emc_clariion0_265 format=cdsdisk
    root@ #
    root@ # vxdisk -e list emc_clariion0_265
    DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
    emc_clariion0_265 auto:cdsdisk   -            -           online               c5t5006016F3EE00243d241 lun RAID_6
    root@ #

    Thanks to you and the others for more help.

     

     

  • Sandeepkumar's avatar
    Sandeepkumar
    Level 4
    10 years ago

    Is the disk is labeled....????

    Label the disk by using format command so that VTOC will be present on the disk and then run vxdisksetup command

  • msleite's avatar
    msleite
    Level 3
    10 years ago

    Hi Sandeepkumar,

     

    did the formatting and put the label, but when checking the disc continues without label. I wonder if the problem is in size?
     

    root@ # vxdisk list emc_clariion0_264
    Device:    emc_clariion0_264
    devicetag: emc_clariion0_264
    type:      auto
    flags:     nolabel private autoconfig
    pubpaths:  block=/dev/vx/dmp/emc_clariion0_264 char=/dev/vx/rdmp/emc_clariion0_264
    guid:      -
    udid:      DGC%5FVRAID%5FCKM00123600618%5F6006016025303100932DF87904C4E411
    site:      -
    errno:     Device path not valid
    Multipathing information:
    numpaths:   8
    c7t5006016E3EE00243d228s2       state=enabled   type=secondary
    c7t500601673EE00243d228s2       state=enabled   type=primary
    c5t5006016F3EE00243d228s2       state=enabled   type=secondary
    c5t500601663EE00243d228s2       state=enabled   type=primary
    c6t500601663EE00243d228s2       state=enabled   type=primary
    c6t5006016F3EE00243d228s2       state=enabled   type=secondary
    c8t5006016E3EE00243d228s2       state=enabled   type=secondary
    c8t500601673EE00243d228s2       state=enabled   type=primary
    root@ #
    root@ # format c7t5006016E3EE00243d228s2
    selecting c7t5006016E3EE00243d228s2
    [disk formatted]


    FORMAT MENU:
            disk       - select a disk
            type       - select (define) a disk type
            partition  - select (define) a partition table
            current    - describe the current disk
            format     - format and analyze the disk
            repair     - repair a defective sector
            label      - write label to the disk
            analyze    - surface analysis
            defect     - defect list management
            backup     - search for backup labels
            verify     - read and display labels
            save       - save new disk/partition definitions
            inquiry    - show vendor, product and revision
            volname    - set 8-character volume name
            !<cmd>     - execute <cmd>, then return
            quit
    format> l
    Ready to label disk, continue? y

    format> q
    root@ # vxdisk list | grep  emc_clariion0_264
    emc_clariion0_264 auto            -            -            nolabel
    root@ #

     

  • msleite's avatar
    msleite
    Level 3
    10 years ago

    Ok Sandeepkumar,

     

    root@ # prtvtoc c7t5006016E3EE00243d228s2
    * c7t5006016E3EE00243d228s2 partition map
    *
    * Dimensions:
    *     512 bytes/sector
    *     189 sectors/track
    *     255 tracks/cylinder
    *   48195 sectors/cylinder
    *   44558 cylinders
    *   44556 accessible cylinders
    *
    * Flags:
    *   1: unmountable
    *  10: read-only
    *
    *                          First     Sector    Last
    * Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
           0      2    00          0    289170    289169
           1      3    01     289170    289170    578339
           2      5    01          0 2147376420 2147376419
           6      4    00     578340 2146798080 2147376419
    root@#

     

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    This seems to be the problem:

    10: read-only

    Get storage team to present lun in read/write mode.

    As long as you are unable to label the disk at OS-level, forget about trying to add/use the disks in VxVM..

  • starflyfly's avatar
    starflyfly
    Level 6
    10 years ago

    The disk need first labled before used by vxvm, and it must in read-write state to do the label.

     

    You can first test if you can write sth to the disk:

     

    make sure the disk is not contain useful data, test dd:

     

    dd if=/dev/zero  of=/dev/rdsk/c3t500601603022FB3Fd11s2 bs=1024  count=1000 

  • msleite's avatar
    msleite
    Level 3
    10 years ago

    Hi Marianne and starflyfly,

    I ran the test that the starflyfly recommended and it worked, see:
     
    root@ # dd if=/dev/zero of=/dev/rdsk/c7t5006016E3EE00243d228s2 bs=1024 count=1000
    1000+0 records in
    1000+0 records out
     
    another disk that already is being used that is also read-only.

    root@ # prtvtoc /dev/rdsk/c8t500601673EE00243d224s2
    * /dev/rdsk/c8t500601673EE00243d224s2 partition map
    *
    * Dimensions:
    *     512 bytes/sector
    *      16 sectors/track
    *     256 tracks/cylinder
    *    4096 sectors/cylinder
    *   51200 cylinders
    *   51198 accessible cylinders
    *
    * Flags:
    *   1: unmountable
    *  10: read-only
    *
    *                          First     Sector    Last
    * Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
           2      5    01          0 209707008 209707007
           7     15    01          0 209707008 209707007

     

     

     

     

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    Speak to your Storage Admins. As long as you cannot label the disk(s), there is nothing that can be done from OS or VxVM.

    Ask storage admins to compare lun settings of working luns with newly added luns.

    Required LUN/Array settings are listed in SF Host and Storage Configuration Guide for Dynamic Multi-Pathing :  http://www.symantec.com/docs/TECH47728

  • TonyGriffiths's avatar
    TonyGriffiths
    Level 6
    10 years ago

    Hi

    After labelling the disk, did you rescan the device tree in Volume Manager ? (vxdisk scandisks etc)

    It looks like you are using SMI label scheme for the 1TB disks.

    Can you post the updated vxdisk list once you have rescanned

    thanks

    tony

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    If disk is bigger that 1TB,  use 'format -e' with the /dev/vx/rdmp name to set the size of partition 0 to 0tb and partition 2 to entire disk, then label the disk.