PowerPath: ID 939976 local0.error MPAPI: Error: Internal error occurred.

Summary: The error message occurs at a Solaris host boot - MPAPI: Error: Internal error occurred

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

Error message: PowerPath: [ID 939976 local0.error] MPAPI: Error: Internal error occured.

The error message comes up at a boot:

# egrep 'MPAPI|MSunOS Release 5.10 Version Generic' messages.[0-2]
messages.0:Feb 20 22:15:24 PBGSVH01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_150400-26 64-bit
messages.0:Feb 20 22:16:06 PBGSVH01 PowerPath: [ID 939976 local0.error] MPAPI: Error: Internal error occured.
messages.0:Feb 20 22:58:30 PBGSVH01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_150400-26 64-bit
messages.0:Feb 20 22:59:13 PBGSVH01 PowerPath: [ID 939976 local0.error] MPAPI: Error: Internal error occured.
messages.1:Jan 19 03:11:16 PBGSVH01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_150400-26 64-bit
messages.1:Jan 19 03:12:17 PBGSVH01 PowerPath: [ID 939976 local0.error] MPAPI: Error: Internal error occured.
messages.2:Dec 18 11:01:53 PBGSVH01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_150400-26 64-bit
messages.2:Dec 18 11:02:36 PBGSVH01 PowerPath: [ID 939976 local0.error] MPAPI: Error: Internal error occured.
messages.2:Jan 19 02:25:09 PBGSVH01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_150400-26 64-bit
messages.2:Jan 19 02:26:10 PBGSVH01 PowerPath: [ID 939976 local0.error] MPAPI: Error: Internal error occured.

Cause

For powermt load boot command, boot option is not being set which would otherwise have ensured that the configuration file updates are not attempted during early boot.
 
/lib/svc/method/powerstartup
#!/sbin/sh
. /lib/svc/share/smf_include.sh
if [ -f /etc/powermt_custom.xml -o -f /etc/powermt.custom ]
then
    /etc/powermt load boot
else
    /etc/powermt config boot
fi
case "$?" in
  0) exit 0 ;;
  *) exit $SMF_EXIT_ERR_CONFIG ;;
esac
  1. The issue is only seen with a root file system that is on UFS (not on ZFS).
  2.  powerstartup service is run during early boot which runs powermt load boot that results into this error.
  3. UFS root file system during early boot is Read Only and during this phase, if powermt load boot tries to update the /etc/emc/mpaa.lams file while loading the previous state, the update fails.
  4. For ZFS root file system, during early boot when powerstartup service runs, the file system is read/write and error is not thrown.
  5. The failure of update of /etc/emc/mpaa.lams file results into the MPAPI error but rest of the process continues without any issues.
  6. Later into the boot stage, when powerconfig service runs, that too does powermt load first and since the file system is read/write by then, the configuration files are updated appropriately.
 

Resolution

This error is harmless and does not indicate anything wrong with the driver state and can be ignored.

  • Sanity of the system is good once it is up and running.
  • All the powermt commands are working fine.
  • No issues seen with the configuration files once the system is booted.
Article Properties
Article Number: 000171334
Article Type: Solution
Last Modified: 22 Oct 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.