EFI labeled disk under OVM for SPARC (LDoms) environment (Doc ID 1474271.1)

Last updated on DECEMBER 21, 2023

Applies to:

Symptoms

These symptoms are some of the possible observations resulted from EFI labeled disk *not* being export through slice 2 on the primary domain ldm(1M) configuration. Do note that once you have confirmed that the vdisk configurations are correctly configured as outlined here, the following symptoms can be due to other issues.

• Guest domain unable to find vdisk after primary domain reboot.
• Zpool on guest domain shown unavailable after guest/primary domain reboot.
• Disk label observed to have changed, either on primary or guest domain, with no known reboot or reason.
• The guest domain fails to boot due to missing boot disk.

Symptoms include (but may not limited to) corrupted label on the physical disk, corrupted boot block and/or boot archive on the guest domain, corrupted ZFS label on the guest domain, or disappeared underlying disk(s) in ZFS configuration on the guest domain.

On the I/O domain, errors similar to below may (or may not) be logged in /var/adm/messages file:

Note the guest domain may run normally for days or even months before the symptoms appear.

Example of the error when trying to add EFI labeled disk using slice2
# ldm add-vdsdev  /dev/dsk/c2t2d0s2 [DISK]@primary-vds0
    Path /dev/dsk/c2t2d0s2 is valid but not accessible on service domain primary

Changes

Although /dev/dsk/cXtXd0 represents the entire disk for a disk with an EFI label, the problem with exporting /dev/dsk/cXtXd0 is that if the disk label is changed from EFI to VTOC (SMI) then this device will disappear. Resulting in various issues manifesting either on the primary or the guest domain.

Cause

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