Device identity
Rack/U, asset tag, serial, model and any label that prevents work on the wrong system.
Hardware support
Troubleshoot the physical layer without guessing at the system layer.
Hardware intervention is safer when symptoms, approved diagnostics, replacement parts and rollback/stop conditions are explicit before the chassis is opened.
Quick answer
A useful hardware-support request identifies the exact device, symptoms, existing remote diagnostics, actions already attempted, parts available, approved physical tests and what should trigger a stop/escalation. Logical data recovery and OS repair are separate scopes unless agreed.
Diagnostic brief
What to send before a hardware intervention
Symptoms
LED state, BMC alerts, POST errors, link loss, drive state or other observable failure evidence.
What you already tried
Remote reboot, BMC checks, cable tests or other actions — avoid repeating risky work unnecessarily.
Replacement part
Part number, compatibility, location and whether data-bearing media has handling requirements.
Change control
Define the safe boundary
Approve actions
List what can be reseated, replaced, disconnected or power-cycled.
Protect data
Identify data-bearing drives and any chain-of-custody or no-removal requirement.
Set escalation
If findings differ from the brief, pause and contact the designated decision-maker.
Verify
Check physical health indicators and hand control back to the remote system owner for logical validation.
FAQ
Questions to settle before deployment or onsite work
Physical checks can be scoped, including power, cabling, indicators, console state and approved component tests. OS/filesystem or data recovery is separate and requires its own plan.
Do not assume it. Data-bearing media handling, retention, return or destruction requires a specific chain-of-custody and security agreement.
Technical request
Describe the hardware or onsite task
For faster scoping, include the equipment, location, requested action, maintenance window, urgency and any stop conditions.
Turn the requirement into an executable scope.
Send the hardware, workload or onsite task. We will separate assumptions from confirmed availability before anything is deployed or touched.