电话:18211188378
QQ/Wechat:fjstore
电子邮件:wliu@raid.com.cn
-
MegaRAID 94xx 95xx Win Driver 2025-07-23 this Document explains the Structure of Released Package for MegaRAID Windows Drivers.Starting MR 7.11, new folder naming conventions have been provided in the same conventions as Microsoft releases.Starting MR 7.14, Support for 32-bit OS architecture has been dropped and support for SAC release has been limited to N(latest SAC release).Please refer to updated OS policy for more details.Controllers Supported : This Driver supports SAS3.5 MegaRAID 94xx (Ventura Family) and MegaRAID 95xx (Aero Family) of Controllers only.The following description helps to select proper driver for each release of Windows Operating Systems:Win2022_Server_LTSC_x64 - It should be used for Windows Server 2022 x64.Win11_22H2_Client_x64 - It should be used for Windows 11 22H2 Client X64.Win11_23H2_Client_x64 - It should be used for Windows 11 23H2 Client X64.Win2025_x64 - It should be used for Windows Server 2025 X64.Win11_24H2_X64 - It should be used for Windows 11 24H2 Client X64. -
MR Windows Driver - 06.714.18.00 2025-07-03 *******************************************
Broadcom MegaRAID Windows Drivers
*******************************************
Release Date: 12/17/18
======================Supported Controllers
==================
MegaRAID SAS 9460-16i
MegaRAID SAS 9460-8i
MegaRAID SAS 9480-8i8e
MegaRAID SAS 9440-8i
MegaRAID SAS 9380-8i8e
MegaRAID SAS 9380-4i4e
MegaRAID SAS 9380-8e
MegaRAID SAS 9380-8i
MegaRAID SAS 9361-24i
MegaRAID SAS 9361-16i
MegaRAID SAS 9361-8i
MegaRAID SAS 9361-4i
MegaRAID SAS 9341-8i
MegaRAID SAS 9341-4i
MegaRAID SAS 9380-8e
MegaRAID SAS 9380-4i4e
MegaRAID SAS 9270-8i
MegaRAID SAS 9271-4i
MegaRAID SAS 9271-8i
MegaRAID SAS 9271-8iCC
Syncro CS 9271-8i
MegaRAID SAS 9286-8e
MegaRAID SAS 9286CV-8e
MegaRAID SAS 9286CV-8eCC
Syncro CS 9286-8e
MegaRAID SAS 9265-8i
MegaRAID SAS 9285-8e
MegaRAID SAS 9240-4i
MegaRAID SAS 9240-8i
MegaRAID SAS 9260-4i
MegaRAID SAS 9260CV-4i
MegaRAID SAS 9260-8i
MegaRAID SAS 9260CV-8i
MegaRAID SAS 9260DE-8i
MegaRAID SAS 9261-8i
MegaRAID SAS 9280-4i4e
MegaRAID SAS 9280-8e
MegaRAID SAS 9280DE-8e
MegaRAID SAS 9280-24i4e
MegaRAID SAS 9280-16i4e
MegaRAID SAS 9260-16i
MegaRAID SAS 9266-4i
MegaRAID SAS 9266-8i
MegaRAID SAS 9250-4i
MegaRAID SAS 9285CV-8e
For older MegaRAID controllers including 1068 legacy controllers, use the Windows inbox driver.
Component:
==========
SAS MegaRAID Signed Drivers for Windows
Release Date: 12/17/18
Version Numbers:
================
Current Version 6.714.18.00
Previous Version 6.714.05.00Contents:
=========This package contains signed drivers for the following Windows versions:
Below is described which driver to be used for which OS:
Win8_X86 - Windows 8 and Windows Server 2012 x86
Win8_X64 - Windows 8 and Windows Server 2012 x64
Win8.1_x86 - Windows 8.1 and Windows Server 2012 R2 x86
Win8.1_x64 - Windows 8.1 and Windows Server 2012 R2 x64
Win10_x86 - Windows 10, Windows Server 2016 x86, Windows Server 2019 RS5
Win10_x64 - Windows 10, Windows Server 2016 x64, Windows Server 2019 RS5Note : Windows XP X86 OS version is not supported as it does not support Storport driver required for MegaRAID Drivers.
Note: Windows Server 2003 should work with the Windows Server 2008 Drivers but is no longer tested.
-
Braodcom MegaRAID LSAlinux管理软件 2023-11-05 博通94 95系列 linux下的管理软件
-
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. -
Marvell QLoigc管理软件 2025-08-11 Marvell Qlogic HBA windows 平台管理软件

