Dell PowerVault MD 34/38 Series Storage Controller Firmware and NVSRAM firmware version 08.25.14.60
需要重新啟動hi testing
驅動程式 ID : NC41W
重要性 : 建議
繁體中文版 : 08.25.14.60, A19 最新版本 建議版本 最新與建議版本
發佈日期 : 24 8月 2018
下載類型 : 韌體
類別 : 儲存控制器
Dell PowerVault MD 34/38 Series Storage Array
下載檔案
檔案名稱: PowerVault_MD34_MD38_Series_Firmware_08_25_14_60.zip
檔案大小: 69.64 MB
為了確保下載的完整性，請驗證總和檢查值。
MD5： 87273191b573e9ae3a4d91bd5b6e16e5
SHA1： c30a029de2c0aa628da90b2664d595363ec603f4
SHA-256： 0b66cfd458f92cdeddeb742cb85f2edb7756fd982f6bb7118f7f7b6719f26691
修復及強化
Fixes:
Host IO during missing drive recovery for a volume with unwritten data in cache causes Data Assurance error or data inconsistency.
With 16Gb Fibre Channel, RLS request from the switch can cause controller reboot or an extremely unlikely chance of data inconsistency.
On Dense array with a reconfiguration operation (ex: dynamic volume expansion, RAID migration, etc.) and synchronous mirroring, an unexpected controller reboot occurred.
Replacing all drives in a pool with larger capacity drives results in data loss.
On dense array with write-back cache and cache mirroring enabled, heavy write workload results in host I/O timeouts and aborts.
Failed hardware component caused drive discovery errors and overlapping target resets, which lead to drive failures.
If a controller reboots while a drive is being failed, in extremely rare circumstances, data integrity issues could occur.
Changing the host port configuration when volume discovery is occurring on a host causes a controller to reboot.
With 'cache without batteries' enabled, a 'sync cache' command from the host may cause a controller reboot.
When migrating controller firmware between certain versions, an unexpected controller reboot may occur.
With greater than 200 hosts in a cluster, a device reset issued by a host caused an unexpected controller reboot.
With asynchronous mirroring, workloads that fill write cache can cause unexpected controller reboots.
On dense array with more than one thin-provisioned volume, under rare circumstances (that increase in probability with larger numbers of thin volumes), writes to previously unwritten regions of the thin volumes can lead to data integrity issues or controller reboots.
With iSCSI, a rare timing issue could cause a controller to attempt to close a session twice, which results in a controller reboot.
With a non-pool volume with an integrated hot spare, a flaky drive that generates critical event 0x224D results in continuous reboots or controller lockdown.
If a drive is failed by the controller due to impending failure, the drive fail operation cannot be cancelled.
With pools, if a drive is removed before or during a system power-cycle, controller lockdown or potential data loss could occur.
SMcli check parity command could stall if data parity mismatch is found.
Unexpected failure when configuring only IPv4 address if IPv6 is enabled.
Unexpected controller reboot/core dump on dense array when a pool or pool volume is undergoing reconfiguration.
On dense array, asynchronous mirror or snapshot with multiple repository volumes may result in unexpected controller reboots.
With VMware VAAI enabled and synchronous mirroring on dense array, unexpected controller reboots could occur.
Volume would not fail back to preferred controller after SAN fault recovery due to unlikely error while processing STPG from FlexArray (or other explicit mode TPGS/ALUA driver).
Enhancements:
None
Host IO during missing drive recovery for a volume with unwritten data in cache causes Data Assurance error or data inconsistency.
With 16Gb Fibre Channel, RLS request from the switch can cause controller reboot or an extremely unlikely chance of data inconsistency.
On Dense array with a reconfiguration operation (ex: dynamic volume expansion, RAID migration, etc.) and synchronous mirroring, an unexpected controller reboot occurred.
Replacing all drives in a pool with larger capacity drives results in data loss.
On dense array with write-back cache and cache mirroring enabled, heavy write workload results in host I/O timeouts and aborts.
Failed hardware component caused drive discovery errors and overlapping target resets, which lead to drive failures.
If a controller reboots while a drive is being failed, in extremely rare circumstances, data integrity issues could occur.
Changing the host port configuration when volume discovery is occurring on a host causes a controller to reboot.
With 'cache without batteries' enabled, a 'sync cache' command from the host may cause a controller reboot.
When migrating controller firmware between certain versions, an unexpected controller reboot may occur.
With greater than 200 hosts in a cluster, a device reset issued by a host caused an unexpected controller reboot.
With asynchronous mirroring, workloads that fill write cache can cause unexpected controller reboots.
On dense array with more than one thin-provisioned volume, under rare circumstances (that increase in probability with larger numbers of thin volumes), writes to previously unwritten regions of the thin volumes can lead to data integrity issues or controller reboots.
With iSCSI, a rare timing issue could cause a controller to attempt to close a session twice, which results in a controller reboot.
With a non-pool volume with an integrated hot spare, a flaky drive that generates critical event 0x224D results in continuous reboots or controller lockdown.
If a drive is failed by the controller due to impending failure, the drive fail operation cannot be cancelled.
With pools, if a drive is removed before or during a system power-cycle, controller lockdown or potential data loss could occur.
SMcli check parity command could stall if data parity mismatch is found.
Unexpected failure when configuring only IPv4 address if IPv6 is enabled.
Unexpected controller reboot/core dump on dense array when a pool or pool volume is undergoing reconfiguration.
On dense array, asynchronous mirror or snapshot with multiple repository volumes may result in unexpected controller reboots.
With VMware VAAI enabled and synchronous mirroring on dense array, unexpected controller reboots could occur.
Volume would not fail back to preferred controller after SAN fault recovery due to unlikely error while processing STPG from FlexArray (or other explicit mode TPGS/ALUA driver).
Enhancements:
None
重要資訊
This update is strongly recommended for all MD34/MD38 Series Storage Arrays
相容的系統
支援的作業系統
Novell SuSE Linux ES 11
Red Hat® Enterprise Linux 6
Red Hat® Enterprise Linux 7
Windows Storage Server 2012 R2
SUSE Linux ES 12
Windows Server 2012 R2
Windows 7, 64-bit
Windows 8, 64-bit
Windows 8.1, 64-bit
Windows Server 2008 R2
Windows Server 2016
Windows 10, 64-bit
VMware ESXi 5.1
VMware ESXi 5.5
VMware ESXi 6.0
VMware ESXi 6.5
安裝指示
NOTE: I/O to the array can continue while you are upgrading RAID controller and NVSRAM firmware.
NOTE: It is recommended that the firmware and NVSRAM be upgraded during a maintenance period when the array is not being used for I/O.
NOTE: The RAID enclosure must contain at least two disk drives in order to update the firmware on the controller.
To download RAID controller and NVSRAM firmware in a single operation:
1. If you are using the EMW, go to step 9. If you are using the AMW, go to step 2.
2. In the AMW, select Upgrade>RAID Controller Module Firmware>Upgrade.
The Download RAID Controller Module Firmware is displayed.
NOTE: The RAID Controller Module Firmware area and the NVSRAM area list the current firmware and the current NVSRAM versions respectively.
3. To locate the directory in which the file to download resides, click Select File next to the Selected
RAID controller module firmware file text box.
4. In the File Selection area, select the file to download. By default, only the downloadable files that are compatible with the current storage array configuration are displayed.
When you select a file in the File Selection area of the dialog, applicable attributes (if any) of the file are displayed in the File Information area. The attributes indicate the version of the file.
5. If you want to download an NVSRAM file with the firmware:
a) Select Transfer NVSRAM file with RAID controller module firmware.
b) Click Select File.
6. To transfer the files to the RAID controller module without activating them, click Transfer files but
don't activate them (activate later).
7. Click Transfer.
Keep these guidelines in mind: If the Transfer button is inactive, ensure that you either select an NVSRAM file or clear the Transfer NVSRAM file with RAID controller module firmware check box.
8. In the Confirm Download dialog, click Yes. The download starts.
9. If you are using the EMW, perform one of these actions: Select Tools>Upgrade RAID Controller Module Firmware. Select the Setup tab, and click Upgrade RAID Controller Module Firmware.
10. In the Storage array pane, select the storage array for which you want to upgrade the RAID controller module firmware or the NVSRAM. You can select more than one storage array.
NOTE: The Details pane shows the details of only one storage array at a time. If you select more than one storage array in the Storage Array pane, the details of the storage arrays are not shown in the Details pane.
11. Click Firmware in the Download area. If you select a storage array that cannot be upgraded, the Firmware button is disabled. The Download Firmware dialog is displayed. The current firmware version and the NVSRAM version of the selected storage arrays appear. Click OK to close the dialog and select the storage arrays with similar RAID controller module types.
12. To locate the directory in which the file to download resides, click Browse in the Select files area. The Select File dialog is displayed.
13. Select the file to download.
14. Click OK.
15. If you want to download the NVSRAM file with the RAID controller module firmware, select Download NVSRAM file with firmware in the Select files area. Any attributes of the firmware file are displayed in the Firmware file information area. The attributes indicate the version of the firmware file. Any attributes of the NVSRAM file are displayed in the NVSRAM file information area. The attributes indicate the version of the NVSRAM file.
16. If you want to download the file and activate the firmware and NVSRAM later, select the Transfer files but do not activate them (activate later) check box.
17. Click OK. The Confirm Download dialog is displayed.
18. Click Yes.
The download starts and a progress indicator is displayed in the Status column of the Upgrade RAID Controller Module Firmware window.
NOTE: It is recommended that the firmware and NVSRAM be upgraded during a maintenance period when the array is not being used for I/O.
NOTE: The RAID enclosure must contain at least two disk drives in order to update the firmware on the controller.
To download RAID controller and NVSRAM firmware in a single operation:
1. If you are using the EMW, go to step 9. If you are using the AMW, go to step 2.
2. In the AMW, select Upgrade>RAID Controller Module Firmware>Upgrade.
The Download RAID Controller Module Firmware is displayed.
NOTE: The RAID Controller Module Firmware area and the NVSRAM area list the current firmware and the current NVSRAM versions respectively.
3. To locate the directory in which the file to download resides, click Select File next to the Selected
RAID controller module firmware file text box.
4. In the File Selection area, select the file to download. By default, only the downloadable files that are compatible with the current storage array configuration are displayed.
When you select a file in the File Selection area of the dialog, applicable attributes (if any) of the file are displayed in the File Information area. The attributes indicate the version of the file.
5. If you want to download an NVSRAM file with the firmware:
a) Select Transfer NVSRAM file with RAID controller module firmware.
b) Click Select File.
6. To transfer the files to the RAID controller module without activating them, click Transfer files but
don't activate them (activate later).
7. Click Transfer.
Keep these guidelines in mind: If the Transfer button is inactive, ensure that you either select an NVSRAM file or clear the Transfer NVSRAM file with RAID controller module firmware check box.
8. In the Confirm Download dialog, click Yes. The download starts.
9. If you are using the EMW, perform one of these actions: Select Tools>Upgrade RAID Controller Module Firmware. Select the Setup tab, and click Upgrade RAID Controller Module Firmware.
10. In the Storage array pane, select the storage array for which you want to upgrade the RAID controller module firmware or the NVSRAM. You can select more than one storage array.
NOTE: The Details pane shows the details of only one storage array at a time. If you select more than one storage array in the Storage Array pane, the details of the storage arrays are not shown in the Details pane.
11. Click Firmware in the Download area. If you select a storage array that cannot be upgraded, the Firmware button is disabled. The Download Firmware dialog is displayed. The current firmware version and the NVSRAM version of the selected storage arrays appear. Click OK to close the dialog and select the storage arrays with similar RAID controller module types.
12. To locate the directory in which the file to download resides, click Browse in the Select files area. The Select File dialog is displayed.
13. Select the file to download.
14. Click OK.
15. If you want to download the NVSRAM file with the RAID controller module firmware, select Download NVSRAM file with firmware in the Select files area. Any attributes of the firmware file are displayed in the Firmware file information area. The attributes indicate the version of the firmware file. Any attributes of the NVSRAM file are displayed in the NVSRAM file information area. The attributes indicate the version of the NVSRAM file.
16. If you want to download the file and activate the firmware and NVSRAM later, select the Transfer files but do not activate them (activate later) check box.
17. Click OK. The Confirm Download dialog is displayed.
18. Click Yes.
The download starts and a progress indicator is displayed in the Status column of the Upgrade RAID Controller Module Firmware window.
適用於
MD3 Series Controller Firmware Updates