Homelab / Technical documentation
Failures, investigations and bounded conclusions.
Dated records preserve the symptom, action, observed outcome and what the evidence cannot establish.
Jump to a section
27 September · USB / ext4 interruption
Recovered report · S06. The external disk disappeared during a USB/xHCI interruption. Consumers were stopped; the unmounted filesystem was checked, remounted read/write and services resumed. Exit status 0 and a subsequent error-free observation window were reported.
The Bluetooth troubleshooting step is correlation, not a proven root cause. The result does not prove a lasting hardware repair or backup integrity. The storage triage procedure keeps device identification and mount state ahead of any repair.
Evidence: S06.
17 October · malicious process associated with Plex
Recovered report, with limited transcript corroboration. A process under a temporary path consumed roughly 365% CPU and 2.3 GiB memory. Cgroup inspection associated it with the old Plex container. The recovered account reports miner output and download attempts; the initial entry route remains unknown.
- Disabled automatic restart and stopped the old container; the process disappeared afterward.
- Inspected filesystem/process state, preserved suspect artifacts with hashes and backed up roughly 3.2 GB of Plex configuration.
- Created a replacement Plex instance and reported successful registration and library recovery using an earlier database backup/repair path.
- Reported read-only media mounts and removal of the public Plex port exposure; left the old instance stopped.
docker update --restart=no plex
docker stop plexA separate described transcript confirms the old image/restart policy and a scoped process sweep without matching indicators. That sweep is not proof the host was clean, persistence was absent or the incident was fully eradicated. No particular vulnerability, complete forensic examination or host rebuild is asserted.
Original artifacts, hashes, account information and network details remain private. The exact database-repair commands were not recovered and are not reconstructed as a recipe.
Evidence: S07.
23 October · container DNS divergence
Recovered report. Sonarr resolved the failing target after explicit resolver configuration and recreation. Other container results varied. The later daemon file passed syntax validation without established activation.
The confirmed outcome is the tested Sonarr lookup. The DNS page separates host, container, network and daemon layers.
Evidence: S10.
3 November · LG playback stall
User-confirmed workaround in recovered history. Playback on an LG Plex client stalled after approximately 10–15 seconds; Force Direct Play worked in the reported test.
This is a client-specific workaround, not a proven codec/network root cause or a global recommendation. It must remain separate from the later investigation of conversion-related storage contention.
19 October · image packaging failed after frontend build
The frontend compiled, then the old image failed while copying a missing build-stage data directory. The newer source and successful November deployment record are a separate continuation of the project. See the source comparison.