- Notes, cautions, and warnings
- iDRAC9 Release Notes
- Revision History
- Product description
- New features
- Resolved issues
- Known issues
- Limitations
- Environmental and system requirements
- Installation and upgrade considerations
- Where to get help
Description | A mismatch in cryptographic erase capable attribute values may be displayed in Redfish interface in current version of iDRAC firmware and version 6.00.30.00. |
Workaround | Check in other iDRAC interfaces. |
Systems Affected | All systems supported by this release. |
Tracking number | 252957 |
Description | After HBA355e controller firmware update, iDRAC interfaces may display duplicate entries for enclosure and drives under the storage enclosure and storage physical disk page. |
Workaround | Perform an iDRAC reset. |
Systems Affected | All systems supported by this release. |
Tracking number | 251527 |
Description | iDRAC GUI may fail to display the front backplane image of the supported backplane with 3.5" drives and 2.5" drives in all the slots. |
Workaround | Ensure that at least one Physical disk form factor matches with backplane form factor. |
Systems Affected | All systems with front backplanes supported by this release. |
Tracking number | 244410 |
Description | Drives that are encrypted by a third-party application may be displayed a "Encryption Capable" instead of "Secured by Foreign Key" |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 247168 |
Description | RAC0128 error is displayed after vFlash initializes with a failure in image upload that is caused by a network disruption during Create Partition task. |
Workaround | Reset the iDRAC. |
Systems Affected | All systems supported by this release. |
Tracking number | 252865 |
Description | If iDRAC and PERC have the same Key Ids then PERC Rekey command fails. |
Workaround | Use the iDRAC Rekey command instead of PERC Rekey. |
Systems Affected | All systems supported by this release. |
Tracking number | 230629/189445 |
Description | Maximum capable speed for SAS4 drives that are configured with PERC9, PERC10, or PERC 11 is reported as Unknown in iDRAC. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 230290 |
Description | After a disk firmware upgrade, LC logs may report it as a firmware downgrade with PR36 message. |
Workaround | Restart the host system. |
Systems Affected | All systems supported by this release. |
Tracking number | 197049 |
Description | When existing VD is deleted from iDRAC GUI using delete VD operation from the Virtual disk option and then added to pending operation, the pending operation displays no information. However, the delete VD pending operation is created successfully. |
Workaround | To successfully delete the VD and add to pending operations, perform the following steps:
|
Systems Affected | All systems supported by this release. |
Tracking number | 184393 |