Dell PowerVault MD 32/36 Series Storage Controller Firmware and NVSRAM firmware version 08.20.24.60

Fixes:
A controller reboot during write with cache disabled, degraded RAID 6 volume group and 512e drives caused data inconsistency
Drive reconstruction on a volume that has not completed Immediate Availability Format can cause data inconsistency
Fast I/O timeouts
Failed volume after STPG command received from host, but prior to volume transfer, causes data loss
Do not allow ownership of a thin volume to be transferred if the underlying thick volume is failed
Disk Pool drive that becomes missing before completing evacuation can cause looping reboot of both controllers
Controller firmware mismatch resulted in cache data loss
An unexpected controller reboot caused data inconsistency in Data Assurance-enabled volume
Unexpected controller reboot during host login
Controller memory leak in manual or ASUP support data collection can eventually result in controller reboot
Controller reboot due to invalid pointer during iSCSI login
Controller reboot due to panic when moving a host between host groups with I/O
Controller reboot after several months of operation with IPv6 stateless autoconfiguration enabled
Unexpected controller reboot due to IOC error on Dense array
Controller reboot on array due to data abort fault
Initiator timeout or many 0x100D errors reporting in event log when using wide volumes and heavy I/O
Controller Reboot on Dense arrays during multiple FC Port Login (PLOGI) for the same ITN port combination
Controller reboot during QLogic switch Online Port Diagnostic test
A controller reboot with thin volumes, snapshots or mirroring caused a controller error and additional reboot
Misbehaving SAS expander causes unexpected controller reboot
VAAI cannot be disabled using SMcli
Controller reboot when iSCSI session is closed while support data is being collected
Memory fault caused controller reboot
Multiple logout of same host connection causes controller reboot
Drive read error can cause controller reboot
Unexpected controller reboot with heavy I/O load and multiple volumes from narrow volume groups
Growing a Snapshot group resulted in multiple controller reboots
Adjustments to BBU Gas Gauge Taper Values
Snapshot group or Asynchronous Mirroring recovery point lost when the repository grows beyond 2TB or multiple thereof
Disk Pool may not be expandable to maximum size if capacity reduction has previously occurred
Spontaneous controller reboot when using iSCSI host interface
Array correctable memory errors may cause unexpected controller reboot
Exceeding 512 ITNs per volume results in multiple controller reboots and lockdown
Both controllers may reboot during a drive firmware update
Perform deep learn cycle on spare BBU installation

Enhancements:
None