Go to main content

Updating Your Oracle® Solaris Cluster 4.4 Environment

Exit Print View

Updated: March 2019

How to Recover from a Failed Dual-Partition Update

If you experience an unrecoverable error during dual-partition update, perform this procedure to back out of the update.

Note -  You cannot restart a dual-partition update after the update has experienced an unrecoverable error.
  1. Assume the root role on each node of the cluster.
  2. Boot each node into noncluster mode.
    • SPARC:
      ok boot -x
    • x86:
      1. In the GRUB menu, use the arrow keys to select the appropriate Oracle Solaris entry and type e to edit its commands.

        For more information about GRUB based booting, see About Run Level Booting in Booting and Shutting Down Oracle Solaris 11.4 Systems.

      2. In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.
      3. Add -x to the multiboot command to specify that the system boot into noncluster mode.
      4. Press Enter to accept the change and return to the boot parameters screen.

        The screen displays the edited command.

      5. Type b to boot the node into noncluster mode.

        Note - This change to the kernel boot parameter command does not persist over the system boot. The next time you reboot the node, it will boot into cluster mode. To boot into noncluster mode instead, perform these steps to again add the –x option to the kernel boot parameter command.
  3. On each node, run the update recovery script.
    phys-schost# scinstall -u recover

    Specifies update.


    Restores the /etc/vfstab file and the Cluster Configuration Repository (CCR) database to their original state before the start of the dual-partition update.

    The recovery process leaves the cluster nodes in noncluster mode. Do not attempt to reboot the nodes into cluster mode.

    For more information, see the scinstall(8) man page.

  4. Perform either of the following tasks.
    • Restore the old software from backup to return the cluster to its original state.
    • Continue to update software on the cluster by using the standard update method.

      This method requires that all cluster nodes remain in noncluster mode during the update. See the task map for standard update, Table 1, Task Map: Performing a Standard Update for Oracle Solaris Cluster 4.4 Software. You can resume the update at the last task or step in the standard update procedures that you successfully completed before the dual-partition update failed.