Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Vxdiskadm Replace disk does not show my failed disk

Created: 08 May 2013 | 25 comments

Hello all,

 

i would like to replace my failed disk via the vxdiskadm utility

 

EMMDPD04:/# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0t0d0s2     auto:sliced     rootdisk     rootdg       online
c0t1d0s2     auto:sliced     rootmirror   rootdg       online
c0t2d0s2     auto            -            -            error
c0t3d0s2     auto:none       -            -            online invalid
emcpower0s2  auto:sliced     bgw1dgemcpower0  bgw1dg       online shared
emcpower1s2  auto:sliced     ora1dgemcpower7  ora1dg       online shared
emcpower2s2  auto:sliced     fmm1dgemcpower6  fmm1dg       online shared
emcpower3s2  auto:sliced     bgw1dgemcpower1  bgw1dg       online shared
emcpower4s2  auto:cdsdisk    -            -            online
emcpower5s2  auto:cdsdisk    -            -            online
emcpower6s2  auto:sliced     lic1dgemcpower5  lic1dg       online shared
emcpower7s2  auto:cdsdisk    -            -            online
emcpower8s2  auto:sliced     bgw1dgemcpower8  bgw1dg       online shared
emcpower9s2  auto:sliced     bgw1dgemcpower9  bgw1dg       online shared
emcpower10s2 auto:sliced     bgw1dgemcpower10  bgw1dg       online shared
emcpower11s2 auto:sliced     bgw1dgemcpower11  bgw1dg       online shared
emcpower12s2 auto:sliced     bgw1dgemcpower12  bgw1dg       online shared
emcpower13s2 auto:sliced     bgw1dgemcpower13  bgw1dg       online shared
emcpower14s2 auto:sliced     bgw1dgemcpower14  bgw1dg       online shared
emcpower15s2 auto:sliced     bgw1dgemcpower15  bgw1dg       online shared
EMMDPD04:/# 
EMMDPD04:/# 
EMMDPD04:/# 
EMMDPD04:/# vxdiskadm
 
Volume Manager Support Operations
Menu: VolumeManager/Disk
 
 1      Add or initialize one or more disks
 2      Encapsulate one or more disks
 3      Remove a disk
 4      Remove a disk for replacement
 5      Replace a failed or removed disk
 6      Mirror volumes on a disk
 7      Move volumes from a disk
 8      Enable access to (import) a disk group
 9      Remove access to (deport) a disk group
 10     Enable (online) a disk device
 11     Disable (offline) a disk device
 12     Mark a disk as a spare for a disk group
 13     Turn off the spare flag on a disk
 14     Unrelocate subdisks back to a disk
 15     Exclude a disk from hot-relocation use
 16     Make a disk available for hot-relocation use
 17     Prevent multipathing/Suppress devices from VxVM's view
 18     Allow multipathing/Unsuppress devices from VxVM's view
 19     List currently suppressed/non-multipathed devices
 20     Change the disk naming scheme
 21     Get the newly connected/zoned disks in VxVM view
 22     Change/Display the default disk layouts
 23     Mark a disk as allocator-reserved for a disk group
 24     Turn off the allocator-reserved flag on a disk
 list   List disk information
 
 
 ?      Display help about menu
 ??     Display help about the menuing system
 q      Exit from menus
 
Select an operation to perform: 4
 
Remove a disk for replacement
Menu: VolumeManager/Disk/RemoveForReplace
  Use this menu operation to remove a physical disk from a disk
  group, while retaining the disk name.  This changes the state
  for the disk name to a "removed" disk.  If there are any
  initialized disks that are not part of a disk group, you will be
  given the option of using one of these disks as a replacement.
 
Enter disk name [<disk>,list,q,?] list
 
Disk group: rootdg
 
DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE
 
dm rootdisk     c0t0d0s2     auto     80321    583834230 -
dm rootmirror   c0t1d0s2     auto     80321    583850295 -
 
Disk group: bgw1dg
 
DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE
 
dm bgw1dgemcpower0 emcpower0s2 auto   96130    1312574752 -
dm bgw1dgemcpower1 emcpower3s2 auto   96130    1310486288 -
dm bgw1dgemcpower8 emcpower8s2 auto   96130    1576844000 -
dm bgw1dgemcpower9 emcpower9s2 auto   96130    1576844000 -
dm bgw1dgemcpower10 emcpower10s2 auto 96130    1576844000 -
dm bgw1dgemcpower11 emcpower11s2 auto 96130    1576844000 -
dm bgw1dgemcpower12 emcpower12s2 auto 96130    1314695328 -
dm bgw1dgemcpower13 emcpower13s2 auto 96130    1293746560 -
dm bgw1dgemcpower14 emcpower14s2 auto 96130    1576844000 -
dm bgw1dgemcpower15 emcpower15s2 auto 96130    1576844000 -
 
Disk group: fmm1dg
 
DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE
 
dm fmm1dgemcpower6 emcpower2s2 auto   80065    104711648 -
 
Disk group: lic1dg
 
DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE
 
dm lic1dgemcpower5 emcpower6s2 auto   67324    2019328  -
 
Disk group: ora1dg
 
DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE
 
dm ora1dgemcpower7 emcpower1s2 auto   80065    419280416 -
 
Enter disk name [<disk>,list,q,?] c0t2d0s2                
  VxVM  ERROR V-5-2-400
There is no disk named c0t2d0s2 in any disk group configuration.
  To get a list of disks enter "list".
 
Enter disk name [<disk>,list,q,?] q
 
 
Is this the proper way or is there any other way to replace my spare disk?
 
 
Discussion Filed Under:

Comments 25 CommentsJump to latest comment

starflyfly's picture

Hi,

 

  In vxvm admin guide document, there is a chapter for replace  disks, Except upper operation, you need run some os commands to clean device tree.

 

You can access sort.symantec.com  to check document.

https://sort.symantec.com/documents

Regards

 

If the answer has helped you, please mark as Solution.

chuckchang23's picture

Hi starflyfly,

 

when i use the vxdiskadm command, is says it needs a diskgroup the problem is that the spare disk has no diskgroup

stinsong's picture

Hi Chunckchang23,

Did you try menu option 5 VolumeManager/Disk/ReplaceDisk? It is used for your condition. smiley

 

Menu: VolumeManager/Disk/ReplaceDisk
  Use this menu operation to specify a replacement disk for a disk
  that you removed with the "Remove a disk for replacement" menu
  operation, or that failed during use.  You will be prompted for
  a disk name to replace and a disk device to use as a replacement.
  You can choose an uninitialized disk, in which case the disk will
  be initialized, or you can choose a disk that you have already
  initialized using the Add or initialize a disk menu operation.
 
chuckchang23's picture

 

Hi Starflyfly
 
I cannot proceed with this step due to the error can't be detected.
 
Pls see output of vxdiskadm
 
Replace a failed or removed disk
Menu: VolumeManager/Disk/ReplaceDisk
  Use this menu operation to specify a replacement disk for a disk
  that you removed with the "Remove a disk for replacement" menu
  operation, or that failed during use.  You will be prompted for
  a disk name to replace and a disk device to use as a replacement.
  You can choose an uninitialized disk, in which case the disk will
  be initialized, or you can choose a disk that you have already
  initialized using the Add or initialize a disk menu operation.
  VxVM  INFO V-5-2-396
There are currently no devices that are failed or removed.
Hit RETURN to continue.
kjbss's picture

Make sure your OS can see the c0t2d0s2 disk BEFORE you try any volume manager actions.

Does 'prtvtoc /dev/rdsk/c0t2d0s2' show you the contents of the label, or an error?

If an error is shown, you need to fix your OS to be able to see your disk; try 'devfsadm -Ccv disk', then try the prtvtoc command again, and depending on if that work or not, you might try to format the disk, then make sure you can prtvtoc it. 

If that doesn't work, you may need to physically replace the drive (or is that what you have already done)?

You sould also keep on eye on the OS console log (/var/adm/messages) and address any errors reported there.

Only after you have fixed and/or proven access from the OS level should you start using VxVM tools on the device. 

Once your OS tools can successfullly see the disk, you should do 'vxdisk scandisks' (or 'vxdctl enable') so that VxVM can refresh his device tables with the new and/or fixed devices. 

 

chuckchang23's picture

Hi kjbss

It can be seen with the prtvoc command.

 

EMMDPD03:/# prtvtoc /dev/rdsk/c0t2d0s2

* /dev/rdsk/c0t2d0s2 partition map
*
* Dimensions:
*     512 bytes/sector
*      63 sectors/track
*     255 tracks/cylinder
*   16065 sectors/cylinder
*   36350 cylinders
*   36348 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector 
*           0     16065     16064
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       3      9    00      16065  10490445  10506509   /opt/bmc
       6     11    00   10506510 573424110 583930619   /backup
       8      1    01          0     16065     16064
EMMDPD03:/# 

my problem is that when i list down all disks, it shows the disk with an error state,

 

EMMDPD04:/# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0t0d0s2     auto:sliced     rootdisk     rootdg       online
c0t1d0s2     auto:sliced     rootmirror   rootdg       online
c0t2d0s2     auto            -            -            error   <---------------------- Error disk
c0t3d0s2     auto:none       -            -            online invalid
 
but when i try to fix this, it can't be shown on the VVM. Hope you could help me clear the error
 

 

starflyfly's picture

Hi,

  The disk is in error state, so you can't use replace  failed disk procedures to replace it.

 

  the error state is because you have no partition 2  in this disk.

   If you dont' need keep original data on this disk,

  use format  to create partition 2 for this disk, which  from 0 to last  sector.

 then , run:

  vxdctl enable,

  it should in  online invalid state.

 Be careful when do operation, make sure backup data if needed, and run vxdctl enable in non business time.

 

If the answer has helped you, please mark as Solution.

chuckchang23's picture

Hello Starflyfly,

 

Thank you for the input. I'm starting to understand what's going on :)

 

Since my goal is to reformat the disk and create partition, how do i make sure that files under the disk are not lost(if there are any?)

 

 

EMMDPD03:/# vxdisk list c0t2d0s2
Device:    c0t2d0s2
devicetag: c0t2d0
type:      auto
flags:     error private autoconfig
pubpaths:  block=/dev/vx/dmp/c0t2d0s2 char=/dev/vx/rdmp/c0t2d0s2
guid:      -
udid:      LSI%5FMR9262-8i%5FDISKS%5F600605B002952B10167068FF1DB9ECA3
site:      -
Multipathing information:
numpaths:   1
c0t2d0s2        state=disabled
EMMDPD03:/# 
 
pubpaths are already defined, is this ok?
starflyfly's picture

Hi,

 You should use format to add partition 2, with full disk capacity, then run vxdctl enable, it will change to "online invalid"  state.

Here is my test log, hope you can first finish test in your bed.

================

 

root@hostAAA # prtvtoc /dev/rdsk/c2t500601603022FB3Fd17s2
* /dev/rdsk/c2t500601603022FB3Fd17s2 partition map
*
* Dimensions:
*     512 bytes/sector
*      10 sectors/track
*      64 tracks/cylinder
*     640 sectors/cylinder
*   32768 cylinders
*   32766 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector 
*           0      6400      6399
*    10492160   8389120  18881279
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       3      9    01       6400  10485760  10492159
       4      0    01   18881280   2088960  20970239   /test1
       6      0    01   10492160   8389120  18881279   /test
       7     15    01          0  20970240  20970239
 
 
root@hostAAA # vxdisk -eo alldgs list
DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR        
 
emc_clariion0_37 auto           -            -           error                c2t500601603022FB3Fd17s2 lun RAID_5  <<<< 
 
======
format
...
 
select  disk
p
partition> p
Current partition table (unnamed):
Total disk cylinders available: 32766 + 2 (reserved cylinders)
 
Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wu       0                0         (0/0/0)            0
  1 unassigned    wu       0                0         (0/0/0)            0
  2 unassigned    wu       0                0         (0/0/0)            0
  3 alternates    wu      10 - 16393        5.00GB    (16384/0/0) 10485760
  4 unassigned    wu   29502 - 32765     1020.00MB    (3264/0/0)   2088960
  5 unassigned    wu       0                0         (0/0/0)            0
  6 unassigned    wu   16394 - 29501        4.00GB    (13108/0/0)  8389120
  7 unassigned    wu       0                0         (0/0/0)            0
 
partition> 2
Part      Tag    Flag     Cylinders         Size            Blocks
  2 unassigned    wu       0                0         (0/0/0)            0
 
Enter partition id tag[unassigned]: backup
Enter partition permission flags[wu]: 
Enter new starting cyl[0]: 
Enter partition size[0b, 0c, 0e, 0.00mb, 0.00gb]: fie
Please specify units in either b(blocks), c(cylinders), e(end cylinder),
m(megabytes) or g(gigabytes)
Enter partition size[0b, 0c, 0e, 0.00mb, 0.00gb]: 32766c<<<<last partition number
partition> p
Current partition table (unnamed):
Total disk cylinders available: 32766 + 2 (reserved cylinders)
 
Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wu       0                0         (0/0/0)            0
  1 unassigned    wu       0                0         (0/0/0)            0
  2     backup    wu       0 - 32765       10.00GB    (32766/0/0) 20970240
  3 alternates    wu      10 - 16393        5.00GB    (16384/0/0) 10485760
  4 unassigned    wu   29502 - 32765     1020.00MB    (3264/0/0)   2088960
  5 unassigned    wu       0                0         (0/0/0)            0
  6 unassigned    wu   16394 - 29501        4.00GB    (13108/0/0)  8389120
  7 unassigned    wu       0                0         (0/0/0)            0
 
partition> label
Ready to label disk, continue? 
Ready to label disk, continue? y
 
partition> q
 
 
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> q
root@hostAAA # vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
 
emc_clariion0_37 auto            -            -            error   <<<<<
 
root@hostAAA # vxdctl enable     <<<<<
root@hostAAA # vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
 
emc_clariion0_37 auto:none       -            -            online invalid<<<<<
 

If the answer has helped you, please mark as Solution.

starflyfly's picture

 if  you like do vxdisksetup for this disk, the data in the old file system will lost.

 

If the answer has helped you, please mark as Solution.

Yasuhisa Ishikawa's picture

I wonder why you tried to replace disk. There are no "failed" disk media in "vxdisk list" output. c0t2d0s2 is in error state, but it just mean c0t2d0s2 is not initialized at OS level for use of VxVM.

By prtvtoc output, c0t2d0s2 is used without VxVM, so do not format it by format command or vxdisksetup. Ignore 'error' status and keep it as it is.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Gaurav Sangamnerkar's picture

Hi,

If a disk is in error state, the two main causes that drills down are:

1. disk partition table has issues

2. paths to disk are disable .

I agree with starflyfly's advice, you need to fix the partition table & get the disk to online invalid state. If the disk had data before & you want to recover data, you need to ensure that partition table is restored correctly as it was before & while intializing disk in veritas, you need to restore exsting configuration of privlen, publen attributes .. you can use this options with vxdisk init or vxdisksetup..

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

chuckchang23's picture

Hi Gaurav, 

 

is there a way to check if the disk partition has files before?

kjbss's picture

If you *know* that the disk used to be managed by VxVM, then you would need to get the partition layout as it was back then and reapply that exactly to the disk, as Gaurav says.  

Interestingly, from the prtvtoc output you provided, partition 7 has the VxVM Tag (15) and points to the entire disk, so in that way it does appear that it was at one time a VxVM managed disk.

However, the prtvtoc output also now shows two slices (4 and 6) with Mount Directories associated with them, and so it looks like this disk was *last* used as a test disk outside of VxVM management:

*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       3      9    01       6400  10485760  10492159
       4      0    01   18881280   2088960  20970239   /test1
       6      0    01   10492160   8389120  18881279   /test
       7     15    01          0  20970240  20970239

We can see that slices 4 and 6 were likely used for testing purposes, but if you really want to see the files in those partitions:

...Taking slice 6 as an example:

Check to see if it is a mountable partition:
  $ fstyp /dev/rdsk/c2t500601603022FB3Fd17s6

If it shows to be a filesystem on there, like ufs or vxfs, sanity-check the filesystem:
  $ fsck -F <FStype> -y /dev/rdsk/c2t500601603022FB3Fd17s6

Make a temporary mount point for it:
  $ mkdir /tmp_test

Mount it:
  $ mount -F <FStype> /dev/dsk/c2t500601603022FB3Fd17s6 /tmp_test

Inspect it however you want to...
  $ ls -l /tmp_test
  ...etc...

kjbss's picture

Hi again chuckchang23 --

I just noticed I based my last advice to you on the prtvtoc output from starflyfly's test envrionment!

Naughty of me; sorry about that...

The pertinent section of your 'prtvtoc /dev/rdsk/c0t2d0s2' output shown below:

*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       3      9    00      16065  10490445  10506509   /opt/bmc
       6     11    00   10506510 573424110 583930619   /backup
       8      1    01          0     16065     16064

Well, it would appear to me that this disk never had VxVM management on it, or at least has been reformatted since.

The point is, if you want to see the data on there...:

(Using slice 3 as the expample, which seems to contain BMC software data (/opt/bmc) data on there)...

Check to see if it is a mountable partition:
  $ fstyp /dev/rdsk/c0t2d0s3

If it shows to be a filesystem on there, like ufs or vxfs, sanity-check the filesystem:
  $ fsck -F <FStype> -y /dev/rdsk/c0t2d0s3
 
Make a temporary mount point for it:
  $ mkdir /tmp_opt_bmc

Mount it:
  $ mount -F <FStype> /dev/dsk/c0t2d0s3 /tmp_opt_bmc
       
Inspect it however you want to...  
  $ ls -l /tmp_opt_bmc
  ...etc...

 

chuckchang23's picture

Hi kjbss,

 

The first command issued an error on my faulted disk

 

 

EMMDPD03:/# fstyp /dev/rdsk/c0t2d0s2
hsfs fstyp: cannot open </dev/rdsk/c0t2d0s2>
/dev/rdsk/c0t2d0s2: I/O error
udfs fstyp: cannot open </dev/rdsk/c0t2d0s2> errorno <5>
/dev/rdsk/c0t2d0s2: I/O error
UX:vxfs fstyp: ERROR: V-3-20003: Cannot open /dev/rdsk/c0t2d0s2: I/O error
open64: I/O error
Unknown_fstyp (no matches)
EMMDPD03:/#
 
EMMDPD03:/# fsck -F ufs -y /dev/rdsk/c0t2d0s2
Can't open /dev/rdsk/c0t2d0s2: I/O error
EMMDPD03:/# 
 
 

 

stinsong's picture

Hi chuck,

The I/O error indicate that there is I/O problem with the disk /dev/rdsk/c0t2d0s2.

You should check on the I/O error first for HW issue or link problem.

kjbss's picture

chuckchange23 -

It would seem that you have transient access to disk /dev/rdsk/c0t2d0s2, because on your 10 May 2013 post above, you show 'prtvtoc  /dev/rdsk/c0t2d0s2' working -- this would not have worked if you had I/O errors to that disk, as shown in your 22 May 2013 post.

