Soon Robert, soon, still baking
3.694
Key improvements:
- UUID check lottery where one in (2^128)*(2^32)/2 chances may produce the same part UUID.
- Wait a bit longer for a slumbering USB device (if detected) to fully wakeup.
Hello,
I tried an OTA update from 3.691 to 3.694 but it failed.
Running on a Pi4 with SD card.
Test mode enabled
No alpha test mode
info: Update Ready: {“changeLogLink”:“http://volumio.org”,“description”:"
FIXES
\n
\n
Improvements for Volumio logo on boot
\n
Fix kiosk start on boot
\n
Improved responsiveness of scrolling on motivo
\n
\n
NEW ADDITIONS
\n
\n
Play next functionality
\n
Use 64bit kernel on CM4
\n
Add BBC radios
\n
Bump to kernel 6.1.77 on RPi
\n
Bump to init-v3
\n
Add USB and NVME boot capabilities to RPi
\n
Add install to NVME disk on supported RPi models
\n
New awesome plymouth on boot
\n
New onboarding wizard
\n
Update socket.io to 2.3.0
\n
Improvements for 11 inch displays
\n
Increase size of back and home button
\n
UNSTABLE ALPHA BUILD - DO NOT INSTALL
\n
\n",“title”:“Update v3.694”,“updateavailable”:true}
info: CoreCommandRouter::executeOnPlugin: updater_comm , setUpdateMessageCache
info: Update: [object Object]
info: CoreCommandRouter::executeOnPlugin: updater_comm , checkSystemIntegrity
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
info: CoreCommandRouter::executeOnPlugin: system , setTestSystem
info: CoreCommandRouter::executeOnPlugin: updater_comm , checkUpdates
info: CoreCommandRouter::executeOnPlugin: my_volumio , getAutoUpdateCheckEnabled
PROGRESS: 0, STATUS: “Starting update”, ETA: “6m”
info: CoreCommandRouter::executeOnPlugin: updater_comm , notifyProgress
/bin/rm: cannot remove ‘/imgpart/rck*’: No such file or directory
/bin/rm: cannot remove ‘/imgpart/.part’: No such file or directory
/bin/rm: cannot remove '/imgpart/.zs-old’: No such file or directory
PROGRESS: 5, STATUS: “Preparing update”, ETA: “5m”
info: Killing processes that might interfere with OTA Updates
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/killall matchbox-keyboard
pam_unix(sudo:session): session opened for user root by (uid=0)
info: CoreCommandRouter::executeOnPlugin: websocket , broadcastMessage
updateProgress
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/killall matchbox-window-manager
pam_unix(sudo:session): session opened for user root by (uid=0)
{
downloadSpeed: ‘’,
eta: ‘5m’,
progress: 5,
status: ‘Préparation de la mise à jour’
}
pam_unix(sudo:session): session closed for user root
error: Cannot kill process: Error: Command failed: /usr/bin/sudo /usr/bin/killall matchbox-keyboard
matchbox-keyboard: no process found
pam_unix(sudo:session): session closed for user root
error: Cannot kill process: Error: Command failed: /usr/bin/sudo /usr/bin/killall matchbox-window-manager
matchbox-window-manager: no process found
PROGRESS: 5, STATUS: “Preparing update”, ETA: “5m”
PROGRESS: 5, STATUS: “Preparing update”, ETA: “5m”
info: CoreCommandRouter::executeOnPlugin: websocket , broadcastMessage
updateProgress
{
downloadSpeed: ‘’,
eta: ‘5m’,
progress: 5,
status: ‘Préparation de la mise à jour’
}
info: CoreCommandRouter::executeOnPlugin: websocket , broadcastMessage
updateProgress
{
downloadSpeed: ‘’,
eta: ‘5m’,
progress: 5,
status: ‘Préparation de la mise à jour’
}
info: CALLMETHOD: user_interface websocket broadcastMessage [object Object]
info: CoreCommandRouter::executeOnPlugin: websocket , broadcastMessage
info: CoreCommandRouter::Close All Modals sent
ENABLE DISABLE
State of progress 5 - indicates that the download of OTA has not completed yet; whilst eta: ‘5m’ suggest how long it is going to take, calculated from your network socket pipe.
Can you try again and wait for something like fail state?
Kind Regards,
Message from Volumio:
Update Failed
Updating to the latest version on this system is unfortunately not possible. Please download the latest Volumio and flash your SD Card from scratch
For more information, please see https://community.volumio.com/t/update-to-v-3-569-not-possible-all-you-need-to-know/
Hello…I have the same problem…OTA doesn’t work properly. Unfortunately I didn’t create a log… when re-flashing the current beta v3.694 onto a USB stick, the Raspi doesn’t start at all… Beta v.691 works
Kind regards
This is/was for much older partitions layout, prior v3.569.
In your case:
SBC: | Raspberry Pi 4 |
Storage: | MicroSD |
Volumio OS: | 3.691 |
Will try to replicate.
Perhaps an HDMI display will be needed to diagnose your case further. Freshly flashed image will not be aware of the Pi 7" display yet.
Kind Regards,
Hi…I just tested with an external display and also with the original 7" Raspi display…
BOTH displays are dark on a newly bottled Volumio c.3694… The Raspi’s LED lights up red continuously, no flickering of the green LED…
Kind regards
P.S. Tested the same with v3.691, works perfectly
I installed succesfully a 3.694 on a SD card for a Pi3.
3.691:
After OTA to 3.694:
Logs after OTA: http://logs.volumio.org/volumio/PBi4Mxt.html
What am I doing differently?
Fresh install USB: 3.694:
Log: http://logs.volumio.org/volumio/pxdEnnf.html
What am I doing differently?
This is the image I am flashing to USB: https://updates.volumio.org/pi/volumio/3.694/Volumio-3.694-2024-05-23-pi.zip
Can be that there is a bad download in your case? However, this should not hamper the OTA anyway.
Thanks…I’ll test it tomorrow. My “SmartiPi Touch Pro Case” is still being “converted”…
Kind regards
@MitchStoner
I wonder if this is storage capacity being exceeded.
Would be possible to login with ssh client to your volumio and execute:
df -h
What does the output say?
Just to offer a different experience I updated 2 Raspi 5s from 6.691 - 6.694 via OTA without any problems.
- Pi 5, Pimoroni NVMe Base for Raspberry Pi 5 + 500GB SSD, and PoE HAT (F)
- Pi 5, Official Pi NVMe board 500GB SSD and official PI power supply.
This is the first time the Pi 5 with an official NVMe board has updated without a hitch - the previous 2 or 3 stalled with the restart after the OTA and then a blank screen requiring starting from scratch and reflashing with an SD card.
Steve
volumio@pi4:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.8G 0 3.8G 0% /dev
tmpfs 785M 5.3M 780M 1% /run
/dev/mmcblk0p2 2.5G 544M 1.8G 24% /imgpart
/dev/loop0 478M 478M 0 100% /static
overlay 115G 17M 109G 1% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 20M 32K 20M 1% /var/log
tmpfs 3.9G 0 3.9G 0% /var/spool/cups
tmpfs 3.9G 44K 3.9G 1% /tmp
tmpfs 3.9G 0 3.9G 0% /var/spool/cups/tmp
/dev/mmcblk0p1 91M 66M 25M 73% /boot
tmpfs 785M 0 785M 0% /run/user/1000
Succesfull OTA on a Pi2 from 3.661 to 3.694
There is nothing obvious preventing OTA.
There is a module throwing stack trace - would be possible to disable or uninstall “Now playing” and check again?