Solaris Volume Manager: 'boot -a' with Default Root Device Will Not Boot Properly if Root Disk is Mirrored With SVM / SDS
Last updated on NOVEMBER 03, 2016
Applies to:Solstice DiskSuite Software - Version 4.2 to 4.2.1 [Release 4.0]
Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.10.0 [Release 11.0]
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)
Typically system administrators use "boot -a" when they need to boot with an alternative /etc/system file, or control how a system boots, or troubleshoot booting problems. Unfortunately with Solaris 10 even if the correct boot parameters are provided during a "boot -a" the system will still fail to boot, the system panic at boot time.
Dependant on the versions of Solaris and the circumstances under which the "boot -a" was needed, will determine the action required to resolve the issues seen.
For Solaris 8 and Solaris 9, with a correctly functioning system that boots normally, the problem can be resolved, by providing the "pseudo" device during the "boot -a" interactive phase.
For Solaris 10 even providing the correct "pseudo" device does not work as expected (the system panic's), the recommended solution is to boot "failsafe" or alternate media, and unmirror / unencapsulate the root disk before attempting to use "boot -a"..
Example 1: Boot failure Solaris 8 and 9 "boot -a" with the default parameters
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms