One Song Wouldn't Play. 231 Files Were Broken. Lidarr's Ogg Tag Writer Was the Culprit.
On September 11, 2026, one song would not play. The client just retried it, in a loop, forever. Not a silence, not an error dialog — a little spinner that never resolved. I’d seen that behavior before, and I’d always blamed the server. This time the server was fine, and the truth was stranger: Lidarr had been quietly corrupting my Ogg Vorbis files for months, nightly, one byte at a time.
The setup is a normal homelab. Music lives on the NAS (.12, ZFS) and is served by Navidrome on .21, which streams the raw file — transcoding is off — to a desktop client called Supersonic. Lidarr 3.1.0.4875, also on .21, manages the library. Somewhere along the way I’d set “Write Metadata to Audio Files” to Sync (writeaudiotags = Sync, scrubaudiotags = True), which means every nightly Refresh Artist rewrites tags and embeds cover art directly into the files themselves.
That setting is the whole story. It turned a metadata tool into a corruption machine.
"My NAS Is Out of RAM and My Download Is Stuck" — Two Homelab Myths, Debunked
Two things happened on the same day that looked like problems and weren’t — at least not the problems they appeared to be. My NAS was reporting almost all its RAM in use, which sounds like a leak or an imminent crash. And a TV show I’d grabbed through LunaSea on my phone had downloaded fine but then “wouldn’t import” into the library, which sounds like a broken automation pipeline.
Both are among the most common false alarms in a self-hosted media stack. Neither was what it looked like. Here’s what was actually going on, and the real fixes.