Diskgroup containing EFI device doesn't autoimport after reboot when using VxVM version 5.1SP1 and later

book

Article ID: 100005420

calendar_today

Updated On:

Description

Error Message

VxVM disk groups created using EFI LUNs do not get auto-imported on reboot.

If vxconfigd debug level is enabled, debug log may show:

02/22 09:33:33.838: VxVM vxconfigd DEBUG V-5-1-24323 get_efi_slice_parms: devintf_get_full_devt failed with ret=113, devtag=ams_25000_2803

Cause

While determining the disk format of EFI LUNs, stat() system call on the corresponding DMP (Dynamic MultiPathing) devices fail with ENOENT No such file or directory error because the DMP device nodes are not created in the root file system during system boot. This leads to failure in auto-import of disk groups created on EFI LUNs.

Resolution

VxVM code is modified to use OS (Operating System) raw device nodes if stat() fails on DMP device nodes.

The fix is included in the following releases:

VxVM 5.1 SP1 RP1 P1 HF4 (146870-04) 

VxVM 5.1 SP1 RP2

The above patch is available from Veritas SORT website :https://sort.Veritas.com/patch/detail/5516

Workaround

Until the fix is installed, the workaround is to manually import the disk groups using vxdg import

 

Applies To

This issue affects the following versions of Volume Manager on Solaris 9 and 10:

  • VxVM 5.1 SP1
  • VxVM 5.1 SP1 RP1
  • VxVM 5.1 SP1 RP1 P1

Disk groups with EFI labeled LUNs with either sliced or cdsdisk format are affected.

 

Issue/Introduction

VxVM (VERITAS Volume Manager) disk groups created on EFI (Extensible Firmware Interface) LUNs do not get auto-imported during system boot in VxVM version 5.1SP1 and later.

Additional Information

ETrack: 2299670