System (GoSD) error codes
Every `GOSD-*` code the underlying GoSD appliance can raise, fully documented — including ones before atfs itself starts.
This page only applies when you deploy to an SD-card device.
An SD-card atfs device runs on top of GoSD, the appliance framework that
boots the board, mounts its storage, and supervises the atfs process
itself. GoSD has its own error codes, prefixed GOSD-, separate from
atfs’s own ATFS-* codes covered in Error codes.
A GOSD-* code can appear even when atfs’s own configuration is correct,
because it names a failure in the layer underneath atfs.
| Code | What happened | What the device does |
|---|---|---|
GOSD-DATA-CORRUPT | The data storage exists, but no longer holds a filesystem the device recognizes. | Halts, so the operator can recover whatever is still on the drive. |
GOSD-BOOT-MOUNT | The device could not read the SD card it booted from. | Reboots automatically after 5 seconds. |
GOSD-EARLY-MOUNT | The device could not prepare the temporary storage every later boot step needs. | Reboots automatically after 5 seconds. |
GOSD-APP-CRASH | atfs itself exited unexpectedly — a crash, or the board running out of memory. | Restarts atfs automatically. Each restart waits longer than the last. |
Note
GOSD-EARLY-MOUNT and GOSD-BOOT-MOUNT happen before the boot partition
is even mounted. Neither can ever reach the card’s LAST_FATAL_ERROR.md file, so a serial console is the only way to read one. See Read the report.
This page is hand-transcribed from GoSD’s own documentation rather than
generated from source in this repository, since GoSD is a separate
project. It was last checked against the gosd version named in this
page’s verified_against field, and may fall behind a later GoSD release.