cancel
Showing results for 
Search instead for 
Did you mean: 

protocol error with volume configuration daemon

trba
Level 3
Hi There,
 
we had a hard drive failure which we have swapped and restored our unix but we are having problems with our veritas volume manager.
 
when the server is booting up we get the following error:
 
"vold is not enabled for transactions
 
no volumes started"
 
when we try and use any vxvm commands we get the following error:
 
"protocol error with volume configuration daemon"
 
 
this makes it so we can't acces the rest of our hard drives. we are running a Fujitsu Team server S Series with ICL Unix NX 7mplus V11 L10 and veritas volume manager 1.3.
 
any assistance would be greatly appreciated
 
thanks
7 REPLIES 7

trba
Level 3
hi guys i have run the debug and get the following:
 
# vxconfigd -x9
DEBUG:
VOLD STARTUP pid=5135
DEBUG: IOCTL GET_VOLINFO: return 0(0x0)
DEBUG: IOCTL ABORT_KTRANS: failed: errno=22 (Invalid argument)
DEBUG: IOCTL GET_KMEM id=0 size=68: return 0(0x0)
        Results: got 68 bytes
DEBUG: IOCTL RESET_KERNEL: return 0(0x0)
DEBUG: IOCTL SET_KMEM id=0 size=68: return 0(0x0)
DEBUG: IOCTL GET_KMEM id=1 size=0: failed: errno=2 (No such file or directory)
DEBUG: IOCTL SET_KMEM id=1 size=0: return 0(0x0)
DEBUG: Found SCSI disk /dev/dsk/c0d0    - Hard disc
DEBUG: Found SCSI disk c0d0: base dev=17/63
DEBUG: Found SCSI disk /dev/dsk/c0d1    - Hard disc
DEBUG: Found SCSI disk c0d1: base dev=17/575
DEBUG: Found SCSI disk /dev/dsk/c0d2    - Hard disc
DEBUG: Found SCSI disk c0d2: base dev=17/1087
DEBUG: Found SCSI disk /dev/dsk/c0d3    - Hard disc
DEBUG: Found SCSI disk c0d3: base dev=17/1599
DEBUG: Found SCSI disk /dev/dsk/c0d4    - Hard disc
DEBUG: Found SCSI disk c0d4: base dev=17/2111
DEBUG: Found SCSI disk /dev/dsk/c0d5    - Hard disc
DEBUG: Found SCSI disk c0d5: base dev=17/2623
DEBUG: Found SCSI disk /dev/dsk/c1d0    - Hard disc
DEBUG: Found SCSI disk c1d0: base dev=17/4159
DEBUG: Found SCSI disk /dev/dsk/c1d1    - Hard disc
DEBUG: Found SCSI disk c1d1: base dev=17/4671
DEBUG: Found SCSI disk /dev/dsk/c1d2    - Hard disc
DEBUG: Found SCSI disk c1d2: base dev=17/5183
DEBUG: Found SCSI disk /dev/dsk/c1d3    - Hard disc
DEBUG: Found SCSI disk c1d3: base dev=17/5695
DEBUG: Found SCSI disk /dev/dsk/c1d4    - Hard disc
DEBUG: Found SCSI disk c1d4: base dev=17/6207
DEBUG: Found SCSI disk /dev/dsk/c1d5    - Hard disc
DEBUG: Found SCSI disk c1d5: base dev=17/6719
DEBUG: vold: 12 disk devices installed.
 
vxvm:vxconfigd: ERROR: enable failed: Cannot create portal
        Device busy; aborting
hopefully this means something to someone?

springer
Level 4
modinfo | grep -i vx

i bet vxprotal; driver module not loaded try and do manually ( google to load solaris driver)

or check ur licence key

trba
Level 3
thanks for your reply springer,
 
our license is loaded ok, modinfo doesn't work on our server.
 
i will look into the vxportal for icl unix nx7
 
thanks  

springer
Level 4
ahhh ok .. have u a rootdg created prior to 4.0 u need rootdg ..if u restored aka after dead hearddrive u may have to do vxinstall and re-created rootdg via custom menu

trba
Level 3
i'm not sure what you mean by created before 4.0?
 
in dev/vx/dsk/rootdg we have the list of binary special files.
 
the files were restored to a new hard drive from the backup tape so everything is in place on c0d0.
 
i will have a look at vxinstall but if the daemon services aren't running will it let me alter them?

springer
Level 4
u cant just restore these files .. as part of rootdg is to create special slices on rootdiks aka tag 14 and tag 15 b.. and also maybe major/minor number of files aka devcie files might be different..

i suggest u do following

pkgchk VRTSvxvm and i bet u get lots errors so u might have to re-install  but at very least re-create rootdg ...but before u do that

can u confirm version  and u do know vxvm is onlu suuported on

sol,aix,hpux,linux ... and 4.0 is old supported version ... just fyi

trba
Level 3
finally got it working,
 
had to remove the vold
 
then start vxconfigd
 
this allowed vxinfo to show the volumes and then i started them with vxvol
 
rebooted the server and all seems ok
 
thanks for your help