This release note and the software that accompanies it are copyright (c) 2014, Intel Corporation or its suppliers, and may only be installed and used in accordance with the license that accompanies the software.

This Software is furnished under license and may only be used or copied in accordance with the terms of that license. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. The Software is subject to change without notice, and should not be construed as a commitment by Intel Corporation or its suppliers to market, license, sell or support any product or technology. Unless otherwise provided for in the license under which this Software is provided, the Software is provided AS IS, with no warranties of any kind, express or implied. Except as expressly permitted by the Software license, neither Intel Corporation nor its suppliers assumes any responsibility or liability for any errors or inaccuracies that may appear herein. Except as expressly permitted by the Software license, no part of the Software may be reproduced, stored in a retrieval system, transmitted in any form, or distributed by any means without the express written consent of Intel Corporation.

==========================
Supported RAID Controllers
==========================
This download supports Intel(R) RAID controllers using MegaRAID SAS software stack (RS25SB008, RS25NB008), please verify that this utility has been tested with the RAID card you have chosen to use by checking the drivers web page for your controller at http://www.intel.com/support/.

===================
Package Information
===================
Flash package = v23.6.1-0024

==========
Attention!
==========
Intel recommends to loading Factory Default setting after the firmware upgrade which will not affect data on any existing array. 
To do so:
1. Reboot the system and login to the RAID BIOS Console. 
2. Select the controller and select 'Adapter Properties'->'Next'
3. Set the 'Set Factory Defaults' setting to 'Yes' and submit the change.
4. Reboot the system (the default settings are applied).
5. Re-configure to the desired settings in RAID Web Console2.

==================
Known Restrictions
==================
1) This download does NOT support EFI v1.1 environment. Please use the EFI shell commander which will display the EFI version, 
to identify the EFI version.
2) When 2 or more VDs are created, VD cache settings must be the same.


=======================
Contents on the package 
=======================
The following files are included in this zip:

Name:								Description:
ir3_2208-HADAS_FWPKG-v23.6.1-0024_readme.txt			This file
2208s11p.rom							Firmware binary
update.bat							DOS firmware update batch file
update.nsh							UEFI firmware update batch file
CmdTool2\DOS\*							DOS update utility and support files 
CmdTool2\FreeBSD\*						FreeBSD update utility and support files
CmdTool2\Linux\*						Linux update utility and support files
CmdTool2\Solaris\*						Solaris update utility and support files
CmdTool2\UEFI\*							UEFI update utility and support files
CmdTool2\Windows\*						Windows update utility and support files
License_v2.pdf							License Agreement
COPYING.NEWLIB.txt						License Agreement


==========================
Installation instructions:
==========================

UEFI (EFI 2.0) instructions for updating RAID Firmware:
-----------------
   1. Download and extract all files to a local drive.
   2. Boot the target system to EFI shell. 
   3. Change directory to the local drive and directory containing the flash update files and the firmware image file.
   4. Type "update.nsh" or "efi\cmdtool2 -adpfwflash -f 2208s11p.rom -noverchk -aall"
   5. Wait for the flash to complete. Do NOT reboot the system during the update.

Windows and Linux instructions for updating RAID Firmware:
-----------------
The firmware update may be run from Within Windows or Linux using the appropriate versions of CmdTool2.
  In Windows, unzip the utility into the same directory as the rom file by typing 
      "cmdtool2 -adpfwflash -f 2208s11p.rom -aall". 
  The Linux CmdTool2 by running the rpm and then calling the utility from /opt/MegaRAID/CmdTool2 as 
      "./CmdTool2 -AdpFwFlash -f 2208s11p.rom -aall"

DOS instructions for updating RAID Firmware:
-----------------
   1. Download and extract all files to a local drive.
   2. Boot the target system to DOS. 
   3. Change directory to the local drive and directory containing the flash update files and the firmware image file.
   4. Type "update.bat" or "dos\cmdtool2 -adpfwflash -f 2208s11p.rom -aall"
   5. Wait for the flash to complete. Do NOT reboot the system during the update.

