Version: 5.2.0-17002 - Suggested
---------------------
Enhancements: None

Problem(s) Fixed:
- POST displays different event notification in same line.
- Clear Task progress for individual legs of a RAID 10 clear operation not
  displayed.
- Amber LED not glowing on the copy back drive marked as defunct.
- Kernel Panic occurs when a drive belonging to RAID-50 is removed.
- Kernel Panic occurs when hotpsare drive is removed during copyback.
- Rebuild occurs to wrong leg and array members are swapped in RAID-50 in case of
  two drive failure.
- Pending clear tasks are not triggered automatically even after completion of
  all current tasks.
- Rebuild not getting started when Auto Failover is enabled after a reboot
- Unable to create arrays over drives participated in failed migration operation
  in SRM and arcconf.
- Blink LED observed during NVLogUpdate.
- File system goes to Read-only mode.
- Sensor 75 error on IBM 3650 servers.

Version: 5.2.0-17001 - Suggested
---------------------
Enhancements:
- Added support for defunct state of drives to remain persistent across reboot.
- RAID1 rebuild behavior when Auto Failover is disabled.
- Added support for background tasks to execute in parallel.

Problem(s) Fixed:
- LSI controller fails to boot in presence of Adaptec controller.
- Firmware crashes when we delete a flash copy child.
- Array gets rebuild with different drive types (SAS & SATA).
- RAID Volume is displayed as okay state in BIOS while rebuilding is in progress.
- RAID-6 is rebuilding even after the target drive is initialized.
- The RAID-10 is getting created with incorrect cache setting.
- Rebuilding is triggered automatically in newly created OKAY RAID10 array.
- While copy back is in progress, target drive is allowed to be assigned as a
  hotspare.
- PHY values are displayed in place of slot number for RAID 1E array.
- Copy back fails on the second hotspare drive in RAID-6.
- Migration is displayed as critical migrating even though the array has all
  the members.
- Allowed to assign a physical drive as hotspare even though it contains an
  array.
- Unable to assign a hotspare when a RAID-5 array is in critical state.
- Unable to assign SAS drive as a global hotspare when arrays created with SATA
  drives exist or vice versa.
- Rebuilding is not triggered while secure erase is in progress on any
  physical drive.