Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Device does not match the kernel configuration

Created: 27 Apr 2014 • Updated: 12 Jun 2014 | 7 comments
This issue has been solved. See solution.

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 

 

 

Operating Systems:

Comments 7 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

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
 

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.
 

Gaurav Sangamnerkar's picture

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

 

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.
 

novonil_choudhuri's picture

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

Best Regards,

Novonil

starflyfly's picture

which os version, sf version?

 

try : vxdisk -f init c2t0d0

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

Marianne's picture

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.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Gaurav Sangamnerkar's picture

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

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.
 

SOLUTION
starflyfly's picture

Hi, about e2866997,

 

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

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