Скачать драйвер для Intel 6GB SAS Hardware RAID Firmware 12.14.0-0185

Fixes:
- MegaRAID iMR FW with "enableReducedFeatureSet=1" issue
- After the newest image is installed, servers often will not boot.
- FW sending wrong configuration data during boot msg pending state
- Not able to change the properties of MSM.
- Upgrading from Software RAID to 9260-8i causes Alarm to sound
- Error in MR_DCMD_CTRL_EVENT_COUNT/SL_DIR_READ
- MSM log warning: Controller booted in headless mode with errors
- Data Corruption with R5 cachedIO mode
- Sequential Read performance is less on CacheCade associated LD's.
- Montask occurs when running host i/o and parallel OOB command
- Generic point release MR4.9 :VPD output of lspci vvxxx showing [RV] Reserved: checksum bad, 86 byte(s) reserved
- When pinned cache present VD property not changing from WB to WT.
- 9260-8i(SAS2108) hitting OOB SRAT timeout for a long time causing OOB commands to fail
- Check-in Pl version 5.0.42.0 -- Improve STP connection timing behavior with idle connections
- Checking-in new PL version :05.00.41
- To check-in new PL version 5.00.40.00
- Discard preserved cache takes excessive time or hangs
- Controller always gives an event MR_EVT_CTRL_BOOT_HEADLESS_MODE_HAD_ERRORS if controller is set in HSM mode.
- Montask occurs when running host i/o and parallel OOB command
- PDs go online without VD created & App doesn't allow any VD creation on passing a wrong parameter in Spanned VD.
- To Disable the logging of event MR_EVT_PD_EMERGENCY_SPARE_COMMISSIONED_REMINDER
- EEprom CRC error is detected when WebBIOS is running
- STP Passthrough Support through OOB
- FW is not declaring the battery bad if learn cycles fail continuously
- Validate the requested blocks for SCSI VERIFY commands on RAID volumes
- See 9261-8i emergency spare being commissioned
- Data Miscompare found while running I/O overnight with degraded virtual drives
- FW halts when you have pinned cahce and remove VD form the configuration.
- FW halts when you have pinned cahce and remove VD form the configuration.
- Card Running iMR Machine Checks when Requesting Host Memory
- Minimum Capacity needed for relearn is incorrect in 2208 MR FW
- Incorrect variable type in MR Read/Modify/Write path
- RM_SataBBMTotalCount always return 0
- FW Automatically detect backplane SGPIO type to set the driveactivityLED parameter
- Setting the ASO key with storcli 1.02.08 (MegaCli 8.07.06) fails with an error code 3 on Windows or Linux if the MB BIOS PCI
- Discard preserved cache takes excessive time or hangs
- During rebuild on PRL11 CacheCade VD and rebuild on RAID6 Source VD IO integrity error is seen.
- IO integrity error seen after Source VD associated with CacheCade VD is forcibly unblocked
- LDBBM on RAID6 not eligible
- PCIe core has received a PCIe request that it does not support
- Firmware returns asc value as 0 when failing IOs with medium errors
- Firmware hits Montask when drive is pulled after changing the volume property from read ahead to no read ahead.
- Faulty protocol used for changing the Disk Write Cache Policy
- BU SOH bad message be posted after exhauting retry attempts. Stop monitoring battery once SOH bad is declared
- RHEL6.4 Kernel crash after reboot
- Medium error correction event is not logged during CC
- Firmware Version 2.130.383-2912 is hitting MonTask at line 1209 in file ../../raid/1078dma.c
- Source VD gets blocked on OCR after one PD removal from R0 WB CCVD and reuse of that PD in creating another CCVD.
- Data Corruption seen when IOs are in progress and cachecade PD is marked as missing and reused to create another SSC VD.
- Sequential Read performance is less on CacheCade associated LD's.
- When a Cachecade PD marked as missing is reused to make Cachecade VD IO integrity error is observed.
- Saved Release Note DataSLIB returning bad data as good data after host reboots
- (Vital Product Data) needs to identify PCB hardware level
- Validate the requested blocks for SCSI VERIFY commands on RAID volumes
- If a BOOT Passphrase is enabled with SafeStor "MegaCli adpbios dsply a0" will display "BIOS will Stop on error" even if any other mode is set.
- Update the events
- Firmware is not updating recovery timer as intended
- "chip paused" causes high service time on all drives
- 9260-8i(SAS2108) hitting OOB SRAT timeout for a long time causing OOB commands to fail
- Raid configuration loss after reboot - PDs in POWERSAVE
- Code Review: Call DDF_discardInvalidPds only if DS3 is enabled
- Upgrading from Software RAID to 9260-8i causes Alarm to sound
- System black screen during S1 Sleep test
- UEFI driver issue with platforms when user having 2TB or 4TB VD
- Platfrom has UEFI hang when SATA is connected
- Disable Debug print in UEFI Driver
- Block IO tests from SCT IHV test suite failed
- ATA PT: Follow UEFI Spec on interpreting In and Out Transfer Length that upper layer sends
- Obtain the Physical Slot number from the PCI Bridge to which the Controller is connected.
- Memory allocation: Allocate only two 64k

Versions:
- Medusa_Expander SAS2XFW-25.05.04.00_MFGIMG-25.05.04.00
- NVDATA 2.09.03-0046
- OEM specific change only
- BootBlockCommon 09.250.01.219
- BootBlock 2.02.00.00-0000
- ROMENV 1.08
- WebBIOS 6.0-52-e_48-Rel
- PCLI 4.04.20
- UEFI_Driver 0x05290000
- FCODE 4.14.05.00
- BIOS 3.29.00
- Hii 1.38.00

This download is valid for the product(s) listed below.
- Intel Integrated RAID Module RMS2MH080
- Intel RAID Controller RS2BL040
- Intel RAID Controller RS2BL080
- Intel RAID Controller RS2MB044
- Intel RAID Controller RS2PI008
- Intel RAID Controller RS2SG244
- Intel RAID Controller RS2VB040
- Intel RAID Controller RS2VB080
- Intel RAID Controller RS2WG160
- Intel RAID Controller RT3WB080


It is highly recommended to always use the most recent driver version available.

Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games.

Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.

Примечание: Ссылка "скачать" может вести как непосредственно на файл, так и на сайт производителя, на котором Вы можете найти нужный файл.
Это связано с тем, что некоторые производители не позволяют размещать прямые ссылки на файлы.