iDRAC9 Version 5.00.15.00 Release Notes

Release Summary

PDF

Storage and storage controllers

Table 1. Cryptographic erase failing on Micron drives Cryptographic erase operation may fail on Micron drives with an error code "SYS157".
Description	Cryptographic erase operation may fail on Micron drives with an error code "SYS157".
Workaround	Perform the cryptographic erase using BIOS (System Setup).
Systems Affected	All systems supported by this release.
Tracking number	205468

Table 2. Cryptographic erase failing on hot-plugged NVMe drives Cryptographic erase operation may fail on hot-plugged NVME drives, even after performing a server reboot.
Description	Cryptographic erase operation may fail on hot-plugged NVME drives, even after performing a server reboot.
Workaround	Perform an iDRAC reboot.
Systems Affected	All systems supported by this release.
Tracking number	201915

Table 3. iDRAC displays disks as not capable of cryptographic erase iDRAC may display cryptographic erase capable disk as not capable.
Description	iDRAC may display cryptographic erase capable disk as not capable.
Workaround	Perform an iDRAC reboot.
Systems Affected	All systems supported by this release.
Tracking number	205535

Table 4. Unable to create RAID 10 using LC Creating RAID 10 through Lifecycle Controller interface fails with a message "You have selected too many physical disks for this RAID level" on configurations with four or more SATA SSDs and SAS drives.
Description	Creating RAID 10 through Lifecycle Controller interface fails with a message "You have selected too many physical disks for this RAID level" on configurations with four or more SATA SSDs and SAS drives.
Workaround	Use any other iDRAC interface.
Systems Affected	All systems supported by this release.
Tracking number	204656

Table 5. Remote file share disconnecting RFS may get disconnected if iDRAC IP is not reachable for some time.
Description	RFS may get disconnected if iDRAC IP is not reachable for some time.
Workaround	Reboot iDRAC.
Systems Affected	All systems supported by this release.
Tracking number	201672

Table 6. LC logs display incorrect version change for disks After a disk firmware upgrade, LC logs may report it as a firmware downgrade with PR36 message.
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

Table 7. Storage Devices displayed in gray text After a reboot stress followed by BIOS update, storage devices may appear as not ready or in gray text.
Description	After a reboot stress followed by BIOS update, storage devices may appear as not ready or in gray text.
Workaround	Reset iDRAC.
Systems Affected	All PowerEdge Rx5xx/Cx5xx series supported by this release.
Tracking number	194537

Table 8. Deleting VD creates pending operation with empty data 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.
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: Select the Configuration option in iDRAC GUI Select Storage Configuration, then select the Controller and click Apply now.
Systems Affected	All systems supported by this release.
Tracking number	184393