Sorry Nerd. I was a bit frustrated, as things had been running so well. I’m thinking maybe my SD card has seen better days and caused some corruption. I have ordered a new one and I will sent logs for sure if and when it happens.
ive tried, but still the harddisk is not editable. Also are the rights changed. Wenn i wil edit the rights i got the same errorcode 3 . the strange behavour is since the update to 4.067. at the last volumio 3 it was working pretty fine
We’re live!!!
Volumio 4.067 is now available for Raspberry Pi and PC platforms.
This beta thread has been an incredible journey. Your testing, bug reports, suggestions, and patience made this release possible. Nerd, Wheaten, Balbuze, Ash, and everyone who participated in testing, thank you. We literally couldn’t have done this without you.
We’re moving feedback and discussion to a new thread dedicated to Volumio 4:
You’ll find it pinned in the forum. If you run into issues, have questions, or want to share your experience with the new release, that’s the place. But before we do, we wanted to say thank you here, where it all happened.
This community is what makes Volumio special. Thanks for being part of this journey. Let’s see what we can build together on this foundation.
5 Likes
Hey @Dick_van_der_Wal,
The issue is clear from your log: both drives have dirty filesystem flags from improper unmounts. This causes the “error code 3” you’re seeing.
Why This Happens Now (Volumio 4.067):
Volumio 3 ran on Debian Buster with older kernel and filesystem drivers that were more forgiving of dirty mounts. Volumio 4 runs on Debian Bookworm with kernel 6.12.47 and newer exFAT drivers that strictly enforce filesystem integrity protection. The drives are blocked from writes to prevent corruption.
What Causes Dirty Mounts:
- Power interruptions during file transfers
- Disconnecting drives without proper unmount
- System crashes or freezes
- Impatient shutdowns during write operations
The Fix (Windows Only):
You must connect each problematic hard disk to a Windows PC:
- Safely shut down Volumio
- Disconnect the hard disk from Raspberry Pi
- Connect to Windows PC via USB
- Windows will automatically detect filesystem errors and show a notification
- Click “Scan and fix” when Windows prompts you
- Wait for repair to complete
- Right-click drive icon, select “Eject”
- Disconnect from Windows
- Reconnect to Raspberry Pi
- Power on Volumio
Repeat for the second drive if needed.
Important:
This is the only reliable fix. Linux filesystem repair tools require advanced knowledge and are not recommended for your situation. If you cannot access a Windows PC to perform the repair, the drives will remain write-protected.
Kind Regards,
Dear Volumionauts,
THE VOLUMIO 4 JOURNEY From Alpha to Release - A Seven-Month Build
April 22, 2025 - Alpha Begins (v0.058) “Audio Without Compromise” - not just a tagline, but a technical manifesto.
The announcement was clear: this was not a simple OS bump. Debian Buster to Bookworm required months of custom build engineering, core package refinement, and architectural realignment. The mission stayed the same - bit-perfect playback without compromise - but everything underneath had to be rebuilt.
The Alpha opened with a challenge: Raspberry Pi and x86 platforms, targeting the latest Pi 5 and NVMe boot support. The community was asked to test everything: I2C DACs, SPI displays, GPIO buttons, USB audio, CD playback, multiroom, and strict A2DP Bluetooth with BlueZ-ALSA. No PulseAudio. No compromises.
The devs had poured countless hours into kernel rebuilds, plugin surgery, D-Bus battles, and Bluetooth wrangling.
The call went out: “Flash it. Boot it. Break it gently. Tell us what works and what doesn’t.”
The community responded. Jumped in within hours - Pi 3B+ with Allo DigiOne, confirming Play Here, Spotify, YouTube Music, and Radio Paradise all working. Validated Pi 5 with NVMe and Cambridge DACMagic 200M. Dove into plugin testing, surfacing Touch Display and IR controller issues that needed attention.
The feedback loop started turning.
Through late April and May, the builds accelerated:
- v0.060: OTA infrastructure first appeared
- v0.061: WiFi and hotspot fallback logic overhauled
- v0.065: Kernel updated to 6.12.28
- v0.066: Time service improvements, Realtek driver stack expanded
- v0.067: Partition layout updated for OTA support
- v0.068: KMS/framebuffer enabled, ACPI keymap fallback implemented
- v0.069: Custom firmware injection, rfkill handling refined
Every release brought fixes. Every fix came from real-world testing reports.
June 2, 2025 - Beta Launch (v4.010) The Alpha graduated. A new numbering scheme. A new partition layout. A clean slate for the public beta phase.
The foundation was solid, but the work was far from done. What followed was not just testing - it was collaboration at scale.
Through summer and fall, the community brought forward issues no lab could replicate. CD-ROM playback quirks. SMB race conditions. Bluetooth timing issues. MPD metadata mysteries. Service initialization sequencing problems. Each report became a stepping stone.
The team responded with surgical precision:
- MPD evolved through three major revisions (0.24.5 pre-release to 0.24-6)
- Kernel updates kept pace with upstream stability (6.12.34, 6.12.35)
- Service initialization was reorchestrated for reliability (alsa-restore, volumio.service dependencies)
- Boot performance optimized (Samba winbind/nmbd sequencing)
- Platform-specific refinements for both Pi and x86
- Third-party integrations stabilized (TIDAL Connect, Qobuz Connect, WebRadio)
17 beta releases followed. Each one built on the last. Each one informed by real user logs, real hardware configurations, real edge cases.
November 10, 2025 - Volumio 4.067 Released What started as an Alpha experiment with 10 downloads became a production-ready platform trusted by thousands.
Seven months. 26+ releases across Alpha and Beta. Hundreds of test reports. Thousands of log lines analyzed. The feedback loop never stopped, and it worked.
To the dev team - the kernel work, the custom firmware injection, the service-level orchestration, the plugin migration - all of it matters.
To devs, volunteers, and every community member who flashed an Alpha build with 10 total downloads, who sent logs when things broke, who confirmed when things worked, who tested on hardware the devs didn’t have access to: this release exists because you showed up.
The community didn’t just test Volumio 4. You built it with us.
The Alpha thread served its purpose. The Beta thread served its purpose. Now the real work begins.
Audio without compromise. A foundation built to last.
Kind Regards,
17 Likes