Hardware Failure

Sophos XGS 87 POST failure on startup: 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.

Across years of operating Sophos gear I have watched the same hardware-failure pattern repeat: a unit ships fine, runs for two years, then trips on a power-event or a thermal excursion. On SFOS (Sophos Firewall OS) the recovery path is the same whether the affected unit is from the XGS 87 family or something newer.

Before you touch anything, capture state. `system version (CLI)` and `system diagnostics show device-info` dumped to a file is worth more than a screen-cap because Sophos Support will ask for the exact output when you open the case. Keep the artifact even if the box recovers on its own.

Below I walk through the on-box steps first, then the Sophos Support escalation path. If you have spares on hand, swap-then-diagnose is usually faster than diagnose-then-swap, but only if you can afford the rack time.

What this guide covers

Diagnose and recover from POST failure on startup on a Sophos XGS 87.

Step-by-step

Note the exact POST failure code from the console.
Look up the code in the vendor hardware install guide.
Common: memory test fail (RMA RAM / motherboard), FPGA fail (RMA mainboard).
Open a Sophos Support case with the POST log and the device serial.

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.

Before you start

A few things to confirm so the Sophos device fix goes cleanly:

Latest firmware downloaded if you're going to update.
Warranty + support contract status checked, opening sealed parts may void it.
Backup of current configuration (where applicable) taken.
Spare parts on hand if you anticipate replacement.
Adequate workspace, lighting, and time. rushing causes regressions.

How to confirm it's actually fixed

On a Sophos device, the test is rarely "reboot and see". Use this list:

Active reproduction: trigger the original failure path on purpose.
Indirect reproduction: do an activity that would expose the same subsystem.
Status indicator review: every LED / display / app status should be green.
24-hour soak: leave the device under normal load overnight; check the next morning.
Telemetry check: review the device or app's diagnostic log for new error entries.

When to call Sophos support instead

Escalate if:

The same symptom returns within 24 hours of a clean fix.
You see physical damage (burn marks, swollen battery, cracked PCB).
The device is in warranty and a hardware replacement is the cheaper outcome.
Repair requires specialised tools you don't own (alignment jigs, calibration software).
Following the official path keeps the warranty intact, which matters more than the time spent.