Was it USB or NVMe?
Kind Regards,
Hi Nerd
It was NVMe - just reflashed the SD card and re-loaded Volumio onto NVMe and everything is running fine so the problem appears to be the OTA to 3.689
version 3.689 Strange behaviour!
- BBC Radio 3 linked started to work - its icon also changed
- BBC Radio 4 acquired an icon
then sometime later ā¦ - BBC Radio 3 plays Radio 4 again and its icon went back to the origina versionl and Radio 4 has lost its icon
Put simply the BBC Radio links have gone back ro where we started - any ideas?
Hi nerd
Yes, on fresh installā¦SD Card & SSD no Problemā¦ 
Heyā¦yes, i will dio this tomorrowā¦ ,) iām at cooking nowā¦in Switzerland is 5:45 PM 
Kind Regards,
This is very cumbersome. Our team, and I mean TEAM can not reproduce the problem in any combination.
The only remark on USB OTA upgrade, is that the Raspberry Pi 4B/5 requires power re-cycle and on 4 it takes quite a time to complete.
As the devil leaves in the details - with failing scenarios please provide:
- Board model and revision
- Storage device type (MicroSD/USB/USB-SSD/NVMe)
- Storage brand
- Storage model
- Storage size
OTA from 3.679 to 3.689 did work fine here.
When starting playback (tidalā) the mpd player restarted unexpectedly.
hereās the log: http://logs.volumio.org/volumio/yrzSuca.html
Thanks for letting us know Robert.
As this is not new init related, it will be noted as a volumio core issue.
OTA from 3.689 to 3.691
Everything seems to work fine until now.
On Raspi4B USB OTA from 679 to 691 without problemsā¦
Good morning nerd
Now I have activated the log, including an OTA update to the new version 3.691.
Unfortunately, restarting with USB (whether SSD or stick) still doesnāt work. Cold startā¦ Could also be due to the Raspi 4.
The error message from āalsaā is still there.
I havenāt made any adjustments to the āuserconfigā yet, so the system is unchanged.
Sound at the outputs works perfectly.
Plugins are installed:
Spotify
AuroStart
Backup & Restore Data
IR Remote Controller (USB Flirc 2 & Flirc Skip 1s Remote are on the way)
System information
Now Playing
Touch screen
My equipment:
RaspiPi 4, 8GB, Rev B (latest Eeprom, configured with 0xf41)
Original 7" Touch screen with light sensor BH1750 (software is still inactive, is intended for automatic display brightness)
Argon Fan Hat (software not yet configured)
iQaudIO DAC Pro
Samsung SSD T7, 500GB
USB stick Kingston Data Traveler Kyson, 512GB (Would be for testing, but with the USB stick the system always hangs when you first start it with a new flash) SanDisk doesnāt work at all.
The DAC or Fan Hat is connected to the Raspi with a GPIO cable, which is then installed in the "SmartiPi Smart Case Pro Large)ā¦
Log file:
http://logs.volumio.org/volumio/3CTSe6Z.html
Kind Regards, Camelot631
Thank you for the logs, it helps quite a lot actually. Something concerning:
May 19 08:31:47 volumio kernel: sda: sda1 sda2 sda3 May 19 08:31:47 volumio kernel: sd 0:0:0:0: [sda] Attached SCSI disk May 19 08:31:47 volumio kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. May 19 08:31:47 volumio kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. May 19 08:31:47 volumio kernel: loop0: detected capacity change from 0 to 977888 May 19 08:31:47 volumio kernel: EXT4-fs (sda3): recovery complete
FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. This may lead to the boot partition lockout. Upgrade logic prevents from partition removal without unmounting first. This leads to the question: How did we end-up here with a partition check flag? Unsafe eject or remove?
As basic as it may be, when flashing USB initially - can you describe your process including OS and tools involved?
Kind Regards,
Hey
For the Raspi I usually use āRaspberry Pi Imagerā or āBalena Etcherāā¦ but always with the current beta of Volumio.
The error probably comes from the fact that there is no clean reboot. The system gets stuck. Turn off the power, wait, plug the power cable back inā¦
Kind Regards
Hi,
OTA to 3.691 worked here.
After the startup of the new version MyVolumio seems to be inactive. I had to āstopā and āstartā the MyVolumio and then āconnectā it. After that, everything was working fine.
That was the case after the last OTA to Version 3.689 as well.
Best regards, Robert
thanks for this nice option.
new flash v3.691, 8 GB USB stick.
raspberry pi 4, 2gb.
waveshare 7.9 inch hdmi touchscreen.
rotary encoder: KY-040.
infrared sensor: tsop38238.
dac dual pcm 1794, ian canada FifoPiMa reclocker.
i2s driver hifiberry dac plus.
upsample via FusionDSP otherwise no sound Spotify, known problem with this combination.
installed plugins:
FusionDsp, v1.0.53
spotify, v4.0.4
ir remote controller, v3.4.13
rotary encoder II, v1.0.22
touch display, 3.4.0
now playing, 0.6.0
everything works well, except for installing plugins, the interface loses the connection (the progress bar also disappears) but the plugin is eventually installed.
and the reboot thing doesnāt work well either.
I hope the log is of some use to you.
http://logs.volumio.org/volumio/ndhPCbo.html
userconfig.txt
# Add your custom config.txt options to this file, which will be preserved duri$
# 7,9 inch hdmi touchscreen
hdmi_group=2
hdmi_mode=87
hdmi_timings=400 0 100 10 140 1280 10 20 20 2 0 0 0 60 0 43000000 3
# ian canada FifoPI MA
dtoverlay=hifiberry-dacplus
# power off button
dtoverlay=gpio-shutdown,gpio_pin=13,active_low=1,gpio_pull=up=gpio-shutdown
# led + op gpio-15 en massa
gpio=15=op,dh
#### Touch Display rotation setting below: do not alter ####
display_lcd_rotate=3
display_hdmi_rotate=3
Thank you for your detailed feedback.
USB and SBC reboot - there is clearly some love-hate relation here going as deeply as eeprom USB-MD power-cycle handling. Not sure (yet) how to keep the USB active state without external powered USB switch/hub.
Kind Regards,
Dear Volumionauts:
Booting from USB, although very appealing, has some shortcomings. Depending on USB thumb drive underlying controller or USB SSD hardware there may be no other choice than flashing Volumio OS releases directly. I appreciate that this is not ideal, however problem originates from USB drive handling by Raspberry Pi SBC. We do not stop in our research of this awkward behaviour, however we are still limited by the hardware interoperability. There are few things that you can try by experimenting with settings discussed in subsection 5 of the guide (with no guarantees):
Kind Regards,
Hello them all,
long time so see - anything new? 
Cheers,
Robert
Soon Robert, soon, still baking 