联系我们
联系人：刘先生
电话：18612853062
网址：www.raid.com.cn
QQ/Wechat：fjstore
电子邮件：wliu@raid.com.cn
电话：18612853062
网址：www.raid.com.cn
QQ/Wechat：fjstore
电子邮件：wliu@raid.com.cn
-
MegaRAID 93xx win7 2008 2012驱动 2023-02-24 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 9460-8i 重要固件 2023-01-11 ***Important***Is is unlikely any issues will arise by flashing your MegaRAID controller, but always use caution.Make sure that you have a backup of your data on the Virtual drives that are connected to your MegaRAID controller that you are flashing.To flash MegaRAID RAID controllers, you can use LSA, (LSI StorageAuthority) or storcli.storcli /cx download file=filenameNote - /cx is a variable, usually /c0 and can be confirmed with storcli showIf you are flashing PSoC firmware, please use the fullowing command:storcli /cx download psoc file=pblp_catalog.signed.romYou may also save your configuration (Highly recommended) with storcli:Save config:storcli64 /c0 get config file=c0.cfgStore the file off the server.If changes are made to the Virtual drive configuration such as a spare rebuilding, the file needs to be updated. -
MSM linux版本管理软件 2023-07-27 MegaRAID Storage Manager
-
Storcli管理工具 2023-05-22 StorCLI管理工具
Description:===========This is a StorCLI readme file mentioning instructions to use:1. StorCLI on all the supported operating systems.2. StorCLI's JSON Schema files.3. StorCLI's logging feature.Please read before you start using StorCLI executable.Privileges:=========1. StorCLI should be installed / executed with administrative / root / super user privileges.2. Installed/Execution location should have Read/Write/Execute permissions.Windows:========Installation / Execution:1. StorCLI is a executable. Copy-Paste the executable from where you want to execute.Sign verification:command : signtool.exe verify /v /pa <storcli executable name>Notes:1. signtool.exe is required to validate the StorCLI's signature.Windows-ARM============Installation / Execution:1. StorCLI is a executable. Copy-Paste the executable from where you want to execute.Linux:======Installation / Execution :1. Unzip the StorCLI package.2. To install the StorCLI RPM, run the rpm -ivh <StorCLI-x.xx-x.noarch.rpm> command.3. To upgrade the StorCLI RPM, run the rpm -Uvh <StorCLI-x.xx-x.noarch.rpm> command.StorCLI RPM Verification:1. Import the public key to RPM DB. Command : rpm --import <public-key.asc>2. Verify the RPM signature. Command : rpm -Kv <storcli-rpm>3. Install the StorCLI RPM. If imported public key is for the RPM being installed, No warnings should be shown during installation.4. Please adhere to the steps in the above mentioned order only.Linux-ARM:==========Installation / Execution :1. Unzip the StorCLI package.2. To install the StorCLI RPM, run the rpm -ivh <StorCLI-x.xx-x.aarch64.rpm> command.3. To upgrade the StorCLI RPM, run the rpm -Uvh <StorCLI-x.xx-x.aarch64.rpm> command.VMware:======Installation:1. The StorCLI VIB Package can be installed using the following syntax : esxcli software vib install -v=<Filepath of the StorCLI VIB>2. The installed VIB Package can be removed using the following syntax : esxcli software vib remove -n=<VIB Name of StorCLI>3. All the installed VIB Packages can be listed using following command: esxcli software vib listNotes :1. VIB under directory "VMwareOP64" : This binary is for versions from ESXi7.0 and later.FreeBSD:========Installation / Execution:1. Extract the tar archive and execute the StorCLI.Usage policies / Privileges:1. StorCli or StorCli64 application will not function if the user is trying to run it in CSH, the default shell in FreeBSD.2. Please ensure that the user has entered the bash shell by executing the command "bash".EFI:====Installation / Execution:1. From the boot menu, choose EFI Shell.2. Goto the folder containing the StorCLI EFI binaries.3. Execute StorCLI binaries.EFI-ARM:========Installation / Execution:1. From the boot menu, choose EFI Shell.2. Goto the folder containing the StorCLI EFI binaries.3. Execute StorCLI binaries.Ubuntu:=======Installation:1. Debian package can be installed using following command syntax : sudo dpkg -i <.deb package>2. Installed debian package can be verified using following command syntax : dpkg -l | grep -i storcliPowerPC:=======Open Power Big Endian Distribution:-----------------------------------Installation / Execution:1. Unzip the StorCLI package and execute the storcli binary.Open Power Little Endian Distribution:-----------------------------------Installation / Execution:1. Unzip the StorCLI package and execute the storcli binary.2. To install .deb package,Use "dpkg" command.JSON-Schema:=============Installation:1. Create a folder under /home/JSON-SCHEMA-FILES.2. Unzip the JSON-SCHEMA-FILES.zip and copy all the schema files to /home/JSON-SCHEMA-FILES (In any of the operating systems).Command to Schema mapping:1. Please refer to the Schema_mapping_list.xlsx for command to schema mapping.Logging:========1. While executing StorCLI, Logging is enabled by default.2. To Turn-off the logging, Place the storcliconf.ini in the current directory and change the DEBUGLEVEL to 0.3. To change the log level, Place the storcliconf.ini in the current directory and change the DEBUGLEVEL to any desired log level.4. In case of application crash, Place the storcliconf.ini in the current directory to capture logs.
