电话：13911250791
QQ/Wechat：fjstore
电子邮件：wliu@raid.com.cn
-
Braodcom MegaRAID LSAlinux管理软件 2023-11-05 博通94 95系列 linux下的管理软件
-
MegaRAID 93xx win7 2008 2012驱动 2024-07-19 srv_2008_x86- Windows Server 2008 x86srv_2008_x64- Windows Server 2008 x64Win7_x86 - Windows 7 and Windows Server 2008 R2 x86Win7_x64 - Windows 7 and Windows Server Server 2008R2 x64Win8_X86 - Windows 8 and Windows Server 2012 x86Win8_X64 - Windows 8 and Windows Server 2012 x64Win8.1_x86 - Windows 8.1 and Windows Server 2012 R2 x86Win8.1_x64 - Windows 8.1 and Windows Server 2012 R2 x64 -
Broadcom MegaRAID 95xx FW 2023-02-07 增减了PD属性选择功能建议升级**********************************************Broadcom MegaRAID Firmware Release*************************************************************************************************************************************************************************************************PLEASE READ ON ANY OF THESE MEGARAID CONTROLLERS **************************************************************************************************************************************************************************Due to minor Hardware changes on internal clock source, after upgrading to any MR 7.6 (50.6.x-xxxx) or laterpackage, downgrading to MR 7.5 or older (50.5.x-xxx, 50.4.x-xxx, 50.3.x-xxx, 50.2.x-xxx, or 50.1.x-xxxx) is not allowed.Due to changes required to support new features since MR 7.3, after upgrading to any MR 7.3 (50.3.x-xxxx) or laterpackage, downgrading to MR 7.2 or MR 7.1 (50.2.x-xxx or 50.1.x-xxxx) is not allowed.The UNMAP implementation was modified in MR 7.7 release to ensure all SSDs in the VD support UNMAP.When updating a controller that has FW prior to MR 7.7 via online method (i.e., restarting the MR controller alone, not the entire system), VDs created on prior releases where all members are not compliant will generate errors to syslog until the server reboot is performed. After the reboot the VD will NOT be reported as supporting UNMAP.Note: UNMAP is supported on SAS SSDs only; SATA and NVMe will be supported in a future release.****************************************************************************************************************************************************************************************************************************************************======================Supported Controllers:======================MegaRAID SAS 9540-8iMegaRAID SAS 9560-8iMegaRAID SAS 9560-16iMegaRAID SAS 9580-8i8eComponent:=========SAS MegaRAID Firmware Release for MegaRAID ControllersPackage Version: 52.24.0-4763Release Date : Jan 10, 2023MR 7.24 Aero BIOS Package 7.24.01.0_0x07180100_07.24.03.00 (AARCH64/x64) - SignedMR 7.24 UEFI Driver For Ventura and Aero version 0x07180100 (AARCH64/x64) - SignedMR 7.24 UEFI Driver For Ventura and Aero version 0x07180100 (AARCH64/x64) - SignedUEFI BSD Driver - 0x07180100Firmware Defects Fixed (12):Defect ID: DCSG01342893Headline: Controller fault observed while running cache offload cycles with heavy IOsDescription Of Change: Corrected the memory tag parameter passed while freeing the dynamic memory allocated and also changed the mechanism for reading the NVDATA pages for SPDM authenticationIssue Description: Incorrect memory tag parameter passed while freeing the dynamic memory resulted in controller faultDefect ID: DCSG01331157Headline: MR_7.24: firmware fault on 9560 megaraid card upon malformed sense commandDescription Of Change: Modify firmware to validate SENSE SCSI commands and make sure the application is sending buffer required for the SCSI command. If firmware is not provided with adequate buffer thenthe command will be failed back to the applicationIssue Description: When user sends MODE_SENSE_6 command without allocating buffer for the command, firmware is trying to send the sense data to an invalid address and that is causing the crash/fault.Firmware currently does not have a mechanism to validate data length parameter of SCSI commands and cross check if the command is formed right and the application allocated the bufferfor it. In this test case MODE_SENSE_6 command was issued to JBOD drive without a buffer and it is sent to the firmware.Defect ID: DCSG01315519Headline: For un-configured bad foreign drive import and clear option buttons are visible in applicationDescription Of Change: In allowed operation D-command code path, Added the condition check to set the foreignImportNotAllowed bit based on drive state.Issue Description: Foreign import is allowed on un-configured good foreign drive. import not allowed if the drive is bad state.For un-configured bad foreign drive, firmware not setting the foreignImportNotAllowed bit caused this issue in LSA application.Defect ID: DCSG01285247Headline: for JBODs, not setting physical drive state change committed bit in NVRAM.Description Of Change: not setting the physical drive state change committed bit in NVRAM , if the physical drive is JBOD.Issue Description: for JBODs, physical drive state change committed bit is getting set during config clearDefect ID: DCSG01234817Headline: Firmware flash followed by expander reset hit the ExceptionDescription Of Change: modify the log and avoid printing the unavailable symbolIssue Description: - After flashing the controller firmware, recommended step is to reset/reboot controller.- But, User reset the expander. As part of expander reset, Megaraid firmware try to print the unavailable symbol ( function name )- Firmware hit the exception.Defect ID: DCSG01216058Headline: While generating the snapdump, firmware hit the data abort exceptionDescription Of Change: Added the logical drive valid condition check to avoid accessing the invalid logical drive.Issue Description: When driver initiated the kill adaptor, firmware generates the snapdump.While collecting the kill adaptor logs, firmware tries to access the invalid logical drive and hit the data abort exception.Defect ID: DCSG01192071Headline: Assertion failure seen when expander resets and phy on & off executed in loopDescription Of Change: In topology change event path, add a condition check to clear restricted mode only when expander reset in progress and device ID should be persistent.Issue Description: Firmware received the topology change event to temporary device ID.In this code path, tries to clear restricted mode for temporary device ID leads to assertion.Defect ID: DCSG01341519Headline: Storcli hangs with no output after running script cleaning up debug variables.Description Of Change: Clean up mismatched debug variable declarations.Issue Description: After script cleaning up debug variables, StorCLI would hang for operations requiring CMD BLOCK.Defect ID: DCSG01363017Headline: MegaRAID 7.22: Trying to validate DCSG01234817 and seeing similar issue and a hard hangDescription Of Change: A check was added to see if the symbol table is valid.Issue Description: Firmware crashes while trying to access the symbol table for a debug print. Firmware does not recognize that the symbol table has been invalidated, so it accesses seemingly randommemory which leads to the crash.Defect ID: DCSG01365204Headline: While setting WCE(Disk Write Cache)=0 for JBOD; Firmware throws error mode_sense_10 buffer requested 400 but available 4, command failed.Description Of Change: Fixed a Mode Sense 10 Allocation Length check to swap bytes correctly.Issue Description: With Beta Firmware (52.24.0-4679) while setting WCE(Disk Write Cache)=0 for JBOD; throws Firmware logs show error mode_sense_10 buffer requested 400 but available 4, commandfailed!. ===== Refer section Beta Firmware inputs and logsDefect ID: DCSG01349665Headline: Drive stays in UBAD state when doing running drive insertion/removal testDescription Of Change: Update the post insertion done flag only if the drive is present to avoid false set after drive removal.Issue Description: Quick push pull of a drive was creating a race condition between drive insertion and removal state machinescausing the insertion processing to be skipped leaving the drive in UBAD state.Defect ID: DCSG01118222Headline: NVMe response buffer differs from host for get smart health informationDescription Of Change: Made the code changes avoid sending the junk data to applicationIssue Description: In OOB NVME passthru code path, drive return lesser number of data to user sent NVME command. But firmware sends 4096 bytes of data to application which includes junk data.------------------------EnhancementRequest ID: DCSG01368554Headline: Enhance Reconstruction error handling to avoid crash with invalid physical driveDescription Of Change: Add a boundary check condition to fail the reconstruction start command with MFI_STAT_DEVICE_NOT_FOUND whenthe Physical disk number passed is greater than maximum devices allowed.EnhancementRequest ID: DCSG01311360Headline: Firmware: Add a SAS/SATA only profileDescription Of Change: Added downgrade blocking code when on the SAS/SATA only profile. This prevents profile loading issues when downgrading.Installation:=============Use StorCLI to flash the SAS controllers. These tools can be downloaded from the support and downloadsection of www.broadcom.com. -
Broadcom MegaRAID95xx Linux驱动 2024-07-23 Supported Distro list and supported package list
------------------------------------------------------------------------------################################################################################
SuSE:
################################################################################x86_64
SLES 12 SP3
Gold (4.4.73-5) (default)
SLES 12 SP4
Gold (4.12.14-94.41) (default)
SLES 12 SP5
Gold (4.12.14-120) (default)SLES 15 SP3
Gold (5.3.18-57) (default)
SLES 15 SP4
Gold (5.14.21-150400.22) (default)
SLES 15 SP4
Gold (5.14.21-150400.13-rt) (rt)
SLES 15 SP5
Gold (5.14.21-150500.53) (default)
SLES 15 SP5
Gold (5.14.21-150500.11-rt) (rt)
################################################################################
Red Hat:
################################################################################
x86_64RHEL8
Update7 (4.18.0-425.3.1.el8.x86_64) (el8)
Update7 RT (4.18.0-425.3.1.rt7.213.el8.x86_64) (el8)
Update8 (4.18.0-477.10.1.el8_8.x86_64) (el8)
Update8 RT (4.18.0-477.10.1.rt7.274.el8_8.x86_64) (el8)
Update9 (4.18.0-513.5.1.el8_9.x86_64) (el8)
Update9 RT (4.18.0-513.5.1.rt7.307.el8_9.x86_64) (el8)
RHEL9
Update1 (5.14.0-162.6.1.el9_1.x86_64) (el9)
Update1 RT (5.14.0-162.6.1.rt21.168.el9_1.x86_64) (el9)
Update2 (5.14.0-284.11.1.el9_2.x86_64) (el9)
Update2 RT (5.14.0-284.11.1.rt14.296.el9_2.x86_64) (el9)
Update3 (5.14.0-362.8.1.el9_3.x86_64) (el9)
Update3 RT (5.14.0-362.8.1.el9_3.x86_64+rt) (el9)
##############################################################################
FusionOs:
##############################################################################
x86_64
fos22 (4.19.90-2112.8.0.0131.u32.fos22.x86_64)################################################################################
Ubuntu:
################################################################################Single source DKMS Deb driver package will work for below mentioned Ubuntu OS
releases. Please refer driver README for how to use DKMS deb driver package.x86_64
Ubuntu 20.04 LTS (5.4)
Ubuntu 22.04 LTS (5.15)
NOTE:
In case of a kernel upgrade, if megaraid_sas driver DMKS module installation
fails in the upgraded kernel and if it is due to broken DKMS then inbox driver
will be installed in the upgraded kernel.
################################################################################
Citrix:
################################################################################NOTE:
Only RPM support is provided for Citrix's XenServer/Hypervisor OSes.
Citrix has changed the DUD (Driver Update Disk) process in XenServer/Hypervisor
and made it mandatory for ISO images to be signed with GPG keys and
the GPG public key must be present in the base OS installation media.
Due to this DUD support is dropped for XenServer/Hypervisor.
Also, XenServer/Hypervisor OS by default installs out-of-box megaraid_sas driver
rpm while installing the OS. After installing the OS, user can upgrade to
the latest Citrix XenServer/Hypervisor megaraid_sas driver rpm provided as below,# rpm -Uvh avago-megaraid-sas-07.703.01.00_CitrixXen7.1-1.x86_64.rpm
x86_64
Citrix7
Update 1 LTSR (4.4.0+2)x86_64
Citrix8
Base (4.19.0+1)
Citrix8.1
Base (4.19.0+1)
Citrix8.2
Base (4.19.0+1)
-
STORCLI utility for LSI SAS4 Controllers 2024-06-28 STORCLI utility for LSI SAS4 Controllers
EFI, FreeBSD, Windows, Linux, PPC64, ARM,Vmware,Ubuntu
