Vxrail: Upgrade Fails with 'bad Script Return Code: 1' Due to Vmware Vsphere Profile-driven STORAGE Service Issue

Resumen: VxRail upgrade on some releases encounters error code 1. Logs show a PBM error adding a disk, and the vSphere Storage Service reports ‘Healthy with errors’, blocking profile access.

Este artículo se aplica a Este artículo no se aplica a Este artículo no está vinculado a ningún producto específico. No se identifican todas las versiones del producto en este artículo.

Síntomas

During a VxRail upgrade for 4.7.X, 7.0.X, or 8.0.X, there is the following error "Bad script return code: 1"

lcm-web.log:

INFO : Starting adding new disk sdc
INFO : Checkiing whether sdc exists ...
INFO : No sdc disk on VXM, need to perform add.
INFO : Handling VM <VxM Name Here>
INFO : Get VM Storage Profile name VXRAIL-SYSTEM-STORAGE-PROFILE, id <Long string of characters>.
INFO : Vm profileId is <Long string of characters>.
ERROR : Failed to add a new disk: (vodl.fault.SystemError)
{
dynamicType = <unset>
dynamicProperty = (vmodl.DynamicProperty) []
Msg = 'A general system error occurred: PBM error occurred during Pre-ReconfigureCallback: Fault cause: vmodl.fault.SystemError\n;\n'
faultCause = <unset>
faultMessage = (vmodl.LocalizableMessage) []
Reason = 'PBM error occurred during Pre-ReconfigurCallback: Fault cause: vmodl.fault.SystemError\n;\n'
}

When checking the vCenter VAMI, the VMware vSphere Profile-Driven Storage Service shows Health as 'Healthy with errors " (or warnings) and State as 'Started'.
To check the VAMI, login as root to the vCenter VAMI from a web-browser using https://vCenterFQDN:5480 or IPaddress:5480.
click Services.
Software services table with health and status information.

Causa

The VMware vSphere Profile-Driven Storage Service did not start correctly. This is causing issues viewing storage profiles in the vSphere Client.

Resolución

To resolve this issue, follow the steps below to restart the vCenter (and PSC for 6.7 and below):

If the vCenter version is 6.7.X or below:

  1. In the vSphere client, click the vCenter VM.
  2. Find which host the vCenter VM is running on.
  3. Then click the PSC VM.
  4. Migrate the PSC VM to the same ESXi host as the vCenter VM.
  5. Log in as root to the ESXi host from a web browser using https and the ESXi FQDN or Management IP address.
  6. Left-click Virtual Machines.
  7. Left-click the box for the vCenter VM.
  8. Left-click Actions.
  9. Hover over Guest operating system.
  10. Left-click Shut down.
  11. Left-click Virtual Machines.
  12. Left-click the box for the vCenter VM to clear it.
  13. Left-click the box for the PSC VM.
  14. Left-click Actions.
  15. Hover over Guest operating system.
  16. Left-click Restart.
  17. Wait about 3 - 5 minutes.
  18. Left-click the box for the PSC VM to clear it.
  19. Left-click the box for the vCenter VM.
  20. Left-click Actions.
  21. Hover over Guest operating system.
  22. Left-click Restart.


If the vCenter version is 7.0 or newer:

  1. In vSphere, click the vCenter VM.
  2. Find which host the vCenter VM is running on.
  3. Log in as root to the ESXi host from a web browser using https and the ESXi FQDN or Management IP address.
  4. Left-click Virtual Machines.
  5. Left-click the box for the vCenter VM.
  6. Left-click Actions.
  7. Hover over Guest operating system.
  8. Left-click Restart.

Productos afectados

VxRail, VxRail Appliance Series, VxRail Software
Propiedades del artículo
Número del artículo: 000218572
Tipo de artículo: Solution
Última modificación: 14 jul 2026
Versión:  2
Encuentre respuestas a sus preguntas de otros usuarios de Dell
Servicios de soporte
Compruebe si el dispositivo está cubierto por los servicios de soporte.