As stinsong points out, you need to investigate and resolve your I/O errors first.

Do you have this drive on an array that has active/passive support to your host?  Maybe another host has the active path to the drive, or some other kind of SAN zoning preventing you from accessing that drive from your EMMDPD03 host on the 22 May.

 

chuckchang23's picture

Hi KJBSS,

 

   How do i check what you mean by this 

       "Do you have this drive on an array that has active/passive support to your host? "

   Im not really that familiar with symantec 

  

kjbss's picture
chuckchang23 --

Here's an example of a disk device that is on an active/passive array:

Use vxdisk list on the device in order to see the paths to the device and whether they are all primary or not:

$ vxdisk list c1t5006016041E0B566d26s2
Device:    c1t5006016041E0B566d26s2
devicetag: c1t5006016041E0B566d26
type:      auto
hostid:   
disk:      name= id=1228990244.166.myhost81
group:     name=paytdg id=1228990226.158.myhost81
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig
pubpaths:  block=/dev/vx/dmp/c1t5006016041E0B566d26s2 char=/dev/vx/rdmp/c1t5006016041E0B566d26s2
guid:      {f8ee5150-1dd1-11b2-a075-00144fb7bfa0}
udid:      DGC%5FRAID%205%5F6ARA600581%5F6006016077002100249BE954D575DD11
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=2031232 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1368695151 seqno=0.45
ssb:       actual_seqno=0.2
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   4
c1t5006016041E0B566d26s2        state=enabled   type=primary
c3t5006016141E0B566d26s2        state=enabled   type=primary
c3t5006016941E0B566d26s2        state=enabled   type=secondary
c1t5006016841E0B566d26s2        state=enabled   type=secondary

You can see above that some paths to the same LUN-device are "type=secondary" and others are "type=primary".  You cannot access LUN-devices via the secondary paths.  However, you should note that the "pubpaths:  block=/dev/vx/dmp/c1t5006016041E0B566d26s2 char=/dev/vx/rdmp/c1t5006016041E0B566d26s2" line shows you how you can realiably access the LUN no matter which paths to the LUN are currently "primary".  I:

$ prtvtoc /dev/vx/dmp/c1t5006016041E0B566d26s2
* /dev/vx/rdmp/c1t5006016041E0B566d26s2 partition map
*
* Dimensions:
*     512 bytes/sector
*      16 sectors/track
*       4 tracks/cylinder
*      64 sectors/cylinder
*   32768 cylinders
*   32766 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       2      5    01          0   2097024   2097023
       7     15    01          0   2097024   2097023

Below you can see the error you can get if you try to access the device via a non-primary path:

$ prtvtoc /dev/dsk/c1t5006016841E0B566d26s2
prtvtoc: /dev/rdsk/c1t5006016841E0B566d26s2: Unable to read Disk geometry errno = 0x5

Below you can see that there is no error when you access the device via a primary path:

$ prtvtoc /dev/dsk/c1t5006016041E0B566d26s2
* /dev/dsk/c1t5006016041E0B566d26s2 partition map
*
* Dimensions:
*     512 bytes/sector
*      16 sectors/track
*       4 tracks/cylinder
*      64 sectors/cylinder
*   32768 cylinders
*   32766 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       2      5    01          0   2097024   2097023
       7     15    01          0   2097024   2097023
 

Below you can see your controllers to your devices and their enclosure type:

$ vxdmpadm listctlr all
CTLR-NAME       ENCLR-TYPE      STATE      ENCLR-NAME
=====================================================
c0              Disk            ENABLED      disk
c1              EMC_CLARiiON    ENABLED      emc_clariion0
c3              EMC_CLARiiON    ENABLED      emc_clariion0
c1              EMC_CLARiiON    ENABLED      emc_clariion1
c3              EMC_CLARiiON    ENABLED      emc_clariion1

