Volumio x86 OTA Update Failure – Incorrect OTA Package Delivered (Only ~1 MB Instead of Full Image) + Update Process Always Fails

Platform

  • Device: x86_64 PC
  • Volumio Version: 4.071
  • Target Update Version: 4.073
  • Kernel: 6.12.57-volumio #2 SMP PREEMPT_DYNAMIC Thu Nov 13 17:08:37 CET 2025
  • Storage: Volumio installed to internal disk
  • Test Mode: disabled
  • Alpha Mode: disabled

System Log (required by Volumio guidelines)

:point_right: System log link: http://logs.volumio.org/volumio/YVb1y7g.html


Summary of the Issue

When updating Volumio x86_64 from 4.071 to 4.073 using the built‑in OTA updater, the update always fails, even though the UI incorrectly reports “Update completed successfully”.

After reboot, the system remains on 4.071.

Detailed analysis shows that the OTA server is delivering an invalid update image — a file named:

/data/volumio_pc.img.zip

with a size of only ~951 KB, which is far too small for a complete x86 system image (normally 300–600 MB).
Because of this, the updater cannot extract or apply the update and aborts with an error internally.

This issue is reproducible on multiple x86 devices.


Steps to Reproduce

  1. Start with Volumio x86 version 4.071
  2. Run OTA update from UI or via SSH:
volumio updater forceupdate
  1. Updater shows:
  • “Starting update”
  • “Preparing update”
  • “Update completed successfully”
  1. System reboots automatically
  2. After reboot, system is still on 4.071
  3. Checking /data reveals a corrupted / incomplete OTA package:
-rw-r--r-- 1 volumio volumio 951K volumio_pc.img.zip

Actual Behavior

  • OTA server delivers a ~951 KB file instead of a full system image
  • Updater logs show internal failure:
PROGRESS: 100, STATUS: "Error", MESSAGE: "Error: update failed, please restart system and retry"
  • UI incorrectly reports update success
  • Device reboots
  • System stays on version 4.071

Expected Behavior

  • OTA server provides a valid full system image for x86_64
  • Updater downloads and applies it
  • Device updates to 4.073 without requiring full reinstallation

Log Excerpts

From volumio-remote-updater.service:

PROGRESS: 0, STATUS: "Starting update", ETA: "6m"
PROGRESS: 5, STATUS: "Preparing update", ETA: "5m"
PROGRESS: 100, STATUS: "Error", MESSAGE: "Error: update failed, please restart system and retry"

File cleanup errors:

/bin/rm: cannot remove '/imgpart/rck*': No such file or directory
/bin/rm: cannot remove '/imgpart/*.part': No such file or directory
/bin/rm: cannot remove '/imgpart/*.zs-old': No such file or directory

Test/Alpha mode confirmation:

Test mode disabled
Alpha mode disabled
Alpha legacy test mode disabled

Version check after failed update:

VOLUMIO_VERSION="4.071"
uname -a
Linux volumio-kinderzimmer 6.12.57-volumio ...

Technical Analysis

  • The OTA package delivered from the update API is not a valid image
  • Size is 951 KB instead of hundreds of MB
  • Therefore the update cannot proceed
  • Error is thrown before extraction or installation
  • UI incorrectly reports success
  • System reboots without updating

This strongly suggests a server-side issue with the x86_64 update package provided by:

https://api.volumio.org/update/check/volumiov2/x86_64

Likely causes:

  • Wrong image linked for x86 builds
  • Corrupted or partial delta package
  • Incomplete upload on the update server

Impact

  • x86 users cannot update via OTA
  • Only workaround is full reinstall, which results in:
    • loss of configuration
    • loss of plugins
    • loss of multiroom settings
    • loss of network and library setup
  • This makes the official OTA update mechanism unusable for x86 devices

Request

Please check:

  1. The OTA update definition for x86_64
  2. The file served at the update URL
  3. Whether an incomplete delta or wrong platform image is being delivered
  4. Whether the published 4.073 OTA package for x86 is corrupted or missing essential content

This issue is reproducible across multiple systems and appears to be server-side.

A fix would allow x86 users to update without reinstalling.

Hi everyone,
just a short addition from my side:

I’m running two different Volumio x86 systems here ( both installed on internal storage), and I can reproduce the exact same update issue on both devices.
So it doesn’t seem to be related to one specific machine or a local configuration problem.

If you need any extra logs or tests from my side, just let me know.
Thanks a lot for having a look at this! :blush:

Could you please check local space with df -h and show here?

Hey,
Yes of course

# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            899M     0  899M   0% /dev
tmpfs           188M  8.4M  180M   5% /run
/dev/mmcblk1p2  5.2G  1.2G  3.7G  25% /imgpart
/dev/loop0      1.2G  1.2G     0 100% /static
overlay          52G  1.1G   48G   3% /
tmpfs           940M     0  940M   0% /dev/shm
tmpfs           5.0M   12K  5.0M   1% /run/lock
efivarfs        120K  115K   333 100% /sys/firmware/efi/efivars
/dev/mmcblk1p1  366M   91M  275M  25% /boot
/dev/mmcblk2     59G   39G   18G  69% /media
tmpfs           940M   18M  922M   2% /tmp
tmpfs            20M   92K   20M   1% /var/log
tmpfs           940M     0  940M   0% /var/spool/cups
tmpfs           940M     0  940M   0% /var/spool/cups/tmp
tmpfs           188M     0  188M   0% /run/user/1000

Hi,

the log you submitted, was this taken immediately after the update and before the reboot, or after the reboot when you discovered it was still on 4.071?

My impression is after the reboot, we need a log from after the update and before the reboot.
Preparing a 4.071 setup now to check whether I can reproduce your issue.

EDIT
On an HP Pavilion and a Lenovo Yoga 520 the update from v4.071 to v4.073 works without issues.
In other words, I can’t reproduce the error.

The following scenario should allow you to produce a log before the reboot

  • boot from a clean v4.071
  • ctrl-alt F1 gives you a terminal
  • logon with volumio/volumio and execute
sudo mv /bin/systemctl /bin/systemctl_       (sudo pwd is volumio)
sudo mv /sbin/reboot /sbin/reboot_
  • switch back to the UI with ctrl-alt F2
  • perform the update, afterwards reboot won’t work and the UI crashes
    (the crash restart won’t harm the log info though)
  • NOTE: wait 15-20 secs until the UI restarts
  • submit the log now
  • finish with ctrl-alt F1 and
sudo mv /bin/systemctl_ /bin/systemctl
sudo mv /sbin/reboot_ /sbin/reboot
  • then reboot