HEART storage.corrupted H-04005
Storage corrupted. Stored data or the file system is damaged.
| Code | HEART storage.corrupted; inside a message "code": "storage.corrupted" |
|---|---|
| H-number | H-04005: area 04, code 005 |
| Area | storage: Disk, memory cards, databases |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Anything that stores data |
Likely causes
- Power lost while writing.
- A failing card, disk or flash chip.
- A software bug that wrote bad data.
- A card removed while in use.
How to fix or prevent it
- Stop writing to it, so nothing more is lost.
- Run the file-system check or the product's repair tool.
- Restore from the last good backup.
- Replace the storage if it keeps happening.
- To prevent it: a stable supply, and safe removal of cards.
What the HEART does by itself
It raises an error alert, stops using the damaged data where it can, and falls back to defaults or the last good copy if the product has one. It tells a person.
When to call service
If the product will not start properly, or data that matters cannot be restored.
Related codes
storage.write-failedH-04003: Write faileddata.integrity-failedH-10005: Data integrity check failedpower.supply-lostH-02001: Main power lost
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)