EMC_CLARiiON arrays are "Active/Passiv" arrays, where only certain paths are active at a time.

You can use the "vxdmpadm listctlr all" command on your system to see what kind of arrays you have, if any, in your configuration.

Hope that helps, but I doubt it, because you have an I/O error, which is much more a hardware-physical layer problem.  You need your hardware looked at by your array's hardware Field Engineer (or possibly your server's hardware engineer if the problem is with the HBA in your host).

 

chuckchang23's picture

Hi Everyone, 

 

thank you for the answers :) its starting to make sense now. 

 

After all the research, is there a way to enable the path of this disk?

 

EMMDPD03:/var/VRTSvcs/lock# cat cvmvoldg4_ora1dg_vxnotify | tail
marked as failing path c0t2d0s2 belonging to dmpnode c0t2d0s2
enabled path c0t2d0s2 belonging to dmpnode c0t2d0s2
enabled dmpnode c0t2d0s2
disabled path c0t2d0s2 belonging to dmpnode c0t2d0s2
disabled dmpnode c0t2d0s2
marked as failing path c0t2d0s2 belonging to dmpnode c0t2d0s2
enabled path c0t2d0s2 belonging to dmpnode c0t2d0s2
enabled dmpnode c0t2d0s2
disabled path c0t2d0s2 belonging to dmpnode c0t2d0s2
disabled dmpnode c0t2d0s2
EMMDPD03:/var/VRTSvcs/lock# 
kjbss's picture

What was the resolution to your earlier I/O errors? 

If there are no known media nor SAN issues, Dynamic Multi Pathing (DMP) disables/enables disk paths after receiving SCSI Errors can be caused if your disk has no valid disk label on it (from TECH188277):

On the solaris server there were many disks with no disk label. DMP was unable to check the disk's associated paths because of there being no VTOC, so ended up failing the device and associated paths. Subsequently, DMP re-enables the path and disables it once again at the next check, and so on.

To enable a path:

vxdmpadm enable ctlr= enclosure=

...where the CTLR-NAME and ENCLR-NAME are displayed via the 'vxdmpadm listctlr all' command.

Make sure you label c0t2d0s2:

$ format c0t2d0
> label
> y
> q

 

All the while, monitor your OS and DMP logs for errors.  IE:

tail -f /var/adm/messages

tail -f /var/adm/vx/dmpevents.log

 

g_lee's picture

chuckchang23,

As others have pointed out (eg: kjbss, Gaurav), it appears there are problems with access / i/o to the disk - as you are unable to run prtvtoc at times but other times it works.

From the output provided, it appears the disk is local / not SAN or EMC powerdevice (as the other powerdevices are showing correctly, and vxdisk list shows it's an LSI disk).

Check that it appears correctly in format, if there are errors shown in iostat -En, the status in cfgadm.

To reenable the disk in vxvm, it needs to be accessible (ie: you need to sort out the i/o errors), and to have a valid label (ie: if you have intermittent problems running prtvtoc to display the label, then vxvm is going to show the disk in error as it won't be able to read the label either).

Also note per Yasuhisa's comment ( https://www-secure.symantec.com/connect/forums/vxd... ) - it appears this disk has been used outside vxvm, as your prtvtoc shows s3 and s6 were previously mounted. So whatever is using the disk at the moment may have had its own reasons for removing/not having slice 2 -- so creating s2 now may cause issues.

If you want to use the disk in vxvm, you will need to relabel the disk; however unless you know the history of the machine / have confirmed whatever was using it previously is definitely not impacted by this, you should exercise caution / be prepared to potentially restore a backup of any data that was on this disk as the relabel may render the previous data inaccessible.

regards,

Grace

If this post has helped you, please vote or mark as solution

CliveE's picture

Hi chuckchang23,

Looks like you are making some progress thanks to the good replies here. Would be best to progress this type of enquiry over in the Storage Foundation forum as this not really a cluster server related command.

Cheers