My Oracle Support Banner

Sanboot LDOMs Didn't Boot After upgrade to Solaris 11.3 SRU35.6 (Doc ID 2471292.1)

Last updated on NOVEMBER 12, 2019

Applies to:

Solaris Operating System - Version 11.3 to 11.4 [Release 11.0]
SPARC T5-8 - Version All Versions to All Versions [Release All Releases]
SPARC T7-2 - Version All Versions to All Versions [Release All Releases]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)

Symptoms

The guest ldoms with sanboot disks presented directly to the primary and alterio domians failed to boot up after the Solaris 11.3 upgrade to SRU 35.6.0 due to the sanboot disk path were not found.

The error message example:

# ldm bind potapsd00015
Path /dev/dsk/c0t60001440000000107029CFE9EADDA73Ed0s2 is not a valid file or
device on service domain alterio
Path /dev/dsk/c0t60001440000000107029CFE9EADDA743d0s2 is not a valid file or
device on service domain alterio

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.