update issue

I have to add that I forgot to unmount /mnt/overlay before I tried to update. But I would not expect that to alter /volumio and so its hash the updater gets from md5deep(?)

After I had noticed that I unmounted. The updated still failed with the message that manually edited files were detected. I then ran volumio updater restorevolumio again to no avail.

@michelangelo
Is there something you would like me to try or test in order to find the issue? Otherwise I would go on and either delete user data or do a factory reset or I might force the update without checking system integrity.

Would it be possible that you create an image of your sd card and send it to me? That would help

I have created an image of the whole sd card (32GB) now and compressed it. File size is still 2.1GB. How could I send it to you? I don’t have cloud storage like a dropbox account or the like.

wetransfer.com/ if you split it into two might work

Thanks spyking! :slight_smile:

I decided to reset user data. Volumio restarted and ran the setup wizard. Now system version is 2.457. Except from following the setup wizard and activating ssh (and changing the background image…) I did no modifications at all but ./listdynchanges.sh still results inPreparing folder structure Listing modified files find: `/mnt/overlay/dyn/volumio': No such file or directory Restoring folders
After/bin/mkdir /mnt/overlay /usr/bin/sudo /bin/mount /dev/mmcblk0p3 /mnt/overlay
cat /mnt/overlay/dyn/etc/os-release showed

No such file or directory

and df -hFilesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 2.2G 815M 1.3G 39% /imgpart /dev/loop0 235M 235M 0 100% /static overlay 27G 56M 26G 1% / devtmpfs 477M 0 477M 0% /dev tmpfs 489M 0 489M 0% /dev/shm tmpfs 489M 4.7M 484M 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 489M 0 489M 0% /sys/fs/cgroup tmpfs 489M 28K 489M 1% /tmp tmpfs 489M 0 489M 0% /var/spool/cups tmpfs 20M 52K 20M 1% /var/log tmpfs 489M 0 489M 0% /var/spool/cups/tmp /dev/mmcblk0p1 61M 37M 24M 61% /boot tmpfs 98M 0 98M 0% /run/user/1000 /dev/mmcblk0p3 27G 56M 26G 1% /mnt/overlay
cat /usr/lib/os-release showed[code]
PRETTY_NAME=“Raspbian GNU/Linux 8 (jessie)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“8”
VERSION=“8 (jessie)”
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/
SUPPORT_URL=“http://www.raspbian.org/RaspbianForums
BUG_REPORT_URL=“http://www.raspbian.org/RaspbianBugs
VOLUMIO_BUILD_VERSION=“c00a19098320053824010d132d6bfb39774a7d2f”
VOLUMIO_FE_VERSION=“e2f152c30d370c9c7c86508a02c0323bef5c243b”
VOLUMIO_BE_VERSION=“909cc76a7609428f005f8e2878227062cb5328a6”
VOLUMIO_ARCH=“arm”
VOLUMIO_VARIANT=“volumio”
VOLUMIO_TEST=“FALSE”
VOLUMIO_BUILD_DATE=“Mon Sep 17 00:18:22 CEST 2018”

VOLUMIO_VERSION=“2.457”
VOLUMIO_HARDWARE=“pi”
VOLUMIO_HASH=“cdde21c6e3d40ce352c051f661950d1b”
[/code]
Now that I have to reinstall the plugins anyway I guess I’ll start from scratch in the coming days.

Hi,

It happened to me too. Currently I’m using beta version of volumio 2.533. I could not update to any further version (including today’s release 2.542) because of integrity check failure.
Integrity script outputs:

Preparing folder structure Listing modified files find: `/mnt/overlay/dyn/volumio': No such file or directory Restoring folders
The only change I made with volumio is upload additional background image via web interface. Execution of volumio updater restorevolumio didn’t help. Any idea what is the root cause?

Yes, we might have an idea.
Thank you guys for reporting

Hi.
Update to 2.543 still doesn’t work. The same integrity issue…

+1

2.544 doesn’t work too.

Update from 2.698 to 2.699 not possible due integrity error:

Listing modified files /mnt/overlay/dyn/volumio/app/plugins/audio_interface/alsa_controller/index.js /mnt/overlay/dyn/volumio/app/plugins/miscellanea/albumart/default.jpg Restoring folders
This files does not exist. The whole folder /mnt/overlay does not exist.
How can i fix this? I have not modified any files.

Edit: I have now replaced “/volumio/app/plugins/audio_interface/alsa_controller/index.js” with the one from “volumio-2.698-2020-01-16-pi.img.zip” (in the squashfs). And now it works. :sunglasses: