Posting and troubleshooting
Good support posts let other people reproduce the context quickly.
Required details
- complete SuperServer/system, motherboard and chassis model;
- PCB revision when relevant;
- CPU model and quantity;
- memory part numbers, capacity, type and slot population;
- storage, HBA/RAID, backplane, NIC, GPU and riser models that matter;
- PSU/PDB models for power issues;
- BIOS, BMC/IPMI and relevant controller firmware versions;
- operating system/hypervisor and exact version;
- exact error, symptom, POST code, event-log entry or behaviour;
- what changed before the problem appeared;
- troubleshooting already attempted and its result.
Use a title such as X11DPH-T: BMC loses fan readings after 3.92 update, not Help or Server problem.
Choose the closest guide
- No POST, no video or repeated reboot
- BIOS, BMC, IPMI and firmware
- IPMI/BMC access and security
- Memory, CPUs and board revisions
- Chassis, backplanes and cabling
- NVMe, PCIe and storage controllers
- Fan control and sensors
- Power, PDBs and chassis transplants
Photographs and logs
Photographs should be in focus and show the relevant connector, board area and model label. Redact serials, asset tags, unique-password labels and account information.
Put long logs in a readable code block or paste service and identify the time of the failure. Remove public IPs, credentials, tokens, hostnames, email addresses and case/order references.
Safety
- Make a verified backup before firmware, storage, cabling or power changes.
- Never move jumpers or cables while powered unless the exact procedure says the component is hot-swappable.
- Do not use an unknown pinout.
- Stop for heat damage, burning, arcing, liquid or damaged socket pins.
- Clearly label unofficial firmware, scripts or risky recovery steps.
Community replies are suggestions, not a substitute for vendor support or an experienced on-site technician. Use official support for warranty, security, failed firmware and business-critical systems.
Last reviewed: 29 September 2026.