Error Message

WARNING: unable to load module: vxfs: Invalid argument
vxportal: unable to resolve dependency 'fs/vxfs': cannot load module

/usr/kernel/drv/sparcv9/fdd: Shdr[13].rela.data: relocation[34] error: R_SPARC_64: symbol not found: vx_odm_resilver
/usr/kernel/drv/sparcv9/fdd: Shdr[13].rela.data: relocation[35] error: R_SPARC_64: symbol not found: vx_odm_link
/usr/kernel/drv/sparcv9/fdd: Shdr[13].rela.data: relocation[36] error: R_SPARC_64: symbol not found: vx_odm_resize
/usr/kernel/drv/sparcv9/fdd: Shdr[13].rela.data: relocation[37] error: R_SPARC_64: symbol not found: vx_odm_stat
WARNING: unable to load module: fdd: Invalid argument

Configuring devices.
devfsadm: dlopen failed: /usr/lib/devfsadm/linkmod/VRTS_vxvm_link.so: ld.so.1: devfsadm: /usr/lib/devfsadm/linkmod/VRTS_vxvm_link.so: wrong ELF class: ELFCLASS32

Apr 24 10:45:07 svc.startd[13]: svc:/system/filesystem/local:default: Method "/lib/svc/method/fs-local" failed with exit status 95.
Apr 24 10:45:07 svc.startd[13]: system/filesystem/local:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details

For Solaris 11.4 support, Veritas started shipping two kernel modules in a Solaris package. So, during the first boot (after upgrading OS from Solaris 11.3 to 11.4 ) the modules present in /kernel/drv/sparcv9 are of Solaris 11.3 and the systems attempts to install Solaris 11.3 modules on Solaris 11.4, but that fails and generates the above mentioned errors.  When the system proceeds with boot, there is a code to replace 11.3 modules with 11.4 in appropriate driver directories (before the machine comes up). 

Here in this situation, Local vxfs mounts prevent the system from booting further and causing the reported errors. 

Note: Check svcs -xv to see which service gets stuck. If it is showing filesystem service. Comment out any VxFS file systems and continue to boot further
 

A supported hotfix has been made available for this issue for Infoscale 7.4.1. Please contact Veritas Technical Support to obtain this fix.

A hotfix is now available for this issue in the current version(s) of the product(s) mentioned. Refer to the Hotfix link under Related Articles to obtain the hotfix needed to resolve the issue.