Sophos XGS 126 won't boot at all: Diagnose & Fix
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| 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 126.
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.
Related guides
Related fixes
Related guides worth a look while you sort this one out:
- Sophos XGS 107 won't boot at all: Diagnose & Fix
- Sophos XGS 116 won't boot at all: Diagnose & Fix
- Sophos XGS 87 won't boot at all: Diagnose & Fix
- Sophos AP6 420 won't boot at all: Diagnose & Fix
- Sophos AP6 420E won't boot at all: Diagnose & Fix
- Sophos XGS 126 stuck at boot loader prompt: Diagnose & Fix
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.
Verification checklist
After applying the fix on your Sophos device, confirm:
- The original symptom is no longer reproducible.
- Related features (status LEDs, app sync, paired accessories) still work.
- The device responds to a soft reboot without the fault returning.
- Any error codes that were on display have cleared.
- Documentation (your service log, the brand companion app) reflects the change.
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.
More frequently asked questions
How long does this fix usually take?
Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.
Will this void my warranty?
Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.
Should I update firmware first or last?
Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.
Is it safe to apply during business hours?
If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.
Why is this happening on a brand-new unit?
Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.