[SOLVED] Update to 9.3.0 cancelled

[Venerdi]

Hi, I read this thread:


https://moodeaudio.org/forum/showthread.php?tid=7489

because I had the same problem.
Since everything seemed to work for me, I let it go.
Now I updated to 9.3.0 and I still have the same problem.
Again, everything seems to work.

20250323 113621 updater: Downloading package [update-moode9.zip]
20250323 113621 updater: Start 2025-03-21 update for moOde
20250323 113621 updater: ** Step 01-35: Remove package hold
20250323 113622 updater: ** Step 02-35: Update package list
20250323 113628 updater: ** Step 03-35: Update Linux kernel to 6.6.74
20250323 113628 updater: ** - Kernel is current, no update required
20250323 113628 updater: ** Step 04-35: Install moode-player=9.3.0-1moode1
20250323 113638 updater: ** Step failed
20250323 113638 updater: ** Exiting update
20250323 113638 updater: Install failed, update cancelled

What to do?
I am a very basic user
ciao
v.

[ils1974]

Same issue here, as well as with the upgrade to 9.2.6 from 9.2.5. before.

After the last message, the system reports it's on 9.3.0, but it's actually not.

20250323 162253 updater: Downloading package [update-moode9.zip]
20250323 162253 updater: Start 2025-03-21 update for moOde
20250323 162253 updater: ** Step 01-35: Remove package hold
20250323 162253 updater: ** Step 02-35: Update package list
20250323 162307 updater: ** Step 03-35: Update Linux kernel to 6.6.74
20250323 162307 updater: ** - Kernel is current, no update required
20250323 162307 updater: ** Step 04-35: Install moode-player=9.3.0-1moode1
20250323 162319 updater: ** Step failed
20250323 162319 updater: ** Exiting update
20250323 162320 updater: Install failed, update cancelled

[nosferatu_cat]

Just updated 3 Pis. With one, a Pi 4 the install was logged as failed. It reports the current OS as 9.30. Check for update reports that OS is current.

H A R D W A R E A N D O S

moOde release = 9.3.0 2025-03-21
RaspiOS = 12.5 Bookworm 64-bit
Linux kernel = 6.6.74 64-bit
Pi model = Pi-4B 1.1 2GB
Architecture = aarch64 (64-bit)
Home directory = /home/admin

[ils1974]

If you run mpd --version on the failed one, you'll see the mpd version of the failed one is not 0.24, although moOde reports it's on 9.3.0. Looks like some things went through and other not.

[TheOldPresbyope]

If the update log says the update failed, then it failed.

The update procedure succeeded for two moOde 9.2.6 players that were running here this morning: one on a RPi3A+, the other on an RPi5B.

Code:

rho@sunroom:~ $ cat /var/log/moode_update.log
20250323 080058 updater: Start 2025-03-21 update for moOde
20250323 080058 updater: ** Step 01-35: Remove package hold
20250323 080102 updater: ** Step 02-35: Update package list
20250323 080136 updater: ** Step 03-35: Update Linux kernel to 6.6.74
20250323 080136 updater: ** - Kernel is current, no update required
20250323 080136 updater: ** Step 04-35: Install moode-player=9.3.0-1moode1
20250323 080207 updater: ** Step 05-35: Install alsa-cdsp=1.2.0-2moode1
20250323 080224 updater: ** Step 06-35: Install mpd=0.24-1moode1
20250323 080252 updater: ** Step 07-35: Install mpc=0.35-1moode1
20250323 080314 updater: ** Step 08-35: Install bluez-alsa-utils=4.2.0-2moode1
20250323 080319 updater: ** Step 09-35: Install libasound2-plugin-bluez=4.2.0-2moode1
20250323 080323 updater: ** Step 10-35: Install camilladsp=3.0.0-1moode1
20250323 080327 updater: ** Step 11-35: Install camillagui=3.0.2-1moode1
20250323 080331 updater: ** Step 12-35: Install mpd2cdspvolume=2.0.0-1moode2
20250323 080335 updater: ** Step 13-35: Install python3-camilladsp-plot=3.0.0-1moode1
20250323 080339 updater: ** Step 14-35: Install python3-camilladsp=3.0.0-1moode1
20250323 080343 updater: ** Step 15-35: Install shairport-sync=4.3.6-1moode1
20250323 080347 updater: ** Step 16-35: Install log2ram=1.7.2
20250323 080350 updater: ** Step 17-35: Install librespot=0.6.0-1moode1
20250323 080354 updater: ** Step 18-35: Install libnpupnp13=6.2.0-1moode1
20250323 080358 updater: ** Step 19-35: Install libupnpp16=0.26.7-1moode1
20250323 080402 updater: ** Step 20-35: Install pleezer=0.13.0-1moode1
20250323 080420 updater: ** Step 21-35: Install upmpdcli=1.9.0-1moode1
20250323 080425 updater: ** Step 22-35: Install upmpdcli-qobuz=1.9.0-1moode1
20250323 080429 updater: ** Step 23-35: Install upmpdcli-tidal=1.9.0-1moode1
20250323 080433 updater: ** Step 24-35: Install bluez-firmware
20250323 080437 updater: ** Step 25-35: Install firmware-atheros
20250323 080818 updater: ** Step 26-35: Install firmware-brcm80211
20250323 080822 updater: ** Step 27-35: Install firmware-libertas
20250323 080826 updater: ** Step 28-35: Install firmware-linux-free
20250323 080830 updater: ** Step 29-35: Install firmware-misc-nonfree
20250323 080834 updater: ** Step 30-35: Install firmware-realtek
20250323 080838 updater: ** Step 31-35: Install raspi-firmware
20250323 080842 updater: ** Step 32-35: Install rpi-eeprom
20250323 080917 updater: ** Step 33-35: Apply package hold
20250323 080918 updater: ** Step 34-35: Post-install cleanup
20250323 080918 updater: ** - Restore theme color
20250323 080918 updater: ** - Remove unneeded APT archive files
20250323 080918 updater: ** - Remove unneeded packages
20250323 080935 updater: ** - Reset Bluetooth PIN code if indicated
20250323 080937 updater: ** Step 35-35: Sync changes to disk
20250323 080937 updater: Finish 2025-03-21 update for moOde
20250323 080937 updater: Update installed, restart required

