Volumio 4 Installation FOMO March 2026

Help and Support Help
1

What are the current bugs, work arounds and things just blain broken on the current version available for download on Volumio?

Did a clean install to have a Pi 4 device attached to a new TV in a spare room and HDMI audio is a total hit or miss basket case.

I’d like to use Now Playing if it’s workable in this scenario currently.

UPDATE - So now I’ve gone from 5 working Volumio Pi devices to 2. Three of them I was moving/changing the case, etc. and decided to do a fresh install.

HUGE mistake. The remaining two work fine but I cannot get the other 3 (2 Pi 4 and one Pi 5) to work with new image. HDMI does not work on any. All have horrendous lag. Installing plugins, like Touch Display, takes 10+ minutes. No changes in network - connecting devices via ethernet since configuring WiFi also still seems broken.

Is there a way to export teh image on one of my working devices or an archive available?

3

Hey @Rochambeaux,

The current official Volumio download is version 4.103. You should report the version number, not ask community to locate it.

If these are fresh installs from a current download, your devices should report 4.103 in Settings > System > System Version.

Before any troubleshooting can proceed:

  1. Hardware inventory for each of the 5 devices:

    • Pi model and revision
    • Storage type (SD card brand/model, or NVMe/USB)
    • Audio output (HDMI, HAT, USB DAC - specify which)

  2. What version do your 2 working devices report?

  3. What version do your 3 problematic devices report?

  4. Log link from each of the problematic devices via http://volumio.local/dev > Send Log

Without this information, no investigation is possible. You know the drill by now from the beta works.

Kind Regards,

4

On a lark I burned an image using the Pi Imager and chose Volumio through the Media Player OS options. It looks to be a bit older than the version on Volumio site. Did this on Pi 5 and boom!

Everything works, including getting WiFi option at setup.

Note that is the ONLY difference in the processes. Going to try the Pi 4 today using the same process.

5

The Pi 5 is working with WiFi and Qobuz and Tidal. Spotify connect and Youtube Cast Receiver and Roon bridge will “connect” but the media will not start.

http://logs.volumio.org/volumio/IAtIkjj.html

6

Hey @Rochambeaux,

The log shows the problem clearly:

VOLUMIO_VERSION="3.912"
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
Machine model: Raspberry Pi 5 Model B Rev 1.0

This is Volumio 3, not Volumio 4. Raspberry Pi Imager’s “Media Player OS” option served you an outdated V3 image.

Volumio 3 supported Raspberry Pi 5 but without RP1 support - the new southbridge chip that handles much of the Pi 5’s I/O including USB, ethernet, and GPIO. This limitation means V3 on Pi 5 is a compromised configuration. The HDMI audio problems, streaming failures (HTTP 403 errors on YouTube), and “Device or resource busy” errors in the MPD log are symptoms of this mismatch.

The fact that WiFi “works” on this install is coincidental - V3 has completely different network code than V4. This does not indicate V4 has WiFi problems.

Correct Installation Method

  1. Download the current Volumio 4 image directly from Get Started - Volumio
  2. Flash using Raspberry Pi Imager - select “Use custom” and choose the downloaded image
  3. When prompted with OS Customisation options (hostname, WiFi, SSH settings) - click “No” and skip this entirely. Using OS Customisation corrupts Volumio’s first-boot initialization
  4. Boot the Pi with the freshly flashed media and complete setup through the Volumio wizard

Detailed instructions are here:

Once you have Volumio 4 installed correctly on your Pi 5, if WiFi or HDMI problems persist, provide a fresh log and we can investigate from there.

Kind Regards,

7

So that’s what I originally did but ran into the slew of issues stated at top. Is there a known issue in using Balena to create the Volumio 4 image?

8

Yes. 80% of the images flashes with Balena are causing all kind of issues.

9

So ignore the initial step in the Pi Imager of selecting the hardware type and go straight to OS → Custom?

10

Multiple Pi 5 problems still:

Log: http://logs.volumio.org/volumio/bI1vXuh.html

using image: Volumio-4.103-2026-03-06-pi.img
Created using Pi Imager as directed above.

First Issue: Qobuz will not connect. After credentials comes back with “Bad Request”.
Tidal connect does work and plays.

