In place update to 8.3.2 failure....Now re-installed!

[Tim Curtis]

Even if I put a sticky it would not be read after a few releases. It's just human nature to not read the manual.

I do post release announcements that contain whats new and different here in the Forum, on our Mastodon social feed and in the big diyAudio moOde thread. I think thats sufficient but I'm always open to improving things, time permitting.

Also and in particular with FOSS and DIY projects like moOde it's very important to read the each official release announcement to help keep up with the changes and improvements. If anything is unclear or confusing, just post a question.

[TheOldPresbyope]

Today I tried to install 8.3.2 on a different Raspberry with the same result as described above by me and others.

Sorry again for providing no logs as the Raspberry can neither be reached via SSH nor is downloading from the Logs section of System Config possible.

Below the detailed steps I have taken. Hope this helps with diagnosing the problem.

Much better, but as can be inferred from your follow-up post, this list is missing the "zeroth" step

0a. Flashed image to a uSD card using < Balena Etcher | Win32 Disk Imager | Rufus | Linux dd | whatever >
0b. Did no pre-configuration before first boot, such as creating the default user account , customizing a /boot/moode-config.ini file, etc.

1. Start system with fresh 8.3.2 64bit image
2. Enter Config Menu/ System
3. Change values for timezone, host/player name, browser title, switch SMB to On
4. The field Filesharing/options turns red, asks for input
5. In this field I enter "rw,sync,no_subtree_check,no_root_squash" as this is described as default setting
6. Restart system
7. Result: Change of player name not recognized. Only the Top Configure menu can be reached. Sub menues like audio, network, system, etc. don't respond

....

As for your question

For avoiding threads like this wouldn't it be smart to put a sticky on top of the support section? And why is there still a direct download option if Moode only works with an image created with the Raspberry Imager? For laymans like me this easily leads in the wrong direction.

your point is well taken. Speaking only for myself, I believe it's mostly inertia (and believing folks always read the release notes and setup guide). The need to do more prep work in response to decisions made by the Raspberry Pi Foundation is recent. The addition of moOde to the RPi Imager's predefined list of Audio Player OSes is relatively recent as well.

For folks who experience slow Internet download speeds or folks like me who switch among versions for testing, it's convenient to keep local copies so one or another can be flashed as needed. The RPi Imager supports this through its "Select OS > Use Custom" option.

When the RPi Imager is used to download and flash one of its predefined OSes, it will use a cached image if available but it caches only the most recently downloaded image which is a nuisance for someone like me. OTOH, both current and previous moOde image(s) are available directly from the github repo so it isn't necessary to use the RPi Imager's download capability at all.

Glad you've got 8.3.2 working. It's a nice release.

Regards,
Kent