The moOde release reported by moodeutl is parsed from the file /var/www/footer.min.php. If step 04 got as far as copying in that file before failing, then your player will lie to you about its current release. Who knows how much did or didn't get completed in that step.

Look at steps 05 and beyond to see what your update procedure never even got to, including the update to mpd 0.24 mentioned by @ils1974

Regards,
Kent

[Tim Curtis]

Since adding error checking and reporting to the update script it's not surprising to see that some updates are failing. This was going unreported in the past :-0

You can try running the update manually from the command line. It will print more detail about where the errors are occurring.

Code:

sudo /var/www/util/system-updater.sh moode9

Its certainly possible that the update script has a bug or bad logic but I didn't experience any issues during my tests updating 926 to 930, so unless I can reproduce something the only option at this time for a failed update is to start with a fresh image and restore settings from a backup.

[Tim Curtis]

A new update zip has been posted.

A non essential cleanup step that bombed was removed based on log from @Sander

[Sander]

Thanks Tim, update completed successfully with 'sudo /var/www/util/system-updater.sh moode9'

[nosferatu_cat]

A new update zip has been posted.

A non essential cleanup step that bombed was removed based on log from @Sander

I had to update 2 Pis from the command line.  The update ran smoothly on one.  On the other, it failed twice.  I rebooted and it ran successfully.  Here's the portion of the output from the error:

Code:

The following packages will be upgraded:
 raspi-firmware
1 upgraded, 0 newly installed, 0 to remove and 203 not upgraded.
Need to get 0 B/12.8 MB of archives.
After this operation, 24.6 kB of additional disk space will be used.
apt-listchanges: Reading changelogs...
(Reading database ... 164679 files and directories currently installed.)
Preparing to unpack .../raspi-firmware_1%3a1.20250305-1_all.deb ...
Unpacking raspi-firmware (1:1.20250305-1) over (1:1.20241126-1) ...
dpkg: error processing archive /var/cache/apt/archives/raspi-firmware_1%3a1.2025                                        0305-1_all.deb (--unpack):
unable to stat './usr/lib/raspi-firmware/fixup4cd.dat' (which was about to be i                                        nstalled): Structure needs cleaning
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/raspi-firmware_1%3a1.20250305-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
** Step failed
** Exiting update
Install failed, update cancelled

[Tim Curtis]

A new update zip has been posted.

A non essential cleanup step that bombed was removed based on log from @Sander

I had to update 2 Pis from the command line.  The update ran smoothly on one.  On the other, it failed twice.  I rebooted and it ran successfully.  Here's the portion of the output from the error:

Code:

The following packages will be upgraded:
 raspi-firmware
1 upgraded, 0 newly installed, 0 to remove and 203 not upgraded.
Need to get 0 B/12.8 MB of archives.
After this operation, 24.6 kB of additional disk space will be used.
apt-listchanges: Reading changelogs...
(Reading database ... 164679 files and directories currently installed.)
Preparing to unpack .../raspi-firmware_1%3a1.20250305-1_all.deb ...
Unpacking raspi-firmware (1:1.20250305-1) over (1:1.20241126-1) ...
dpkg: error processing archive /var/cache/apt/archives/raspi-firmware_1%3a1.2025                                        0305-1_all.deb (--unpack):
unable to stat './usr/lib/raspi-firmware/fixup4cd.dat' (which was about to be i                                        nstalled): Structure needs cleaning
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/raspi-firmware_1%3a1.20250305-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
** Step failed
** Exiting update
Install failed, update cancelled

Good info.

What version of moOde was on this system?