Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

iDRAC9 Version 7.00.00.00 Release Notes

PDF

Storage

Table 1. Backplane firmware update job failing Unable to create a backplane firmware update job after running the systemerase reinstallfw command immediately after performing systemerase lcdata
Description Unable to create a backplane firmware update job after running the "racadm systemerase reinstallfw" command immediately after performing "racadm systemerase lcdata".
Workaround Restart the iDRAC and then try "racadm systemerase reinstallfw" command.
Systems Affected All systems supported by this release.
Tracking number 265093
Table 2. BOSS configuration job failing A device configuration job to enable or disable security on BOSS devices may fail with JCP042 message. A PR19 configuration update success message is also logged as the configuration of attributes succeeds.
Description A device configuration job to enable or disable security on BOSS devices may fail with JCP042 message. A PR19 configuration update success message is also logged as the configuration of attributes succeeds.
Workaround Retry the configuration job.
Systems Affected All systems supported by this release.
Tracking number 263709
Table 3. JBODs not displaying in iDRAC iDRAC fails to display the drives in the enclosure PowerVault MD 2412, PowerVault MD 2424, and PowerVault MD 2460 after a warm boot.
Description iDRAC fails to display the drives in the enclosure PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 after a warm boot.
Workaround Perform an iDRAC reset.
Systems Affected All systems supported by this release configured with PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 enclosures.
Tracking number 261523
Table 4. Unable to update external enclosures Changing external enclosure element (EMM/PSU/Fan/TempProbes) inventory/monitoring and Enclosure AssetTag and AssetName may fail for PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 that is connected to the server through PERC H840.
Description Changing external enclosure element (EMM/PSU/Fan/TempProbes) inventory/monitoring and Enclosure AssetTag and AssetName may fail for PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 that is connected to the server through PERC H840.
Workaround N/A
Systems Affected All systems that supported by this release with PERC H840 connected to SAS4 JBODs on PowerVault MD 2412 or PowerVault MD 2424, or PowerVault MD 2460.
Tracking number 260963, 260401, 257318
Table 5. Enclosure components not displayed In servers that are attached to PowerVault MD2460 connected through PERC HBA355e, iDRAC may not display the enclosure components such as Fan, Temperature Probes, EMM, and PSU.
Description In servers that are attached to PowerVault MD2460 connected through PERC HBA355e, iDRAC may not display the enclosure components such as Fan, Temperature Probes, EMM, and PSU.
Workaround N/A
Systems Affected All systems supported by this release.
Tracking number 256962
Table 6. Physical disks not unlocking Physical disks that are connected to a BOSS-N1 controller are not unlocking on system boot.
Description Physical disks that are connected to a BOSS-N1 controller are not unlocking on system boot.
Workaround Perform a system cold boot.
Systems Affected All systems supported by this release.
Tracking number 261135
Table 7. FIPS140ComplianceDescriptor not available GET method on Drives URI not displaying the FIPS140ComplianceDescriptor property for hard drives in the response.
Description GET method on Drives URI not displaying the FIPS140ComplianceDescriptor property for hard drives in the response.
Workaround N/A
Systems Affected All systems supported by this release.
Tracking number 261024
Table 8. Incorrect enclosure state Hot reinsertion of enclosure cables to PERC H840 may cause a change in the enclosure state as Removed and summary of the drive slots in the enclosure page may be displayed as Slot empty.
Description Hot reinsertion of enclosure cables to PERC H840 may cause a change in the enclosure state as Removed and summary of the drive slots in the enclosure page may be displayed as Slot empty.
Workaround Reset the iDRAC.
Systems Affected All 14th and 15th generation of PowerEdge Servers with PERC H840 external controller connected to JBODs.
Tracking number 260816
Table 9. Redundant path not present The value for Redundant Path for an enclosure is displaying as Not Present in iDRAC interfaces.
Description The value for Redundant Path for an enclosure is displaying as Not Present in iDRAC interfaces.
Workaround Perform an iDRAC reset or power cycle the system.
Systems Affected All systems supported by this release.
Tracking number 260767
Table 10. PR36 version change log not displaying for E3 drive firmware update PR36 Lifecycle (LC) Log may not be displayed for a few E3 drives. For example, if all the drive slots are populated with E3 devices, the update completes for all the drives, however, only a few drives report the PR36 message in LC logs.
Description PR36 Lifecycle (LC) Log may not be displayed for a few E3 drives. For example, if all the drive slots are populated with E3 devices, the update completes for all the drives, however, only a few drives report the PR36 message in LC logs.
Workaround See the iDRAC inventory page if the version is updated for the drive.
Systems Affected All systems supported by this release.
Tracking number 256017
Table 11. PERC12 Adapter not displayed in iDRAC After performing a SystemErase or LCWipe, PERC 12 controllers such as H965i, H965i Front adapters may not be displayed under the iDRAC Storage page.
Description After performing a SystemErase or LCWipe, PERC 12 controllers such as H965i, H965i Front adapters may not be displayed under the iDRAC Storage page.
Workaround Reboot the host system or perform a Racreset.
Systems Affected All 16th Generation of PowerEdge servers supported by this release with PERC12 controllers.
Tracking number 257716
Table 12. Duplicate entry for drives and enclosures After HBA355e controller firmware update, iDRAC interfaces display duplicate entries for enclosure and drives under the storage enclosure and storage physical disk page.
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
Table 13. Error RAC0128 in vFlash iDRAC may not display the drive speed for SAS4 drives.
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
Table 14. PERC Rekey failingIf iDRAC and PERC have the same Key Ids then PERC Rekey command fails.
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
Table 15. 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

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\