32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
# Supported systems have at least 16 GB of RAM
|
|
|
|
**Date:** 2026-09-04
|
|
**Status:** active
|
|
|
|
## Context
|
|
|
|
EASY-BEE boots the live image with `toram`. The compressed live medium is
|
|
copied into RAM before the root filesystem is used. During investigation of a
|
|
boot failure, the large squashfs copy was observed to stop part-way through.
|
|
|
|
The servers in scope are not low-memory systems. The minimum supported
|
|
hardware configuration has 16 GB of installed physical RAM.
|
|
|
|
## Decision
|
|
|
|
- EASY-BEE targets and supports systems with at least 16 GB of installed RAM.
|
|
- Capacity below 16 GB is outside the supported hardware envelope.
|
|
- A mid-copy `toram` failure on supported hardware must not be attributed to
|
|
insufficient total RAM without direct evidence such as `ENOSPC`, an OOM
|
|
event, or an unexpectedly restricted tmpfs.
|
|
- Diagnostics must preserve the actual copy/read error so media transport,
|
|
virtual-CD disconnects, and I/O failures can be distinguished from memory
|
|
exhaustion.
|
|
|
|
## Consequences
|
|
|
|
The approximately 2.8 GB live medium has sufficient capacity headroom on
|
|
supported systems. Current v14 boot investigation therefore treats the
|
|
part-way SquashFS copy failure as a source-media or virtual-media read-path
|
|
failure unless boot logs provide explicit evidence of memory exhaustion.
|