cancel
Showing results for 
Search instead for 
Did you mean: 

disk in error state in vxdisk list

symsonu
Level 6

disk replacement was performed for  c1t2d0s2 and after that we are not able to add this disk into dg.

I can see duplicate entry of c1t2d0s2 in vxdisk list

 

abcmas3{root} #: vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c1t1d0s2     auto:none       -            -            online invalid
c1t2d0s2     auto            -            -            error
c1t2d0s2     auto            -            -            error
c1t3d0s2     auto:none       -            -            online invalid
c1t4d0s2     auto:none       -            -            online invalid
c1t5d0s2     auto:none       -            -            online invalid
c1t8d0s2     auto:none       -            -            online invalid
c1t9d0s2     auto:sliced     disk2mirr    datadg        online
c1t10d0s2    auto:sliced     disk3mirr    datadg        online
c1t11d0s2    auto:sliced     disk4mirr    datadg        online
c1t13d0s2    auto:sliced     disk5mirr    datadg        online
c2t0d0s2     auto:none       -            -            online invalid
c2t12d0s2    auto:sliced     disk6mirr    datadg        online

 

I tried to lable c1t2d0 and then vxdctl enable , it dinot come to invalid online.

 

what should be the way forward here?

 

 

 

 

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You forgot to mention your SF version?

Cleaning up the device tree may help.
See http://www.symantec.com/docs/TECH57018

symsonu
Level 6

 

Now, there is only one entry as shown below, however its in error state.

c1t1d0s2     auto:sliced     disk2        datadg        online
c1t2d0s2     auto            -            -            error
c1t3d0s2     auto:sliced     disk4        datadg        online
c1t4d0s2     auto:sliced     disk5        datadg        online
c1t5d0s2     auto:sliced     disk6        datadg        online
c1t8d0s2     auto:none       -            -            online invalid
c1t9d0s2     auto:sliced     disk2mirr    datadg        online
c1t10d0s2    auto:sliced     disk3mirr    datadg        online
c1t11d0s2    auto:sliced     disk4mirr    datadg        online
c1t13d0s2    auto:sliced     disk5mirr    datadg        online
c2t0d0s2     auto:none       -            -            online invalid
c2t2d0s2     auto:none       -            -            online invalid
c2t12d0s2    auto:sliced     disk6mirr    datadg        online

Version is as below :-->

 

 

30  1391850  3ae18 312   1  vxdmp (VxVM 5.0_MP1_RP5: DMP Driver)
 32 7c002000 340ec8 313   1  vxio (VxVM 5.0_MP1_RP5 I/O driver)
 34 7bfe4000   a2c8 316   1  fdd (VxQIO 5.0_REV-5.0MP1RP4a5_sol Q)
 35  13c87e0    d40 314   1  vxspec (VxVM 5.0_MP1_RP5 control/status)
 82 7b200000 1bd5a8  21   1  vxfs (VxFS 5.0_REV-5.0MP1RP4a5_sol Su)
232 7afb9180    c38 315   1  vxportal (VxFS 5.0_REV-5.0MP1RP4a5_sol po)

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Have you confirmed that disk is labelled?

Try once again to label and then initialize the disk.

PS:
Are you aware of the fact that SF 5.0 has reached EOSL?

https://www-secure.symantec.com/connect/blogs/storage-foundation-and-high-availability-solutions-sfh...

TonyGriffiths
Level 6
Employee Accredited Certified

Hi

Is this disk a new disk ?

Is the disk visible to the o/s ? does it have a VTOC/label ?

Can you show the output of

       vxdisk list <disk>

As Marianne mentioned 5.0 has reached EOSL

cheers

tony

starflyfly
Level 6
Employee Accredited Certified

Hi, 

  

1. make sure device tree is clean, and disk  is ok:

#devfsadm –Cv                                                                           

use dd read to test if disk is ok:

 

 # dd if=/dev/rdsk/c1t2d0s2 of=/dev/null bs=1024k count=100

 

2. get  prtvtoc for the disk:

# prtvtoc /dev/rdsk/c1t2d0s2   

 

3.make sure the disk is proper labled.

# cfgadm –alo show_FCP_dev

# echo label > /tmp/fmt ; format –d c#t#d# -s –f /tmp/fmt                       << Label the LUN ( c#t#d# ) prior to updating VxVM

 

 

4.refer http://www.symantec.com/docs/TECH57018

freeze vcs sg, 

# mv disk.info disk.backup

# mv array.info array.backup

# rm /dev/vx/dmp/*

# rm /dev/vx/rdmp/*

 #rm /dev/dsk/c#t#d#s# <------Remove all entries except for internal boot devices.
#rm /dev/rdsk/c#t#d#s# <-------Remove all entries except for internal boot devices.
#devfsadm -Cv 
#vxconfigd -k