cancel
Showing results for 
Search instead for 
Did you mean: 

Device does not match the kernel configuration

karthik1988
Level 2

Dear Symantec Colleague,

 

One of the Disk is giving Error when am trying to take it in Veritas Control.

 

root@gumas1n> /etc/vx/bin/vxdisksetup -i c2t0d0
VxVM vxdisksetup ERROR V-5-2-57 /dev/vx/rdmp/c2t0d0: Device does not match the kernel configuration

 

Please share the ideas .to resolve this issue.

 

I tried to configure through vxdiskadm command but not working 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Gaurav_S
Moderator
Moderator
   VIP    Certified

I found one of my teams faced this issue in past & did opened a case with Symantec. This happened post patching the server to patch 147440-20 level.

This was found as bug as addressed in below technote

http://www.symantec.com/docs/TECH193395

not sure if this is the same case with you & thats why was asking if there was any recent activity done on server.

 

G

View solution in original post

7 REPLIES 7

Gaurav_S
Moderator
Moderator
   VIP    Certified

Hi

Does this device exist in configuration ? can you paste following

# vxdisk list c2t0d0

# vxdisk -e list

# modinfo |grep -i vx

# echo | format

also, what storage are you using in backend ?

 

 

G
 

Gaurav_S
Moderator
Moderator
   VIP    Certified

I was reading an article & thought of a question ..  was there any recent activity done on server ?

 

G

novonil_choudhu
Level 4
Employee Accredited

You may have to do a # vxdiskunsetup -C and then # vxdisksetup -i. 

starflyfly
Level 6
Employee Accredited Certified

which os version, sf version?

 

try : vxdisk -f init c2t0d0

Marianne
Level 6
Partner    VIP    Accredited Certified

Use 'format' or 'prtvtoc' to check if slice 2 represents the full disk.

prtvtoc /dev/rdsk/c2t0d0s2

 

Also found this TN: http://www.symantec.com/docs/TECH181050

 

**** EDIT ****

Moved post to Storage Foundation forum as this is not Cluster related.

Gaurav_S
Moderator
Moderator
   VIP    Certified

I found one of my teams faced this issue in past & did opened a case with Symantec. This happened post patching the server to patch 147440-20 level.

This was found as bug as addressed in below technote

http://www.symantec.com/docs/TECH193395

not sure if this is the same case with you & thats why was asking if there was any recent activity done on server.

 

G

starflyfly
Level 6
Employee Accredited Certified

Hi, about e2866997,

 

fix include in 6.0.5, 6.0.3.100,6.0.3, 5.1sp1rp4.