Second Issue: Roon Bridge installs but playback results in “too many failures”

I have stopped here as these were the same issues I encountered from the start. Since Balena is out of the mix I’m guessing there are issues with this current image as the version 3 image that the Pi Imager installed when selecting from “Media Player OS” seemed to function in more areas except Roon Bridge and Spotify also do not work.

http://logs.volumio.org/volumio/Aa9wMkq.html

At this point should I shelve the Pi 5 as an unstable platform?

11

Volumio on PC hardware (specs below). Also version 4.103 clean install.

Experiencing many of same issue on Pi 5 and Pi 4:

http://logs.volumio.org/volumio/sxwVeNz.html

Spotify won’t stay connected.
Qobuz will not authorize
Roon bridge no audio. Originally all tried via HDMI but install a USB- to TOSLINK and even tried the internal PC speaker. No output on any.

System Information

  • OS info

  • Version of Volumio: 4.103

  • Hostname: cortez1519

  • Kernel: 6.12.57-volumio

  • Governor: performance

  • Uptime: 0 days, 0 Hrs, 17 Minutes, 54 Seconds

  • Network info

  • Interface: wlan0

  • IP Address: 192.168.50.180

  • MAC Address: 90:de:80:38:46:7f

  • Type: wireless

  • Speed: 960.7 Mb/s

  • Audio info

  • Hw audio configured: DSD TECH USB Audio Device

  • Mixer type: Software

  • Number of channels: 2

  • Supported sample rate: 44100 48000 96000

  • Board info

  • Manufacturer: HP

  • Model: HP Elite Slice

  • CPU info

  • Brand: Core™ i7-7700T

  • Model name: Intel(R) Core™ i7-7700T CPU @ 2.90GHz

  • Speed: 2.9 GHz

  • Family: 6

  • Model: 158

  • Number of cores: 8

  • Physical cores: 4

  • Average load: 5%

  • Temperature: 56°C

  • Memory info

  • Memory: 24501768 Ko

  • Free: 21725848 Ko

  • Used: 2775920 Ko

  • Software info

  • MPD version: Music Player Daemon 0.24.6 (b6f106b+)

  • Bluetooth capabilities version: 5.83

  • AirPlay version: AirPlay 2

  • UPnP renderer: upmpdcli 1.9.14-1~ppa1~bookworm

  • Storage info

  • INTERNAL storage - Size: 473893MB

  • Used: 585MB

12

Hey @Rochambeaux,

Your Pi 5 log (bI1vXuh.html) reveals several issues.

MPD Database Corrupted

Mar 06 10:47:11 volumio mpd[1837]: exception: Database corrupted

This is your primary problem. When the MPD database is corrupted, playback fails, the queue breaks, and streaming services cannot feed tracks to the player.

To fix:

sudo rm /var/lib/mpd/tag_cache
sudo systemctl restart mpd

After MPD restarts, re-authenticate your streaming services.

DNS Resolution Failures

Your log shows repeated DNS failures during boot. Volumio works fine on thousands of installations - systematic DNS failures indicate a problem with your local network, not Volumio. Check your router’s DNS settings. If your router provides DNS, ensure it is functioning correctly. Some users find better results using a public DNS like 8.8.8.8 or 1.1.1.1 configured on their router.

NMBD Name Registration Failed

If you are using NAS shares, go to Settings > My Music > Sources, edit your NAS entry, and under Advanced Options set:

vers=2.1

Do Not Shelve the Pi 5

Your x86 system shows the same pattern. This is not a Pi 5 hardware problem - it is a local network configuration issue.

Kind Regards,

13

Hey @Rochambeaux,

Your x86 log (sxwVeNz.html) tells a clear story.

Boot Partition Filesystem Corruption

FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt.

This happens when you power off without using Settings > Shutdown. Fresh flash required.

DNS Resolution Failures

Your log shows Spotify failing repeatedly with “device or resource busy” on DNS lookups, and OAuth token refresh failing the same way. This is not a Volumio problem - Volumio works fine on thousands of installations.

Systematic DNS failures across both your Pi 5 and x86 systems point to your local network DNS configuration. Check your router’s DNS settings. Some routers have DNS caching issues or rate limiting that causes this behaviour.

