Oracle 6.4 TB NVMe SSD v1s run with the minimum required firmware package listed in the following table.
|
The following improvements or changes were included in firmware QDV1RF35 release of Oracle 6.4 TB NVMe SSD v1:
Merged firmware for Oracle Flash Accelerator F640 PCIe Card and Oracle 6.4 TB NVMe SSD v1. Recommended firmware update improves quality of product and merges into one binary for both Oracle Flash Accelerator F640 PCIe Card and Oracle 6.4 TB NVMe SSD v1.
The Oracle 6.4 TB NVMe SSD v1 Firmware RF35 package includes the firmware files and associated metadata.xml files that automate the Oracle 6.4 TB NVMe SSD v1 update process.
If you install Oracle 6.4 TB NVMe SSD v1s as an option, you must update the firmware from release 8DV1RF30 or a lower release to release QDV1RF35.
The following improvements or changes were included in firmware 8DV1RF30 release of Oracle Flash Accelerator F640 PCIe Card and Oracle 6.4 TB NVMe SSD v1:
Merged firmware for Oracle Flash Accelerator F640 PCIe Card and Oracle 6.4 TB NVMe SSD v1. Recommended firmware update improves quality of product and merges into one binary for both Oracle Flash Accelerator F640 PCIe Card and Oracle 6.4 TB NVMe SSD v1.
The Oracle 6.4 TB NVMe SSD v1 Firmware RF30 package includes the firmware files and associated metadata.xml files that automate the Oracle 6.4 TB NVMe SSD v1 update process.
If you install Oracle 6.4 TB NVMe SSD v1s as an option, you must update the firmware from release 8DV1RE14 or a lower release to release 8DV1RF30.
Key Fixes include:
Bug ID 28244670 – Oracle ILOM incorrectly faults the device with message "Fault fault.io.scsi.cmd.disk.dev.rqs.baddrv on FRU /SYS"
Oracle Server X7-2L and Oracle Server X7-2L Software 1.3.2 or later with Oracle ILOM Software Release 4.0.4.21.a is required on x86 platforms using firmware release 8DV1RF30 to reduce device read failures. The SMbus can take up to 30 seconds to respond after a firmware update (Bug ID: 28708331 - Device Monitor: Extend jitter check to cover device read failures).
Bug ID 27759886 – Oracle 6.4 TB NVMe SSD v1 SFF Asserting on RE14 – when device sits unpowered for several weeks, device may report UE errors or assert
To immediately ensure the fix is implemented, perform the Secure Erase Drives Before Use erase sequence, otherwise after two weeks of device power-on the issue will be fully resolved.
Assert codes HI149 and DE003 (DRAM Memory Access Error), and NDA (no device attached) due to NAND channel timeout and sidetrace corruption
The following improvements or changes were included in firmware 8DV1RE14 release of Oracle 6.4 TB NVMe SSD v1s:
Support for Oracle X7 series servers.
Support for SPARC S7 series servers.
Support for SPARC T7 series servers.
Support for SPARC T8 series servers.
If you install Oracle 6.4 TB NVMe SSD v1s as an add-on option, you must update the firmware if the release number is lower than 8DV1RE14. Update to 8DV1RE14 or a subsequent release if available.
If you install Oracle 6.4 TB NVMe SSD v1s as an option, and you must update the firmware from release 8DV1RE12 or a lower release to release 8DV1RE14. You must update Oracle 6.4 TB NVMe SSD v1s to release 8DV1RE13 before they can be upgraded to release 8DV1RE14.
If the firmware release is lower than 8DV1RE13, for example release 8DV1RE12, 8DV1RE10, or 8DV1RE0F, do the following:
Run the fwupdate command once to update the device firmware to 8DV1RE13.
See Accessing Software Updates and Firmware Downloads.
The metadata file ensures that the first time the fwupdate command is run, the device only moves to 8DV1RE13.
The device NVMe Resets from metadata file sequence. The device requires a power cycle after the update for any bootloader changes to take effect.
Verify that the device firmware release is 8DV1RE13.
Run the fwupdate command again to update the firmware to 8DV1RE14, or a subsequent release if available.
Delay at least 30 seconds between running the two fwupdate commands.
The device NVMe Resets from metadata file sequence.
Verify that the device firmware release is 8DV1RE14.