| copyright | lastupdated | keywords | subcollection | content-type | ||
|---|---|---|---|---|---|---|
|
2024-10-29 |
troubleshooting bare metal servers, hardware issues, firmware |
vpc |
troubleshoot |
{{site.data.keyword.attribute-definition-list}}
{: #troubleshoot_bare_metal}
The following topics cover common difficulties that you might encounter, and offers some helpful tips.
{: #bare-metal-troubleshoot-hardware-issues} {: troubleshoot} {: support}
If your bare metal server experiences a hardware issue, you can request support by creating a support case. For more information, see Creating support cases.
After the operation team receives the case, the server goes into a maintenance state.
You must power off the bare metal server before it can go into the Maintenance state. {: note}
You can't start a bare metal server that's in a Maintenance state. The KVM console is also unavailable. You can't connect to the system over the network.
During maintenance, IBM also has no access to your network and workloads. The data on the disks isn't examined. But we still recommend you use software encryption for added security.
You can delete the bare metal server that is in the Maintenance state. {: note}
When the issues are fixed, the server is handed back to you and the state returns to Stopped.
{: #bare-metal-troubleshoot-custom-image-fail-boot} {: troubleshoot} {: support}
If your custom image fails to boot, open the console and debug the operating system boot sequence. The following are common issues that can cause a custom image boot failure.
- An unsigned operating system. Disable secure boot and try starting the system again.
- UEFI boot not support. Verify that the image has an EFI disk partition with an EFI boot loader.
If you need more help, you can request support by creating a support case. For more information, see Creating support cases.