Oracle^® 6.4 TB NVMe SSD v1 Product Notes

28244670

Oracle ILOM Reports a Fault fault.io.scsi.cmd.disk.dev.rqs.baddrv

27759886

Oracle 6.4 TB NVMe SSD v1 Asserting on RE14

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. See Secure Erase Drives Before Use.

28708331

Device Monitor: Extend jitter check to cover device read failures

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).

27410962

Oracle 6.4 TB NVMe SSD v1 loses namespace, IPS 00214730

27036497

MI data returns Drive not ready: TRUE when drive is healthy and functional in-band

27002878

Oracle 6.4 TB NVMe SSD v1 failed on the first boot to Solaris when VTS was started

27002555

Oracle 6.4 TB NVMe SSD v1 does not come ready beyond 20 seconds

26942617

ATS hwdiag pci info all fails for NVMe Oracle 6.4 TB NVMe SSD v1

26910610

Oracle 6.4 TB NVMe SSD v1 disappears when binding to VFIO

26865237

Oracle 6.4 TB NVMe SSD v1 has Queue fail and device no response during SPARC system reboot test

26830704

Oracle 6.4 TB NVMe SSD v1 hwdiag reports invalid field length of vendor specific block This output can be viewed only from the restricted access Sun Service hwdiag shell.

26789934

Oracle 6.4 TB NVMe SSD v1 Invalid field length of vendor specific block for DSN length with RE0D

26726770

Oracle 6.4 TB NVMe SSD v1 fault.io.intel.iio.pcie-data-link-layer-inactive

26693990

Oracle 6.4 TB NVMe SSD v1 drives experiencing pcie-link-degraded-width fault on X7-2L

26630304

Oracle 6.4 TB NVMe SSD v1 devices lost during and after testing

26566040

Determine the correct NVMe Shutdown timeout period for RTD3 (RunTime D3) power state

Oracle 6.4 TB NVMe SSD v1s support NVMe specifications for RTD3 Resume Latency and RTD3 Entry Latency. RTD3R Resume latency allows 12 seconds of margin for devices to safely start before main power is applied to the device controller. RTD3E Entry latency allows 10 seconds of margin for active devices to safely shutdown before main power is removed from the device controller.