I’ve run Volumio since 2021 on a Raspberry Pi 4 (8GB), powered 24/7. My other Pi 4s (backup/IoT servers) are rock-solid. Music source: wired Ethernet to stable Linux server (hundreds of uptime days).
Problem (happens every ~1/5 times over days or weeks): Sources > Network Drives shows red “X” on mount. “Update” rescans library but fails. Reboot gets green check, but “My Music” shows 0 items—needs second Update (10+ min total, and I am now too frustrated to listen and enjoy my music).
Presently using built-in Source mapping but in earlier days used fstab mappings and still had this problem. I have kept up-to-date versions hoping it would fix this but it still persists despite searches many times over the years.
Questions:
Does Volumio have the ability to always be ready to play my music without the issues I have described?
If it does, then what am I doing wrong and how do I fix this.
Without proper logs, it’s impossible to build a meaningful case.
So far, the only facts on the table are:
Raspberry Pi 4 – 8GB model
Connection issues
That’s not enough to diagnose or suggest fixes. Please provide logs so the story can actually be pieced together. Without logs, the only guesses left are the usual suspects: IP conflicts, bad cable, or a faulty switch, worn Storage medium.
Just to clarify my first question: putting my specific hardware aside, in general is Volumio expected to run reliably on a Raspberry Pi 4 with a hard‑wired Ethernet connection to a network music library, staying mounted and ready to play? Once I understand whether that should work reliably in principle, I can focus on gathering the right diagnostics for my setup.
Hi ,
Volumio runs reliable on a rPi4, especially with a wired connection.
Apparently your SD is damaged, as the log show this line: Nov 12 08:46:50 audioroom kernel: FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Details: Error: ENOENT: no such file or directory, stat '/volumio/app/plugins/miscellanea/albumart/icons/fa-tags.svg'
Please take a new SD and flash it with Volumio and test again.
Interesting, Wheaten. I browsed that file but missed it—it’s quite long. Thanks for pointing it out; I’ll definitely dig into it with AI assistance.
I’m not convinced this error ties directly to losing the network connection to my music server, though. That issue has cropped up multiple times over time, where only a reboot resolves it.
Yes, AI can assist, but it doesn’t have specific knowledge about Volumio’s internal state. Based on the symptoms, your SD card appears to be corrupted. This can lead to unpredictable errors because data may be written to damaged sectors. Replacing or re-imaging the SD card is the most reliable solution.
Thanks for your reply, Wheaten. I understand your comments about AI.
I ran SpinRite on the MicroSD drive, and it didn’t report any errors — though it’s possible that SpinRite’s read/write process may have cleaned things up in the process.
After that, I removed the GUI mapping and added it back to fstab.
In my original post, I asked whether anyone is running a similar setup 24/7 and what their experiences have been. Hearing from others could save me a lot of time and frustration.