OTA update fails after changing default album art

Help and Support Help
1

Without realizing it would cause future OTA system updates to fail due to “user modified files”, I changed the default albumart file located at </volumio/app/plugins/miscellanea/albumart/default.png> to a B&W version of the same default image.

I did not save a copy of the original file (stupidly). Do I have any chance of reverting my change so OTA updates can proceed? Obviously I would prefer to avoid a system reset.

Is there a different/better way to change the default albumart image without causing this problem?

Thanks.

2

hi!
via ssh you can try

volumio updater restorevolumio

then update

3

Thanks for the reply. Doesn’t appear to have worked properly:

~$ volumio updater restorevolumio
Deleting Overlay content of /volumio folder
Mounting overlay partition
Overlay partition mounted
Deleting /volumio folder on overlay
Deleting /myvolumio folder on overlay
Could not restore volumio folders: Error: Command failed: [ -d /mnt/overlay/dyn/myvolumio ] && /bin/rm -rf /mnt/overlay/dyn/myvolumio

I gave it a second try, for good (?) measure:

~$ volumio updater restorevolumio
Deleting Overlay content of /volumio folder
Mounting overlay partition
mount: /mnt/overlay: /dev/mmcblk0p3 already mounted on /mnt/overlay.
Could not restore volumio folders: Error: Command failed: /usr/bin/sudo /bin/mount /dev/mmcblk0p3 /mnt/overlay
mount: /mnt/overlay: /dev/mmcblk0p3 already mounted on /mnt/overlay.

In either case, OTA update still fails. Any other ideas? Or am I doomed to a factory reset?

4

You can try:
volumio updater forceupdate

It’s a double-edged sword: it can be helpful in forcing an update if something’s stuck or corrupted, but it bypasses the usual safety checks, which can lead to incomplete installs, broken dependencies, or even rendering the system unusable.
Then you still need to force a factory reset.

1 Like
5

I ended up reverting to an earlier system backup on a separate SD. It’s been a while since I’ve needed to do that which is obviously a good thing. Volumio is so much more stable than it was when I started using it ~2018, and this instance was my own fault.