11-10-2011 03:06 AM
Due to some reason team as removed the rootmirrored disk & once we attached the disk and while giving
the initialize cmd it throws some error :
# vxdisksetup -i c0t1d0 format=sliced
VxVM vxdisk ERROR V-5-1-5433 Device c0t1d0s2: init failed:
Internal configuration daemon error
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:sliced rootdg01 rootdg online
c0t1d0s2 auto:sliced - - error
c1t50060E800548764Dd0s2 auto:cdsdisk SE2-Diskd0 BACKUPDG01 online
c1t50060E800548764Dd1s2 auto:cdsdisk SE2-Diskd1 BACKUPDG01 online
c1t50060E800548764Dd2s2 auto:cdsdisk SE2-Diskd2 BACKUPDG01 online
c1t50060E800548764Dd3s2 auto:cdsdisk SE2-Diskd3 BACKUPDG01 online
its not coming in online..
please can any one say me to solve this problem....
Thanks in advance
11-10-2011 03:25 AM
Can you run:
vxconfigd -k -r reset
Link to check:
11-10-2011 04:48 AM
Can you show the output of "vxdisk list c0t1d0"
Also does the device show a healthy VTOC/partition table ?
11-10-2011 04:49 AM
11-11-2011 12:46 AM
could be couple of things here to know:
1. Is the rootmirror disk replaced or you are using the same disk ?
2. are you able to run any other vx commands normally like "vxdisk list" etc. (I hope yes)
3. can u show the process for vxconfigd from ps output here ? (ps -ef |grep -i vxconfigd)
4. Also paste the output what Tony is asking above.
5. As the disk is in error state, can u confirm if you have labelled the disk ?
01-09-2012 03:55 PM
Hello all, I have researched to the end of internet trying to find exact error:
VxVM vxdg ERROR V-5-1-10978 Disk group dg01rdbmsCRMp: import failed:
Disk is sharable, operation not supported
Server model (model): ia64 hp Integrity BL870c i2
Operating system (uname -a): HP-UX crmpbs03 B.11.31 U ia64 1017400452 unlimited-user license
Product: VxVM 5.0.1
This very early morning a cloning procedure (based on BCV) used every day by the customer failed.
The customer has identified the failed command on the system crmpbs03 (belonging to a two nodes CFS cluster):
vxdg -o useclonedev=on -o updateid -tfC import dg01rdbmsCRMp
Since this command is in a script, the customer does not have the error message but only the return code equal to "5".
Then the customer rebooted the system but the command failed again at 1:26 05/01/2012.
Then, after a second reboot, the procedure worked fine.
01-17-2012 07:26 PM
I would first check the disk with format command as suggested by Tony,
If the disk appears to be ok from format checking, you might run vxdiskunsetup first.