Tidal Connect Works

Your log confirms Tidal played successfully at 17:54:44. Your audio hardware is fine.

NMBD / NAS Shares

If using NAS shares, set vers=2.1 in Advanced Options under Settings > My Music > Sources.

Recommendation

  1. Fresh flash - do not attempt to repair the corrupted filesystem
  2. After flashing, let the system boot completely before interacting
  3. Always use Settings > Shutdown
  4. Investigate your router’s DNS configuration

Kind Regards,

14

I’ve wasted so much time the past 4 days trying to get the newest version to work on Pi 4, Pi 5 and PC hardware.

My 2 existing Pi devices running 4.084 are working perfectly

UPDATE

I put a known working Pi400 into the mix.

So 4 different HW platforms (Pi 4, Pi400, Pi 5 and PC) all known and tested working recently.

Have cycled in 8 different SD Cards, from 32GB, 64GB, 128GB and 256GB - all previously have run prior versions of Volumio.

Over 25+ clean images and installs across these devices.

The only thing that works reliably and plays through HDMI is Tidal Connect.

Qobuz, Spotify, Roon, YouTubeMusic are hit or miss (almost always a miss). Switching to a USB-DAC will sometimes get Roon to work on some of the platforms.

Wifi connections made after ethernet start-up are also unreliable.

Pi 4 response times are horrible - screen load times take forever, if they happen at all.

Have tried enabling Plugin Test Mode and various combinations but no luck.

If someone has a copy of the IMG file other than Volumio-4.103-2026-03-06-pi I would greatly appreciate it. Only older ones I have are pre 4.0 but at this point I’m desperate enough to finish this project I may load Ver 3 just to get something resembling a working unit.

15

Hey @Rochambeaux,

You have posted about this issue across multiple threads. Log analysis takes time - volunteers have day jobs and families. Creating separate posts for the same underlying problem fragments the investigation and wastes everyone’s effort.

I have analyzed both logs you submitted (bI1vXuh.html for Pi 5, sxwVeNz.html for x86).

The Common Pattern

Both systems show systematic DNS resolution failures during boot. Your x86 log shows Spotify failing 12 consecutive times with “device or resource busy” on DNS lookups. OAuth token refresh fails the same way. NTP cannot resolve pool servers.

Volumio works fine on thousands of installations. When we see identical DNS failures across multiple hardware platforms - Pi 4, Pi 5, Pi 400, and x86 - the problem is not Volumio. The problem is your local network.

Check your router’s DNS configuration. Some routers have DNS caching issues, rate limiting, or simply unreliable DNS forwarding. Try configuring your router to use 8.8.8.8 or 1.1.1.1 as upstream DNS.

Tidal Connect Works - Why?

Your x86 log confirms Tidal played successfully. Tidal Connect works because the Tidal app on your phone pushes to the device - Volumio does not need to initiate outbound connections. Qobuz, Spotify, and Roon all require Volumio to reach out and authenticate, which fails when DNS is broken.

Additional Issues

Your x86 boot partition has filesystem corruption from improper shutdown. Fresh flash required - and always use Settings > Shutdown, never pull power.

Your Pi 5 has a corrupted MPD database. After fixing the network issue:

sudo rm /var/lib/mpd/tag_cache
sudo systemctl restart mpd

If using NAS shares, set vers=2.1 in Advanced Options under Settings > My Music > Sources.

Next Steps

  1. Fix your local network DNS
  2. Fresh flash on the x86
  3. Test one device at a time
  4. Submit one log, in one thread

A link to 4.084 is https://updates2.volumio.org/pi/volumio/4.084/Volumio-4.084-2025-12-25-pi.zip but rolling back will not help until your local network DNS is sorted.

Kind Regards,

16

Below is the log from this mornings test of the Pi 4:

http://logs.volumio.org/volumio/W4yU1p5.html

Followed the exact same process as previous attempts using current Volumio 4 image but this time used 4.084. Flashed to one of the SD Cards used in failed attempts previously.

Flash card using Balena - I know Pi Imager was recommended but I tried it and Balena on 4.103 attempts with same results. I have always used Balena in the past and my currently working 4.084 devices were setup that way.

