[SOLVED] Update to 9.3.0 cancelled

[the_bertrum]

To add another point of data, I had the 9.3.0 update fail on two players. Running the manual script revealed that the players that failed had unused packages that needed autoremove, the one that worked did not (recently flashed afresh is probably why). Alas I didn't grab any logs as I went through it, and the moode_update log jus has the headlines...

[Tim Curtis]

I've since posted a new update script that does not contain the final autoremove command.

[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

Good info.

What version of moOde was on this system?

V 9.26

[Venerdi]

A new update zip has been posted.

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

I surrended. I can't solve it.
Where is the new zip?
I always see 9.30
I tried to make a new card. I use my TV screen. Everything stops after a few reboots with the message:
admin@moode: ~$
and yet, I followed the procedure like all the other times.
I reused the old card, the one where the update failed, but it still shows 9.30
Is it possible that there is no way to update again to 9.30, when after a failed update, 9.30 is already installed anyway?
v.

[Tim Curtis]

A new update zip has been posted.

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

I surrended. I can't solve it.
Where is the new zip?
I always see 9.30
I tried to make a new card. I use my TV screen. Everything stops after a few reboots with the message:
admin@moode: ~$
and yet, I followed the procedure like all the other times.
I reused the old card, the one where the update failed, but it still shows 9.30
Is it possible that there is no way to update again to 9.30, when after a failed update, 9.30 is already installed anyway?
v.

Try this command. It automatically downloads the new updater zip and installs the update.

Code:

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

[Venerdi]

Code:

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

Thanks as always for your very fast response and your availability, but I don't know where I have to write this string.
Maybe in the SSH terminal?
Another problem, I can't log in.
I don't think I've ever changed anything, but with "pi" and "moodeaudio" I can't log in.
If you made changes, maybe the only solution will be to create 9.31 which would be detected as a new version...
v.

[Falco]

Code:

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

Thanks as always for your very fast response and your availability, but I don't know where I have to write this string.
Maybe in the SSH terminal?
Another problem, I can't log in.
I don't think I've ever changed anything, but with "pi" and "moodeaudio" I can't log in.
If you made changes, maybe the only solution will be to create 9.31 which would be detected as a new version...
v.

I believe you will find the solution in the setup guide
https://github.com/moode-player/docs/blo...etup-guide-

The procedure has changed some releases ago. Best would be to start fresh with a new image and follow the instructions in the setup guide.

[Venerdi]

I believe you will find the solution in the setup guide
https://github.com/moode-player/docs/blo...etup-guide-

The procedure has changed some releases ago. Best would be to start fresh with a new image and follow the instructions in the setup guide.

How can you think I didn't read it?
I started using moOde from version 4.xx
I have always followed the guides (and the changes that have been made).
There is something new that (at least for me) does not make the process work

[Tim Curtis]

Code:

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

Thanks as always for your very fast response and your availability, but I don't know where I have to write this string.
Maybe in the SSH terminal?
Another problem, I can't log in.
I don't think I've ever changed anything, but with "pi" and "moodeaudio" I can't log in.
If you made changes, maybe the only solution will be to create 9.31 which would be detected as a new version...
v.

Yes, the command is entered in an SSH terminal.

For the forgotten password situation your best bet is prolly to first create a backup of your system using BACKUP on System Config, then start with a fresh image and do a RESTORE.

Being able to open an SSH terminal (very easy on System Config) and running commands to fix problems and assist in troubleshooting is a big benefit for you and for us because we gain knowledge on what might turn out to be bugs that can be fixed.

[Nutul]

I started using moOde from version 4.xx
I have always followed the guides (and the changes that have been made).
There is something new that (at least for me) does not make the process work

If you mention pi / moodeaudio you most probably didn't read the guide... it warns you that NOW a username + password NEED to be set-up in the Raspberry Imager application PRIOR to flashing the image to the SD card. Failing to do so results in a system without any user... unusable.

There is, INDEED something new; and you didn't read about it.