What Happened on the TerraMaster F2-425
The user installed ZimaOS 1.5.3 on an NVMe drive connected through the NAS's internal USB path. The system booted, but later became partially unresponsive, apps appeared as legacy/zombie entries, and shutdown could hang. The user attached diagnostic output showing an Intel Celeron N5095 system with 4 GB of memory.
Why the Storage Path Was the Main Suspect
A community reply suspected the OS and Docker storage path over USB rather than Jellyfin or Transmission individually. That was an inference, not an official compatibility statement. The useful evidence came later: after reinstalling ZimaOS onto one of the SSDs, the user reported that it was working fine.
Logs to Capture Before Power-Cycling
Useful commands from the thread were dmesg -T | tail -200, journalctl -p err -b, and journalctl -u docker --no-pager. systemd documents journal filtering in journalctl documentation, while the Linux kernel documents message output through kernel bug-hunting guidance.
What This Case Actually Demonstrates
It does not prove that every USB-based ZimaOS installation will crash. It demonstrates that changing this user's OS storage path coincided with stable operation and is therefore a strong case-specific diagnostic clue. For supported installation flow, use the current ZimaOS installation guide and current storage guide.
