The TPM chip in your server typically contains encryption/security related data.. If a request to clear the chip was made you will see the following error.

“A configuration changes was requested to clear this computers TPM (Trusted Platform Module.)

It then warns you that clearing the TPM will erase all encryption keys stored on the chip.

You can choose to clear the TPM or reject the change. Your choice depends entirely on your setup.

Before clearing the TPM, determine whether the server uses:

• BitLocker (if running Windows)
• LUKS or other disk encryption (if running Linux)
• Virtualization security features that store secrets in the TPM

If the server is not using TPM-backed encryption or security keys, selecting Yes to clear the TPM is generally safe.

If the server is using BitLocker or other TPM-based encryption, make sure you have the recovery keys before clearing it. Otherwise, the operating system may require recovery information at the next boot.

A few questions:

1. What operating system is installed (Windows Server, VMware ESXi, Linux, etc.)?
2. Did this prompt appear after a BIOS/iDRAC/firmware update?
3. Is this a production server or a lab/test machine?

That will help determine whether clearing the TPM is appropriate.

Other common items stored in a TPM include:

• Disk encryption keys (or key protectors), such as those used by BitLocker.
• Platform integrity measurements, which help verify that the server booted with trusted firmware and software.
• Machine certificates and private keys used for authentication, VPNs, or secure communications.
• Secure Boot and attestation data used to prove the system’s identity and integrity.
• Virtualization and security feature secrets, such as credentials used by virtualization-based security features.
• User authentication material, such as Windows Hello-related keys on desktop systems.

On a server like a Dell PowerEdge R640, the most important concern is usually whether:

1. The operating system drive is encrypted and uses the TPM.
2. Applications or management tools store certificates or cryptographic keys in the TPM.

What happens if you clear it?

Clearing the TPM:

• Deletes the TPM’s stored keys and secrets.
• Does not erase disks or operating system files.
• Does not delete application data.
• May require recovery keys or re-enrollment of security features that depended on those TPM keys.

If this is a server recently purchased and you have no encrypted data on the machine it is generally OKAY to clear the TPM.

I observed the following error on a server I was troubleshooting. “A PCIe link training failure is observed in Embedded Network Device and the link is disabled.”

I love errors like this because it’s telling you in no uncertain terms what hardware device is causing the problem. In this case, the NDC or network daughter card.

Drilling into BIOS—>Devices I can see the problem. This is a 4 port card but only 2 ports are showing up.

Best case scenario is you reseat the card and the problem goes away. That’s not the case for me so my next course of action is to simply replace the card and if that doesn’t work, begin reseating the processors and inspecting the pins for damage. Because PCIe errors are related to the CPU don’t rule out problems with CPUs or the pins themselves on the motherboard.

Luckily, I just needed to replace the card. All ports are now good to go and the PCIe errors are resolved.

You may buy or receive a server that has branding (sometimes ugly branding.) You can rebrand using the DELL OEM Identity module. This will reset the branding back to DELL factory faults.

The following guide can be used to rebrand most DELL servers across different generations. FIrst, download the appropriate Identity module. In the case of the R730xd we want to download this one.

The download will come in an EXE format. What you need to do is extract the EXE with a utility like 7zip to reveal the .PM file. I already have many of them downloaded and renamed but the filename will be something along the lines of 2P6YJ_R730xdDBE_CustBSU_1_00.pm.

Upload this file directly in iDRAC:

Reboot the server and you’ll see the rebranding process come to life:

Once completed the system will reboot itself, revealing the original DELL branding:

And that’s all there is to it!

Perhaps you have an old dusty HP DL-360 G9 laying around with a few spare parts. Maybe everything but a RAID controller. Not to fear, in the absence of an actual hardware RAID controller you can enable the integrated B140i software controller in the BIOS.

Steps:

First F9 into the BIOS and select System Options:

Next enter into SATA controller options:

Enter into Embedded SATA Configuration and Enable Dynamic Smart Array Support.

After reboot you’ll see the controller is now active:

Keep in mind this is a SATA controller. SAS/NVME will not be recognized. Instead of plugging the Mini SAS cables into a controller you will plug them straight into the motherboard.

When troubleshooting an HPE ProLiant DL385 Gen10 server that freezes during the “Memory Initialization” phase of the Power-On Self-Test (POST), one of the most commonly overlooked causes is an outdated BIOS. This issue is particularly relevant when the server has been upgraded with newer AMD EPYC processors, such as the EPYC 7502 from AMD’s second-generation “Rome” family.

Understanding Memory Initialization

Before a server can boot an operating system, the system firmware must perform a series of hardware checks and configuration tasks. One of the most critical stages is memory initialization, often referred to as memory training. During this process, the BIOS configures the processor’s integrated memory controllers, detects installed DIMMs, establishes timing parameters, and verifies that all memory channels can communicate correctly.

If any part of this process fails, the system may stop responding before completing POST.

The Relationship Between BIOS and Processor Support

The BIOS is responsible for initializing the processor and providing the microcode necessary for proper operation. When a server model is introduced, its firmware is designed to support the processors available at that time.

The HPE DL385 Gen10 was originally released when first-generation AMD EPYC processors were current. Later, AMD introduced second-generation EPYC 7002-series processors, including the EPYC 7502. Supporting these newer processors required significant firmware updates from HPE.

A BIOS version released before support for the EPYC 7002 series may not contain the required microcode, memory initialization routines, or processor-specific configuration tables. As a result, the server may be unable to complete memory training and can appear to freeze during the memory initialization stage.

Why the System Freezes at Memory Initialization

Modern AMD EPYC processors contain integrated memory controllers that manage communication with installed DIMMs. During POST, the BIOS must correctly configure these controllers according to the processor model and memory configuration.

If the BIOS does not recognize the installed processor correctly, several issues can occur:

• Memory channels may not initialize properly.
• Timing parameters may be programmed incorrectly.
• Processor-specific memory training algorithms may be unavailable.
• Communication between the CPU and DIMMs may fail.

Because memory training occurs early in the boot process, the server often freezes at the memory initialization screen rather than displaying a more descriptive error message.

Symptoms of an Outdated BIOS

Servers affected by this issue commonly exhibit one or more of the following symptoms:

• POST stops during memory initialization.
• No operating system boot occurs.
• Fans remain running while the screen remains unchanged.
• The Integrated Management Log may contain processor or memory training errors.
• The problem appears immediately after a CPU upgrade.
• The server works with older processors but not with newer EPYC models.

Why This Is Common After Processor Upgrades

Many organizations extend the life of their servers by upgrading processors rather than replacing entire systems. A DL385 Gen10 originally configured with first-generation EPYC processors may operate flawlessly for years.

However, when second-generation processors such as the EPYC 7502 are installed, the system suddenly requires firmware that understands the newer architecture. If the BIOS was never updated during the server’s life cycle, compatibility problems can appear immediately.

In some cases, the server may not even boot far enough to allow a normal firmware update, requiring the use of supported processors or alternative update methods.

How to Verify BIOS Compatibility

Administrators should compare the installed BIOS version against HPE’s processor support documentation for the specific server model. The server’s iLO interface can often display the current System ROM version even when the server fails to complete POST.

If the installed firmware predates support for AMD EPYC 7002-series processors, updating the System ROM should be considered a high-priority troubleshooting step.

Conclusion

After the system BIOS is updated the server boots all the way through: