Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 25

If the Pre-Upgrade Health Check fails during, Maintenance Mode between the ESXi

Page 25 highlights

Issue ID MDT-417339 MDT-401600 MDT-397046 MDT-346158 MDT-337169 MDT-265301 MDT-170949 MDT-164726 Functional Area Description Workaround/Resolution Install or Upgrade Install or Upgrade Install or Upgrade Install or Upgrade Install or Upgrade Install or Upgrade Install or Upgrade Install or Upgrade Pre-upgrade health checks (PUHC) sometimes fail with a "failed_to_get_free_size" error on a PowerStore 500T cluster even when there is no underlying issue with space on the system. If the healthcheck package was uploaded on the PowerStore cluster before a new appliance was added to the cluster, healthcheck package is unable to run for the newly added appliance. If the ESXi host is rebooted outside of the Maintenance Mode between the ESXi upgrade and the PowerStore X model OS upgrade from 2.0.x.x to 2.1.1.x, the PowerStore X model virtual machine (VM) will not startup automatically, and the PowerStore X model VM will require a manual recovery. If a drive failure occurs and the data path unexpectedly restarts during a failed PowerStore software upgrade, the DRE rebuild feature might become disabled, which prevents the PowerStore software upgrade from being retried. NAS services might fail to start during the initial installation and configuration of PowerStore appliances or during a PowerStore software upgrade. When performing a software upgrade on a PowerStore T model appliance running in Unified mode, the inter-node iSCSI connection might fail when one node is rebooted, which can cause the NAS to panic. Running PowerPath 7.1 and earlier on a Linux host causes an I/O error during the software upgrade of PowerStore OS 1.0 to PowerStore OS 1.0.1. If the Pre-Upgrade Health Check fails during an upgrade from PowerStore OS 1.0 to PowerStore OS 1.0.1 or later, clicking the failed operation link under Recent activities might result in an error because of a localization issue with the event message. Rerun the Pre-upgrade health checks (PUHC). Install the same healthcheck package again. Contact your service provider. Contact your service provider for assistance with reenabling the DRE rebuild feature on the PowerStore cluster. If NAS services fail to start during the initial installation and configuration of PowerStore appliances, try to install NAS again as described in step 4 of the Dell Knowledgebase 000130232: "PowerStore Manager displays 'NAS Installation has failed' when trying to configure PowerStore appliance(s)." If NAS services fail to start during a PowerStore software upgrade, contact your service provider for assistance. Allow NAS-HA to take care of uninterrupted NAS operations during a software upgrade. If data unavailability occurs after the software upgrade is complete, contact your service provider. Apply the next/upcoming PowerPath 7.1 patch, and then run the PowerStore software upgrade to avoid the I/O error. None Known Issues 25

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35

Known Issues
25
Issue ID
Functional Area
Description
Workaround/Resolution
MDT-417339
Install or Upgrade
Pre-upgrade health checks (PUHC)
sometimes fail with a
"failed_to_get_free_size" error on a
PowerStore 500T cluster even when there is
no underlying issue with space on the
system.
Rerun the Pre-upgrade health checks
(PUHC).
MDT-401600
Install or Upgrade
If the healthcheck package was uploaded on
the PowerStore cluster before a new
appliance was added to the cluster,
healthcheck package is unable to run for the
newly added appliance.
Install the same healthcheck package
again.
MDT-397046
Install or Upgrade
If the ESXi host is rebooted outside of the
Maintenance Mode between the ESXi
upgrade and the PowerStore X model OS
upgrade from 2.0.x.x to 2.1.1.x, the
PowerStore X model virtual machine (VM)
will not startup automatically, and the
PowerStore X model VM will require a
manual recovery.
Contact your service provider.
MDT-346158
Install or Upgrade
If a drive failure occurs and the data path
unexpectedly restarts during a failed
PowerStore software upgrade, the DRE
rebuild feature might become disabled,
which prevents the PowerStore software
upgrade from being retried.
Contact your service provider for
assistance with reenabling the DRE rebuild
feature on the PowerStore cluster.
MDT-337169
Install or Upgrade
NAS services might fail to start during the
initial installation and configuration of
PowerStore appliances or during a
PowerStore software upgrade.
If NAS services fail to start during the
initial installation and configuration of
PowerStore appliances, try to install NAS
again as described in step 4 of the Dell
Knowledgebase 000130232: “PowerStore
Manager displays ‘NAS Installation has
failed’ when trying to configure
PowerStore appliance(s).”
If NAS services fail to start during a
PowerStore software upgrade, contact
your service provider for assistance.
MDT-265301
Install or Upgrade
When performing a software upgrade on a
PowerStore T model appliance running in
Unified mode, the inter-node iSCSI
connection might fail when one node is
rebooted, which can cause the NAS to panic.
Allow NAS-HA to take care of
uninterrupted NAS operations during a
software upgrade. If data unavailability
occurs after the software upgrade is
complete, contact your service provider.
MDT-170949
Install or Upgrade
Running PowerPath 7.1 and earlier on a
Linux host causes an I/O error during the
software upgrade of PowerStore OS 1.0 to
PowerStore OS 1.0.1.
Apply the next/upcoming PowerPath 7.1
patch, and then run the PowerStore
software upgrade to avoid the I/O error.
MDT-164726
Install or Upgrade
If the Pre-Upgrade Health Check fails during
an upgrade from PowerStore OS 1.0 to
PowerStore OS 1.0.1 or later, clicking the
failed operation link under Recent activities
might result in an error because of a
localization issue with the event message.
None