HEART system.unexpected-restart H-01004

Unexpected restart. The system restarted without being asked to.

Likely causes

• A short power cut or brown-out reset the processor.
• A watchdog reset the product because its software hung.
• The software crashed and restarted itself.
• The product overheated and shut down to protect itself.
• A hardware fault: a loose connector, a failing power supply, a damaged board.

How to fix or prevent it

1. Look in the Rhythm for what happened just before: a power event, a crash, a temperature rise.
2. Check the power supply and its connections, and whether other devices on the same supply also restarted.
3. Check for software.crashed or performance.too-hot alerts around the same time.
4. Install the latest software update if one fixes resets.
5. To prevent it: use a stable supply (a UPS for important equipment), and keep vents clear.

What the HEART does by itself

After the restart it records the start (system.started, or system.restarted when it resumes from saved state), sees that nobody asked for a restart, and raises this alert with what it knows of the reason. It tells a person if restarts repeat.

When to call service

If it restarts several times a day, or after any restart that left the product in a wrong state.

Related codes

• power.supply-unstable H-02002: Power supply unstable
• software.crashed H-06002: Crashed
• software.crash-loop H-06003: Crash loop
• performance.too-hot H-05005: Too hot

Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written HEART storage.full. Things that simply happen, such as system.started, are event types, not faults. The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7. All of it, as data: fault-codes.json.

All fault codes, by area · All fault codes, by H-number · Problem types (API errors)