HEART storage.full H-04002
Storage full. Storage is full. Writing new data fails.
| Code | HEART storage.full; inside a message "code": "storage.full" |
|---|---|
| H-number | H-04002: area 04, code 002 |
| Area | storage: Disk, memory cards, databases |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Cameras, recorders, servers, gateways, anything that stores data |
Likely causes
- A
storage.nearly-fullwarning was not acted on. - A fault writes far too much, such as a log in a tight error loop.
- Recordings not collected, so the card filled.
- A backup or update that needs more space than there is.
How to fix or prevent it
- Free space now: move or delete old recordings, logs and temporary files.
- Find what filled it: look at the biggest and newest files.
- Fix the cause if one program writes too much, then set retention limits.
- Fit a larger card or disk.
- To prevent it: act on
storage.nearly-full, and keep automatic clean-up switched on.
What the HEART does by itself
It raises an error alert. New data is being lost, so it may also raise system.main-function-lost if the main job needs storage, such as a camera that cannot save pictures. A Playbook may rotate logs or remove temporary files. It resolves when writing works again.
When to call service
If space cannot be freed, or it fills again soon after.
Related codes
storage.nearly-fullH-04001: Storage nearly fullstorage.write-failedH-04003: Write failedsystem.main-function-lostH-01001: Main function 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)