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

Failed disks cannot be able to replace

Created: 02 Jul 2014 • Updated: 11 Jul 2014 | 3 comments
This issue has been solved. See solution.

Hi Support

We cannot be able to replace the failed disks.Please find the below logs--

DEVICE       TYPE            DISK         GROUP        STATUS
c1t0d0s2     auto:sliced     rootdisk     rootdg       online
c1t1d0s2     auto:sliced     rootmirr     rootdg       online
c1t2d0s2     auto:none       -            -            online invalid
c1t3d0s2     auto:none       -            -            online invalid
c1t4d0s2     auto:none       -            -            online invalid
c1t5d0s2     auto:none       -            -            online invalid
c1t8d0s2     auto:none       -            -            online invalid
c1t9d0s2     auto:none       -            -            online invalid
c1t10d0s2    auto:none       -            -            online invalid
c1t11d0s2    auto:none       -            -            online invalid
c1t12d0s2    auto:none       -            -            online invalid
c1t13d0s2    auto:none       -            -            online invalid
c2t40d0s2    auto:cdsdisk    disk2        ossdg        online
c2t40d1s2    auto:cdsdisk    disk3        ossdg        online
c3t40d0s2    auto:cdsdisk    -            -            online-----------------------------Disks are there
c3t40d1s2    auto:cdsdisk    -            -            online-----------------------------Disks are there
-            -         disk2mirr    ossdg        failed was:c3t40d0s2
-            -         disk3mirr    ossdg        failed was:c3t40d1s2

When using vxdiskadm utilty getting the below error,it is saying that no disk available for replacement--

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Disk group: rootdg

DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE

Disk group: ossdg

DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE

dm disk2mirr    -            -        -        -        NODEVICE
dm disk3mirr    -            -        -        -        NODEVICE

Select a removed or failed disk [<disk>,list,q,?] disk2mirr
  VxVM  ERROR V-5-2-1985 No devices are available as replacements for disk2mirr.

Select a different disk ? [y,n,q,?] (default: n)

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Operating Systems:

Comments 3 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

Hi,

disks are appearing online without any diskgroup information ... were the disks reinitialized again using vxdisksetup command ?

can u paste below output

# vxdisk -o alldgs list

# modinfo |grep -i vx

# ls -ltr /etc/vx/cbr/bk/*ossdg*/

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.
 

ARUP JYOTI THAKURIA's picture

Hi gaurav

thanks for your revert,this issue got resolved by the following command--

Attaching the disks again with -k option.

vxdg -k -g ossdg adddisk disk2mirr=c3t40d0s2

vxdg -k -g ossdg adddisk disk3mirr=c3t40d1s2

regards

Arup

SOLUTION
Gaurav Sangamnerkar's picture

Hi Arup,

This can happen in older version of vxvm, not sure what version you are on but above state could be a tricky one, reason being disks are appearing online without any diskgroup information .. could be 2 possible states here

1. Diskgroup was force imported when you had 2 disks failed that means DG was imported forcefully with 2 disks available, that is why when your reamaining 2 disks came online, you don't see dg information from them. Probably if you would run a "vxdisk -o alldgs list" you would have got a confirmation if private region on those disks is intact & dg information is stored on them.

2. what you have done is force added disk back to dg using same name which disk had previously (-k switch). Good that disk contained the information of dg & hence was able to add back. This state can also appear if someone accidently reinitialized the disks (after they were available again) & hence private region information is lost. In that case, even if you would add them using -k switch, you may have lost the data

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.