You can also use RAID Web Console 2 to update the RAID firmware. For more detail, please refer to the Intel(R) RAID Software User's Guide.

====================
Product Limitations: 
====================
1.SATA drives are not supported 
2.SAS drives which do not support SCSI-3 persistent reservation 
3.T10/DIF functionality is not supported
4.Dimmer Switch functionality is not supported 
5.FDE/SED drives are not support  
6.SPGIO sideband signal for enclosure management is not supported 
7.Only supports SAS SSD for Cache Cade volumes
8.Supports Cachecade 1.0 only
9.4K Native and 512e HDD Sector HDDs are not supported
10.System/JBOD mode PDs are not supported
11.Drives that are direct-attached to the controller (not via expander device) is not supported
12.Cluster-Active Reconstruction operations (RAID Level Migration or Online Capacity Expansion) is not supported
13.Patrol Read operations that are in progress do not resume after failover
14.Virtual drive erase does not resume after failover
15.Full VD initialization does not resume after failover
16.Firmware-level node incompatibility details are not reported for non-premium features
17.Split-Brain detection logic can cause IO stop during slow failover (double fault) scenarios
18.maintainPdFailHistory is set to disabled/OFF mode by default. Workaround: In order to enable maintainPDFailHistory functionality, both nodes of cluster must be in the pre-boot environment and the setting enabled via pre-boot utility (WebBIOS).
19.Cannot update enclosure/ESM firmware with an active HA cluster (SCGCQ00413571).  Workaround: Shutdown one node for the duration of the ESM firmware update process. Once the update has been completed, the previously shutdown node may be returned to an operational state.

===========
Known Bugs: 
===========
1.SCGCQ00451214 - Continue with the rebuild even after it loses the reservation results in the ddfPd.c (montask)
2.SCGCQ00497037 - Both SAS cables pulled from one node while IOs running in Linux caused all IOs to stop after LDs failed over to peer node
  -Workaround: Restart IO from client (surviving peer node will service IO)
3.SCGCQ00496951 - Hit IO stop on SQLStress test when pulling out power cord on each node 
  -Workaround: See IO stop solution steps in Table 4 of Section 5.4 of the Syncro CS Solution User Guide


=============
Package Details/Fixes/Updates
=============

Package - 23.6.1-0024 (HADAS 1.1 patch2)
 Firmware v3.330.55-3210
  SCGCQ00619188 - Cache policy of Virtual Drives(VD) does not change to Write Through(WT) mode even after detecting a bad supercap

Package - 23.6.1-0020 (HADAS 1.1 patch)
 Firmware v3.330.25-3064
  SCGCQ00524510 - Global hostspare disappears during rebooting both nodes simultaneously
  SCGCQ00530887 - Resolved a number of Persistent Reservation issues
  SCGCQ00557273 - Improved the performance of the LD Persistent Reservation
  SCGCQ00480260 - Enclosure fault LEDs are on following repeated failover of VDs
  SCGCQ00501820 - Shutdown of a node with an OFFLINE VD results in firmware crash
  SCGCQ00553023 - HDD status LED will be lit red after creating and deleting LD but the status is normal via MSM
  SCGCQ00552755 - Incorrect variable type in MR Read/Modify/Write path
  SCGCQ00565007 - Rebuild is not starting from the beginning after manual foreign import
  SCGCQ00518306 - Do not see copyback resume on the failover node
  SCGCQ00549442 - Minor changes needed for handling persistent reservation RELEASE process more robustly
  SCGCQ00552546 - Stale mirror line causes assertion failure.
  SCGCQ00553265 - Miscompare after copy back is finished. (SCGCQ00552646)
  SCGCQ00558261 - HDD status LED will be lit red after creating and deleting LD but the status is normal via MSM
  SCGCQ00574459 - Firmware crash at firmware load time after pinning cache on previous bootup.
  SCGCQ00594076 - Adding and modifying existing messages for cache debugging
  SCGCQ00594078 - Parity is not calculated properly for missing rebuild drive (SCGCQ00575728)
  SCGCQ00531388 - Cluster validation failed in disk arbitration
  SCGCQ00573374 - When user power off the owner node, sometimes the RAID volume will rebuild automatically
  SCGCQ00577062 - A rebuild is occuring while command block is held.
  SCGCQ00593523 - There are write journal orphan entries when importing foreign configuration, thus resulting in firmware to halt
  SCGCQ00504024 - Enclosure fault LEDs are on following repeated failover of VDs
  SCGCQ00559855 - All the HDD drive status change to "Foreign" after rebooting the owner node
  SCGCQ00572392 - Validate the requested blocks for SCSI VERIFY commands on RAID volumes
  SCGCQ00559856 - Improved the performance of the LD Persistent Reservation
  SCGCQ00531386 - Validate disk failover test fails in cluster validation tests
  SCGCQ00580385 - Data corruption after making VD's offline and power pull (SCGCQ00552474)
 BIOS v5.43.00
 WebBIOS v6.1-67-e_67-Rel 
 UEFI_Driver v0x06000500
 HII v04.00.01.00
 PCLI v05.06.03
 NVDATA v2.1210.03-0116
 BootBlockCommon v07.26.26.219
 BootBlock v2.05.00.00-0009
 FCODE v4.12.05.00
 ROMENV v1.08

