Volume Manager doesn't start on reboot after installing fsadv-sol11_sparc-6.0.5.100
Article ID: 100033516
Updated On:
Description
Error Message
# vxdisk listVxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible
Cause
Two problems had occurred during the addition of the patch:
a) /etc/system forceload entries for Volume Manager drivers were commented out
*forceload: drv/vxdmp
*forceload: drv/vxio
*forceload: drv/vxspec
b) /etc/name_to_major had no entries for Volume Manager drivers:
# grep vx /etc/name_to_major
vxge 277
vxlo 293
a) /etc/system forceload entries for Volume Manager drivers were commented out
*forceload: drv/vxdmp
*forceload: drv/vxio
*forceload: drv/vxspec
b) /etc/name_to_major had no entries for Volume Manager drivers:
# grep vx /etc/name_to_major
vxge 277
vxlo 293
Resolution
Workaround:
# cd /kernel/drv/
# add_drv vxdmp
# add_drv vxio
# add_drv vxspec
and also uncommented VxVM forceload entries in /etc/system:
forceload: drv/vxdmp
forceload: drv/vxio
forceload: drv/vxspec
and rebooted - machine came up fine
Similar issues are seen on early releases of 6.0 and Solaris 11. Storage Foundation 6.2 and later has no such problem.
# cd /kernel/drv/
# add_drv vxdmp
# add_drv vxio
# add_drv vxspec
and also uncommented VxVM forceload entries in /etc/system:
forceload: drv/vxdmp
forceload: drv/vxio
forceload: drv/vxspec
and rebooted - machine came up fine
Similar issues are seen on early releases of 6.0 and Solaris 11. Storage Foundation 6.2 and later has no such problem.
Issue/Introduction
Volume Manager doesn't start on reboot after installing fsadv-sol11_sparc-6.0.5.100
It is also possible that the system will hang on boot in some circumstances, requiring manual intervention.
It is also possible that the system will hang on boot in some circumstances, requiring manual intervention.
Was this article helpful?
Yes
No
Powered by
