Volume Manager doesn't start on reboot after CPI installer option "Stop a Product" is run
Article ID: 100033510
Updated On:
Description
Error Message
The following error was seen when attempting to query LUNs under Volume Manager control:-bash-4.1# vxdisk list
VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible
Cause
On Solaris 11.1, the "Stop a Product" option within the installer script runs a rem_drv command, which unloads the driver and updates /etc/system and /etc/name_to_major, meaning that the drivers will not load automatically after reboot
Resolution
To avoid administrative intervention, the CPI installer's option of "Start a Product" should be used to start Storage Foundation. Choosing this option will restore /etc/system and /etc/name_to_major.
It should be noted that the start and stop options to the installer script are typically used in patching/upgrade scenarios to facilitate more controlled stopping of products.
It should be noted that the start and stop options to the installer script are typically used in patching/upgrade scenarios to facilitate more controlled stopping of products.
Issue/Introduction
A Solaris 11.1 machine running Storage Foundation 6.2.1, where boot disk was not under VxVM control, was not able to start Volume Manager on reboot after the CPI installer script option "Stop a Product" had been run to stop Storage Foundation.
Was this article helpful?
Yes
No
Powered by