Package v23.6.1-0018 - (HADAS 1.1)
 Firmware 3.330.05-2793
  SCGCQ00399334 - Disable adding PD FailHistory entries into DDF when maintain PD FailHistory is FALSE
  SCGCQ00471752 - Shared Raid5 virtual drive became foreign configuration when owner node was rebooted.
  SCGCQ00472265 - Cleanup Patrol Read debug prints
  SCGCQ00480316 - Backing out the changes associated to the original defect CQ 475243 because data corruption was found, and will be reworked using CQ 480315.
  SCGCQ00414639 - PL: Certain PhyGroup configurations result in fault 0x7600
  SCGCQ00434111 - Firmware asserts when delete the reconstruction Logical drive (LD)
  SCGCQ00448301 - MSM log events do not show correct message to user
  SCGCQ00454941 - Insert removed pds with maintain PD failhistory enabled and still see PD rebuilding
  SCGCQ00466869 - Changing unconfigured bad drive to unconfigured good did not reflect on the peer node
  SCGCQ00437514 - Update bbu and hw\usb directories to the level of the MR 5.3 Generic Point Release 2 stream.
  SCGCQ00461797 - Firmware hits ASSERT when running I/O from client and move group every five minutes.
  SCGCQ00462466 - The failover is skipped and take the error path when doing single path failover.
  SCGCQ00464015 - Linux MSM owner node doesn't auto update when we initiate planned failover from megamon
  SCGCQ00473171 - Illegible character in boot message when entering safe mode
  SCGCQ00477167 - cache version increment is not working
  SCGCQ00478655 - Firmware hits kill adapter when the user issues online firmware update command to the controller
  SCGCQ00481763 - Firmware faults when Turn OFF/ON Enclosure
  SCGCQ00481766 - Unsupported SAS drive only show in one node
  SCGCQ00443406 - Fimware hits ASSERT when reboot peer node
  SCGCQ00461518 - Target mode error handling print improvements for debugging and minor bug fixes
  SCGCQ00470899 - Some configured drives were not imported during failover when shutting down a node.
  SCGCQ00472716 - In Linux one node can't boot back to OS after shutting down both nodes.
  SCGCQ00480306 - The receiving node (peer) found ACCESS BLOCK after cable pull and reconnect with IOs running on client
  SCGCQ00493602 - MegaRAID firmware hit fault code 0xd05 after failover and Turn OFF/ON enclosure
  SCGCQ00458702 - HA firmware fails to unregister a non-target MegaRAID initiator when it goes into safe mode
  SCGCQ00464506 - PD fail history entries get cleared when CRC errors occur
  SCGCQ00472805 - Unnecessary rebuild initiated during a Logical Drive(LD) Failover creating dummy foreign configurations.
  SCGCQ00482273 - With PD Fail History enabled, unconfigured bad drives that have been marked unconfigured good may be remarked unconfigured bad
  SCGCQ00485398 - Pinned cache reported only on one node after reboot (expected behavour is both nodes)
  SCGCQ00417694 - Syncro-CS controller cannot set disableHII to 0 using MFC command in megamon
  SCGCQ00436992 - In Linux - After initiating a Planned Failover from Debugger, found foreign configuration
  SCGCQ00440238 - HII Browser did not update after pull online drives
  SCGCQ00447877 - Firmware hits an ASSERT when internal utility is used to crash one node
  SCGCQ00449882 - Boot target Id is inconsistent across Nvram and Disk Data Format (DDF)
  SCGCQ00461497 - During the recovery of IO Shipped request the device driver is sending firmware a OCR(online controller reset)
  SCGCQ00464888 - Internal firmware error encountered if a virtual disk (VD) goes to offline state during failover
  SCGCQ00465556 - Firmware faults when updating enclosure firmware using StorCli .
  SCGCQ00468573 - Can't install OS RHEL6.4 x64b with a non-shared volume on SyncroCS
  SCGCQ00480315 - ACCESS BLOCK after a peer discovery generated planned failover due to cache version mismatch
  SCGCQ00399639 - Code Cleanup - Peer Arb not granted during Unplanned Failover
  SCGCQ00426927 - Data Miscompare found while running i/o overnight with degraded virtual drives
  SCGCQ00454106 - Write-policy of non-shared volume changes to write-through by failover
  SCGCQ00462385 - Firmware messages keep rolling when a node enters safe mode.
  SCGCQ00464018 - Pinned cache is reported when booting a server while the other server is performing reconstruction operations
  SCGCQ00480307 - Backing out the changes associated to the original defect CQ 470424 because data corruption was found, and will be reworked using CQ 480306.
  SCGCQ00484772 - I/O stop when pull out power cord of the owner node
  SCGCQ00398236 - Firmware faults when releasing peer block
  SCGCQ00413693 - Enclosure Hotplug not releasing drive reservations making drives to appear only on one node
  SCGCQ00425872 - Firmware faults when shutting down one node
  SCGCQ00425978 - Firmware faults when starting reconstruction
  SCGCQ00435817 - Firmware asserts when the disk is owned by peer
  SCGCQ00457774 - Misleading Fail/Offline Virtual Disk (VD) alert from MSM when reboot a node followed by logging into Windows
  SCGCQ00466131 - Inconsistent reporting of pinned cache
  SCGCQ00466221 - Global Hot Spare is marked as UNCONFIG_BAD when node reboots and gets failed over to peer
  SCGCQ00469069 - Foreign configuration present on the owner node even after clearing the foreign configuration on the peer node
  SCGCQ00477151 - Rebuilding did not resume where it left off on the peer when the (owner) failover happened
  SCGCQ00477239 - Firmware faults when reboot with unsupport drive and SATA drive
  SCGCQ00483905 - I/O's fail and VD becomes failed during planned failover of owner node w/ SMB I/O
  SCGCQ00493177 - HA: Fix compiler warnings
  SCGCQ00412114 - Medium Error Handling for Shipped I/Os
  SCGCQ00413632 - Syncro CS 1.1 Boot Device Selection
  SCGCQ00414605 - Performance Tuning - Implement a new Region Lock message for target mode Ios
  SCGCQ00278370 - Clean up of dead code
  SCGCQ00397077 - Cluster Active PD firmware flash
  SCGCQ00413633 - Maintain PD Fail History Across Nodes
  SCGCQ00439525 - Implemented SCSI3 PR Preempt and Abort Service Action
  SCGCQ00372093 - Refactor the IO shipping path
  SCGCQ00472732 - Change the Exclusive Virtual Disk(VD) behavior in the shutdown handling
  SCGCQ00297516 - Add a duplicate exception print to the TTY log to aid debug of host captures
  SCGCQ00397129 - Implement shutdown handling
  SCGCQ00436439 - Region Lock code sync up from PL code base 12.26.05.00
  SCGCQ00383700 - Clear Pinned Cache On Both Nodes
  SCGCQ00407152 - Add Target Mode Error Injection capability.
  SCGCQ00447495 - PL binary 12.26.06.00 update
  SCGCQ00451109 - Debug variables for validating the shutdown handling process
  SCGCQ00410849 - MSM can not clear pinned cache list on the peer node.
  SCGCQ00411677 - Controller crashed during boot
  SCGCQ00421666 - If a rebuild is in paused state, and the Ld goes offline, the Pd remains in rebuild state.
  SCGCQ00421708 - Imported drive becomes unconfigured good when secure VD erase is running.
  SCGCQ00421749 - Memory test does not execute when performing FW diagnostics.
  SCGCQ00422021 - 3TB Hitachi HDD failed in immunity test (Electrostatic Noise test)
  SCGCQ00422025 - T-bolt firmware : makes unconfigured bad (foreign) to unconfigured bad on reboot.
  SCGCQ00424999 - Fault during a firmware failover
  SCGCQ00454856 - R/W buffer have different behavior between HBA and MegaRAID
  SCGCQ00411651 - found "Wait for Cache sync complete" kept coming when trying to reboot/shutdown it. Othenode is OFF
  SCGCQ00413286 - Hit MonTask: line 719 in file ../../raid/cachePreserve.c
  SCGCQ00421652 - Controller reports wrong elapsed time while reconstructing after OCR.
  SCGCQ00421757 - Set Drive State to JBOD in MR9266/MR2208 will cause Drive Fault LED light on
  SCGCQ00422022 - Patrol Read causes data integrity issue if the LDBBM is fulll
  SCGCQ00461456 - I/O fail while format partition.
  SCGCQ00467957 - Enhancement to decrease the duration of the slow failover functionality
  SCGCQ00478658 - On VMWare Data miscomparison found after 1st controller Failover
  SCGCQ00414648 - Assertion failure with no valid pool for LD being failed over
  SCGCQ00422036 - BIOS does not display accurate message when multiple enclosures are attached to the controller
  SCGCQ00422045 - A good SuperCap could be prematurely marked as failed.
  SCGCQ00424806 - Don't clear Recon LD PDs.
  SCGCQ00424882 - VD becomes WT with a good & new Super Cap on boot
  SCGCQ00435866 - Not able to boot operating system because the boot drive is in access block state
  SCGCQ00461454 - FW hitting Kill_Adapter mon_task after OCR is recovered/ reboot.
  SCGCQ00464977 - Out of resource conditions may lead to discovery non completion
  SCGCQ00481555 - Disconnect SCap during Shutdown/Hibernate only if pinned cache is not present
  SCGCQ00418683 - The reliability and error recovery of the SuperCap firmware was improved.
  SCGCQ00422019 - Subsequent drives are dropped when all drives in the stagger spin up drives fails on boot sequence.
  SCGCQ00422053 - A SuperCap could be shown as prematurely failed if a reboot occurred immediately after a learn cycle completed.
  SCGCQ00424856 - Serious performance issue found in firmware
  SCGCQ00413288 - Firmware crashed while booting with direct attached drives
  SCGCQ00421696 - When BGI is aborted and restarted, elapsed time is not reset
  SCGCQ00421719 - Port Hot spare disk does not adhere the disk cache policy (LSIP200229786).
  SCGCQ00422031 - Set RDM_FLAGS_FUA_REQ in immediate IO pah in rebuilding drive case.
  SCGCQ00435864 - Firmware crash during unplanned failover when there is pinned cache.
  SCGCQ00466797 - TFM error handling : Cache policy change for WB to WT if supercap is faulty
  SCGCQ00481560 - Write policy changed from WT to WB when the battery/Supercap is declared as bad
  SCGCQ00483981 - I/O stopped after one controller stuck in "invalid peerarb from devH xx sasAddr ffffffffffffffff" loop and 2nd Ctrl in montas
  SCGCQ00422024 - Hot Spare lost after FW update
  SCGCQ00423164 - Upon Online Controller Reset (OCR), Recon Ghost LD needs to be created before WJ processing
  SCGCQ00443244 - Firmware crash when pulling a drive from each span of a raid 50 logical drive
  SCGCQ00458624 - DDR3 init failure issue on OEM controller while performing cache offload.
  SCGCQ00466269 - Shutdown entered idle loop with pending virtual drive(VD) deletion
  SCGCQ00469561 - Firmware doesn't allow applications to create Virtual Drives (VDs)
  SCGCQ00411652 - Firmware Hit MonTask: line 1997 in file ../../raid/cache.c
  SCGCQ00413674 - CS1.0 FW hit SQLIO data corruption
  SCGCQ00415932 - MSM halt when import foreign config after enclosure off/on
  SCGCQ00421751 - Not able to flash both 9265-8i and 9285-8e card with 5.3 patch 1 firmware.However, it is ok on 9266-8i.
  SCGCQ00421763 - RAID Member disks state changed to (foreign) online and still can access.
  SCGCQ00422051 - VD Degraded after reconstruction of R5
  SCGCQ00422055 - (multiple) Megacli64 error in deadlock state
  SCGCQ00423931 - If a correctable ECC error occurred during a cache offload, the CPU would crash, resulting in a data loss
  SCGCQ00424676 - Firmware faults on VD erase on Raid 1(R1)
  SCGCQ00442682 - Encountered firmware fatal error while reading Disk Data Format (DDF) record due to not holding SCSI-3 persistent device reservation on device
  SCGCQ00411676 - Firmware Crashed during node reboot
  SCGCQ00419379 - FW goes to montask at cache offload.
  SCGCQ00421707 - Firmware reports device initialization completion status to be greater than 100% at startup
  SCGCQ00421745 - Pulling cable when maintainpdfailhistory=1 create wrong state in arrays.
  SCGCQ00421750 - If a double bit error occurs during memory initialization on an OEM controller, GPIO 19 will now be asserted.
  SCGCQ00421753 - OCR is seen after setting to factory default and reboot
  SCGCQ00421759 - The SuperCap will now remain in the failed state when its capacitance falls below the minimum or its resistance exceeds the maximum
  SCGCQ00421762 - 2208 ROMB see 0 Capacitance
  SCGCQ00422032 - Controller does not come up while a PD Erase is in progress_Debug Firmware
  SCGCQ00422049 - Offline drive becomes automatically online during Raid Level Migration
  SCGCQ00450651 - 9260-8i(SAS2108) hitting OOB SRAT timeout for a long time causing OOB commands to fail
  SCGCQ00461430 - DDF read sections might fail.
  SCGCQ00467326 - System hang on boot when a global hot spare is configured
  SCGCQ00467327 - Failover takes more time than normal when node pull from Cib hardware
  SCGCQ00471848 - Firmware hits kill adapter when pulling out the blade while I/O is running from client on CiB system.
  SCGCQ00476251 - Firmware is hitting kill adapter on both servers when the two Sas cables are pulled from the LD owner node with I/O running from the client.
 BIOS 5.43.00
  SCGCQ00408767 - OpROM not getting relocated to runtime segment if the segment address is 0xC0000
  SCGCQ00395750 - BIOS build date field is empty and build date is displayed as BIOS build time in SLT.
  SCGCQ00397476 - BIOS: Provide scratch segment and populate info to assist Ctrl R to load latest host
  SCGCQ00403158 - Update OEM Sub System Device Ids and the corresponding BBS strings.
  SCGCQ00459907 - Boot Device Selection in multi boot configuratio
 WebBIOS 6.1-67-e_67-Rel 
  SCGCQ00330068 - Creating a non shared VD become shared VD in WebBIOS.
  SCGCQ00365948 - HAMR: Not Able To See/Display The Last Drive On The WebBios
  SCGCQ00466265 - HA WEB BIOS give a blank screen when discard pinned cache from peer node
  SCGCQ00308396 - HAMR-- WEB BIOS Hang when Create Automatic Configuration With No Redundancy
  SCGCQ00319238 - HAMR WebBIOS release with newer load address.
  SCGCQ00350319 - HAMR: Wrong Enclosue ID Shows Between Node 1 & Node 2
  SCGCQ00324174 - "Boot error handling" options are not correct in WebBIOS.
  SCGCQ00314460 - HAMR_Code_Port
  SCGCQ00308399 - HAMR WEB BIOS : The Share Virtual Drive is uncheck when Create Auto-Config With Redundancy Arrays
  SCGCQ00380877 - Revoking Set Boot Drive radio button from all the VDs which are not candidate boot VD.
  SCGCQ00435804 - WebBios Didn't Display The PinnedCacheList On all offlined virtual drives with preserved
  SCGCQ00322616 - HA-DAS: Applications need to handle the new LD_ACCESS_STATUS (MR_LD_ACCESS_STATUS_PEER_UNAVAILABLE)
  SCGCQ00322614 - HA-DAS: HA terminologies used in all the applications need to be modified
  SCGCQ00322613 - An appropriate error message should be prompted when the user assigns a DHSP to multiple arrays belong to different LDs
  SCGCQ00364498 - Add Support for OEM HA-DAS product
  SCGCQ00340795 - Application needs to check for HA-DAS feature support.
  SCGCQ00345326 - Not able to associate multiple VDs in a cache pool.
  SCGCQ00368009 - Wrong spanned drive group size is displayed by Web bios(Ctrl-H).
  SCGCQ00310305 - WebBIOS displays SSD association screen for Secured and Protected VDs (Virtual drive table is empty).
  SCGCQ00309608 - WebBIOS should not allow RLM for protected VDs with non-PI drives.
  SCGCQ00310292 - Remaining capacity is coming 0 from FW.
  SCGCQ00310293 - Battery Firmware vesion(MR_BBU_DESIGN_INFO.moduleVersion) is coming as Null
  SCGCQ00310296 - Preboot apps have to change load address change because of FW changes.
  SCGCQ00449148 - In WebBIOS, if BGI is suspended the vd progress info page shows it as CC progress until it is resumed.
  SCGCQ00310306 - WebBIOS does not show "Day" for Next learn cycle time in battery page. And issue with safe mode.
  SCGCQ00310294 - WebBIOS does not warn user before importing PI enabled VD on PI disabled controller.
  SCGCQ00310295 - WebBIOS reports incorrect number of foreign configs during "Scan Devices"
 UEFI_Driver 0x06000500
  SCGCQ00378953 - HII not showing up + other enhancement for driver health formset
  SCGCQ00413986 - HII app doesnt appear when there is critical message and when platform uses SetOptions
  SCGCQ00408333 - UEFI: Critical boot message formatting issue
  SCGCQ00384884 - Customize health formset + few other issues
  SCGCQ00395190 - When trying to create an R6/R5, I am unable to create though there are 3 SAS unconfigured good avail
  SCGCQ00396051 - UEFI Driver should not display finite boot messages
  SCGCQ00408094 - OEM system with a critical message does not enter EFI preboot config utility
  SCGCQ00395996 - Parse Boot message and remove \r\n at the beginning and replace \n with \r in other parts
  SCGCQ00331573 - Remove dependency on deprecated Driver Configuration2 protocol from UEFI Driver
 HII 04.00.01.00
  SCGCQ00431622 - Navigation issue from Enable Drive Security form
  SCGCQ00397100 - Add HA support to HII
 NVDATA 2.1210.03-0116
  SCGCQ00472354 - Change default setting of maintainPdFailHistory
  SCGCQ00503607 - Change default setting of Maintain Physical Device (Pd) Fail History to 0 for all OEM controllers
 PCLI 05.06.03
 BootBlock 2.05.00.00-0009
 BootBlockCommon 07.26.26.219
 ROMENV 1.08

Package v23.6.0-0086 - Initial release (HADAS 1.0)
 Firmware 3.170.05-2458
 BIOS 5.41.00
 HII 03.02.03.00
 PCLI 05.06-03
 WebBIOS 6.1-63-e_63-Rel
 NVDATA 2.1210.03-0112
 BootBlock 2.05.00.00-0009
 Common Bootblock 07.26.13.219


*Third-party trademarks are the property of their respective owners.