Pi 4 connected with an approved Pi 5 PSU.
Using Ethernet connection (Google Fiber is ISP)
Connected via HDMI to small display (test display I’ve used past 2 years without issues).

  1. Device Boots quickly to QRcode screen
  2. Proceed through initial setup - interestingly it “auto logged” me into Volumio and recognized Premium account.
  3. On Music Sources during initial setup I configured Tidal. Authentication fast and successful.
  4. Next tried Qobuz - same result. I had previously tried the DNS trick of 8.8.8.8.and 1.1.1.1 on previous attempts with no luck. Because everything else on my network is connecting and resolving perfectly (including 2 other Volumio devices running 4.084 I am not inclined to make router or network changes.
  5. Everything else to this point was very responsive.
  6. Installed Touch Display Plugin
  7. Installed Now Playing Plugin
  8. Again, VERY responsive and when when I click on “Settings” the screens pop up instantly. On 4.103 they would lag or remain blank.
  9. Set Touch Display settings to Screensaver = 0 and No Screensaver
  10. Change Now Playing to Kiosk - Switches over immediately.
  11. Test Tidal as SOURCE from Volumio. Display and sound over HDMI
  12. Install Roon Bridge Plugin and setup Audio device in Roon
  13. Test play from Roon app on PC over LAN - Display and sound over HDMI works perfectly.
  14. Install Spotify Plugin and authorize
  15. Test play Spotify from SOURCE from Volumio (not phone) - display and sound works perfectly.

Additional Updates

  1. Spotify from Android phone works smoothly.
  2. YouTube Cast Receiver PLugin Installed. Can connect Spotify app via Cast Receiver but will not play.
  3. YouTube Music Plugin installed and actually accepted the cookie - that’s new, but will not play as a Source.

updated log: http://logs.volumio.org/volumio/jK0K3Nm.html

So in one simple shot I have everything working as expected, except the Qobuz authentication. I can connect to Qobuz direct via browser, Windows App and an Android phone, all over the same network so I am very confident it is not a networking issue.

The only change in above from the 25+ failed attempts before was using 4.084 instead of 4.103.

17

shouldn’t be that hard, nice to start again from fresh sometime.
I wouldn’t worry about any of the Youtube plugins, more trouble than it’s worth and still can’t get it going. Went pear shaped ever since needed to find the cookie instead of logging in, and had to download firefox at that. It’s not worth it for 128-160kbps max haha. I’ve got a Chromecast Audio or Bluetooth for that, don’t need to involve Volumio at all.

ps. I think if you bought one of the volumio devices you’d have a lot less problems in theory, but it’s the nature of the beast tinkering with things.

18

You know what they say, the 26th time is the charm…

The Volumio hardware is OK but TBH their OS is the only thing that interests me. There are far more capable streamer out there at 1/2 the price (or less).

19

Ha, good you sorted it out.

I’m sure that’s true, the software is great when it’s stable which is most of the time now. It’s still a bit experimental with different test modes plugin test modes, hard to know what’s what sometimes.

Yeah the hardware is pretty expensive but great we can apply the software to RPi’s etc (I’ve got a RPi4 and official 7" screen). I really hate how sensative and DIY it feels, bump any cable from the back and it stops playback and has a fit. Really don’t like the RPI cable spew. In a way it was better in the little case Flirc Case

20

Next up is Pi 5 testing using 4.084.

http://logs.volumio.org/volumio/Oqjw1H6.html

Exact same experience with Pi 4 and 4.084 as above (everything works except Qobuz) with the addition that Roon will not play to HMDI - get “Too many failures - Stopping Playback”.

Everything else installed and operates flawlessly. Did not try the You Tube Plugins as that seems to be an issue all on it’s own.

Added in a USB to TOSLINK adapter and connected headphones - Roon works fine. Something with the Pi5 and HDMI

image
image1612×207 20.1 KB

21
  1. You don’t need to download Firefox to get the cookie. Any modern browser will do.
  2. YouTube Music supports 256 kbps. So does casting from YT Music. YouTube (non-Music) is capped at 160 kbps because that’s the max it provides.
  3. Cookie login is there because Google left us with no other options.