HEART storage.write-failed H-04003
Write failed. Data could not be written, for a reason other than being full.
| Code | HEART storage.write-failed; inside a message "code": "storage.write-failed" |
|---|---|
| H-number | H-04003: area 04, code 003 |
| 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
- A memory card or disk is failing, or was removed.
- The file system was switched to read-only after an error.
- Wrong permissions on a folder.
- A network drive or database that is not reachable.
How to fix or prevent it
- Check that the card or disk is in place and seated well.
- Check the file system for errors, and its permissions.
- Replace a card or disk that keeps failing.
- Restore from backup if data was damaged.
What the HEART does by itself
It raises an error alert with the path or store that failed, and may retry. It cannot repair hardware. It resolves when writes succeed again.
When to call service
If the store is built in, or writes fail after the card or disk has been replaced.
Related codes
storage.corruptedH-04005: Storage corruptedstorage.wearing-outH-04004: Storage wearing outstorage.fullH-04002: Storage full
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)