Hardware Failure

Sophos XGS 87 won't boot at all: Diagnose & Fix

Q: Where can I find the Sophos official documentation?

https://support.sophos.com/support/s/ — search the product family + feature name.

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance

Vendor	Sophos
Operating system	SFOS (Sophos Firewall OS)
Category	Hardware Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Sophos Support + RMA.

A Sophos platform behaving badly is usually one of three things: a thermal/PSU issue caught by `system diagnostics show device-info`, a transceiver problem caught by `system interface show name=Port1`, or a boot-loader hang you only see on the console. SFOS (Sophos Firewall OS) surfaces all three differently from competitors, so the diagnostic order matters.

I will be honest: on the XGS 87 family I have seen at least one false-positive from the on-box monitoring per quarter. Always cross-check what `system version (CLI)` and `system diagnostics show device-info` reports against the physical front-panel and a smell test of the chassis.

If this is your first Sophos hardware issue, the good news is that Sophos Support is competent and the part-replacement RMA cycle is usually under a week for a covered unit.

What this guide covers

Diagnose and recover from won't boot at all on a Sophos XGS 87.

Step-by-step

Confirm power: PSU LED is green? Cable seated? Wall outlet live?
Try a known-good power cable + outlet.
If the device has multiple PSUs, try with only one PSU at a time.
Connect the console cable and watch for ANY output during power-on.
If completely dark (no LEDs, no console), suspect the PSU or motherboard.
Confirm warranty status, open a Sophos Support case, prepare for an RMA.

CLI / commands

# Verify hardware state
system version (CLI)
system status
system diagnostics show device-info

# Collect for Sophos Support
system support-tools generate-debug-info

When to RMA

Repeated failure after re-seat and power-cycle
Visible burn, scorching, or physical damage
POST or memory diagnostic failure
Hardware crashinfo without a software workaround

Frequently asked questions

Will this work on my specific SFOS (Sophos Firewall OS) version?

The procedure reflects current SFOS (Sophos Firewall OS) behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a Sophos Support case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the Sophos official documentation?

https://support.sophos.com/support/s/. search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

All Sophos fix guides → /sophos/
All vendor guides → /vendors/

Related guides worth a look while you sort this one out:

References

Sophos support portal: https://support.sophos.com
Sophos knowledge base: https://support.sophos.com/support/s/
Sophos security advisories: https://www.sophos.com/en-us/security-advisories
Open a case: https://secure2.sophos.com/en-us/support.aspx

Reference material, not professional advice. Validate against your specific SFOS (Sophos Firewall OS) version and test in a non-production environment before applying.

Common patterns we see

When this symptom shows up on a Sophos device, three patterns repeat:

1. Recent firmware update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger: temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Safety + preconditions

Before any work on a Sophos device:

Unplug from mains for any internal-access procedure.
Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
Use ESD-safe handling for boards and modules. no carpet, no wool sleeves.
Avoid moisture; never apply liquids near vents or connectors.
If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

Quick verification

Before you walk away from a Sophos device fix, run through:

1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

Escalation guide

For a Sophos device, the right escalation depends on impact:

Cosmetic / minor: log a ticket via the Sophos app or web portal. Response 1-3 business days.
Mid-impact: phone support. Have your serial number ready.
Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
Out of warranty: third-party repair shop with manufacturer-certified technicians.