Unexpected reboot analysis
Unexpected reboots should be treated as incidents until cause is known.
Steps
- Collect OS logs and uptime history.
- Check power, hardware, and kernel events.
- Review maintenance notices.
- Request facility or hardware investigation if unclear.
Useful information to include
- Server ID
- Reboot time
- OS logs
- Application impact
Escalation
Contact Metal on Cloud support when the issue affects production, requires privileged access, involves billing, or needs a formal incident record.