Release Notes

Work around: Restart the Data manager service to get the updated enumeration.
● JIT-156411: On PowerEdge R7525 when multiple NVMe drives hot plugged while PTR is in progress, observing wrong
enumeration of NVMe drives on OMSA page. This is observing only when Toshiba drive is part of either hot plug operation or
PTR (Prepare to remove).
● JIT-165788 : Predictive failure drives on HBA controller displays as ready state and the predictive failure alert is also not
generated for such drives.
● JIT-167651: The Storage Management enumerates the PCIe Subsystem controller also for 2.5'’ NVMe drives on PERC11
controllers.
● When the auto-configure raid 0 task is performed on PERC 9 controllers, only HDDs that are currently in ready state will
change to RAID 0. There will be no change for SSDs.
● JIT-165719 : A blank page of the Storage Alert Log is displayed when the Storage controller generates several alerts and
cold boot performed together from iDrac.
Workaround : Delete dcsys64.xml and restart the services. The file path where the .xml file is available on systems running
Microsoft Window operating system : C:\Program Files\Dell\SysMgt\omsa\log, on systems running ESXi operating
system : /etc/cim/dell/srvadmin/var/log/openmanage/ and other operating systems : /opt/dell/srvadmin/var/log/
openmanage/.
● JIT-154358: On Command Line Interface for Raid 10,50, and 60 virtual disk that is created with more than 78 physical disk,
fails on external RAID PERC H840 and PERC H830 controllers.
● JIT-169111: On a partial RAID-10 virtual disk creation through Create virtual disk advanced wizard, the drive selection list
displayed may not be similar to the actual physical drive associated with the spans.
● JIT-168698: Read Only Write-Protected drive will not enumerate on systems running ESXi operating systems.
● JIT-169839: When Auto Replace Member On Predictive Failure is enabled, it does not work for SSD.
● JIT-159243: If system restart occurs on running the physical disk offline or online task, the backplane status may display as
critical after restarting even though it is not in critical state.
● JIT-155954: While hot-plug-in mulitple drives of MX5016s physically, wait for each insert alert to avoid the wrong
enumeration.
Workaround: Restart the Data manager service to get the updated enumeration.
● If the controller name is not displayed in the alert message, check the controller information for mapping the controller ID
and controller name.
● JIT-168304: On systems running ESXi 7.x operating system, the Cryptographic erase is performed instead of Sanitize
Cryptographic erase on the Sanitize Capable NVMe drives due to the operating system limitation.
● JIT-172767: If bay id is not available on hot plug event, then Server Administrator physical devices page does not update on
hot plug of physical devices for system having multi vSES and HBA 11 controller.
Workaround: Restart the Server Administrator service.
● JIT-175332: On Storage Management operations may get delayed or may not come up for some time, whenever the
physical disks or enclosures are inserted or mapped or even removed or unmapped from MX5016s.
● JIT-176975: The Server Administrator GUI hangs on performing any storage operations or the storage components
enumeration delay is observed when a failed driver is present on the controller.
● JIT-175456: On all systems running Linux operating systems a warning message displays on GHS assignment on Storage
Management GUI. If the user assigns the GHS, it will crash the dsm_sa_snmpd.
Workaround: Restart the dsm_sa_snmpd service.
● JIT-181410: An incorrect physical device name is intermittently displayed in alert when a physical device is hot-plugged and
other enclosure also has a physical device in the same slot.
Workaround: Restart the Data Manager service.
● JIT-181660: The Data Manager stops responding when a few operations are in progress and iDRAC is reset at the same
time.
Workaround: Restart the Data Manager service.
● JIT-181492: On the Linux or ESXi operating systems, the core dump and Semaphore leak issues are observed, when
performing configuration operations on the FD33xD controller while the enhanced message feature is enabled.
Workaround: Restart the Data Manager service.
● JIT-181903: After upgrading or downgrading the PERC S150 driver firmware, the PERC S150 controller is not displayed in
the Storage tab.
Workaround: Restart the Data Manager service.
19