Suppressing the primary path of an encapsulated SAN boot disk from Veritas Volume Manager causes the system reboot to fail (1933631)

Last published : Sep 18, 2026
If you suppress the primary path of an array from VxVM control and then reboot the system, the system boot fails.
If you have an encapsulated SAN boot device with multiple primary paths, the issue occurs when you suppress the first primary path. When you configure a SAN boot device, the primary path is set as a boot device. In general, the first path of the SAN boot device corresponds to the first configured path during SAN boot. Even if another primary path is configured as a boot device, suppressing the first device from VxVM causes the boot to fail.

Workaround:

When the boot device is suppressed from VxVM, change the OS boot device sequencing accordingly.
For Solaris SPARC system, use the eeprom boot-device command to set the boot device sequencing.
For Solaris x86-64 systems, use the eeprom bootpath command to set the boot device sequencing.