i removed the SD card from the rPI and mounted it on another computer; i found a partially downloaded raucb archive in /data/rauc/downloads
below, partial quote, from /data/log/ropieee-20231205.log, with messages that repeated every 4 hours until i powered off the PI this morning; before Dec 04, when i disabled IPv6 on my router i couldn’t find any similar messages, so i suspect the PI tried to connect to image.ropiee.io over IPv6 and failed
Dec 04 17:46:01 RoPieee-D50s ropieee-api[325]: [ 3618.131910 INFO updater] fetchManifest() found update bundle: ropieeexl_ose_pi4-
Dec 04 17:46:02 RoPieee-D50s ropieee-api[325]: [ 3619.133319 INFO updater] downloadBundle() 0 %
Dec 04 17:46:03 RoPieee-D50s ropieee-api[325]: [ 3620.133204 INFO updater] downloadBundle() 2 %
[ . . . ]
Dec 04 17:47:35 RoPieee-D50s ropieee-api[325]: [ 3712.133006 INFO updater] downloadBundle() 91 %
Dec 04 17:47:36 RoPieee-D50s ropieee-api[325]: [ 3713.133556 INFO updater] downloadBundle() 92 %
BTW - i am using a 4 GB SD-card, which could be too small to create the feedback archive (FS usage, after I manually downloaded raucb archive, below):
This is interesting. So, the data partition (dev/sdc7 in your case) has a rather limited amount of free space. Would be great if you can send me a ‘du’ of that directory.
And, then again the network stuff… is your infra ipv6 only?
Network config: dual stack - private IPv4 double NAT-ed (ISP modem that i can’t configure in bridge-mode + personal router) & IPv6 obtained from my ISP (IPv6 prefix delegation); firewall wise, nothing fency - egress permit all / igress permit already connected (on my router; and disabled on the modem). But for now, the IPv6 stack is a mess until ISP will update routes for the delegated IPv6 prefix on the modem.
FS usage on /data mount-point below (most space used by rauc/downloads, where i manually DL-ed the 2023.11 update bundle):
root@HQPlayer:/run/media/rpieee-data-sdc7# df -hPT .
Filesystem Type Size Used Available Capacity Mounted on
/dev/sdc7 ext4 602.7M 509.6M 49.0M 91% /run/media/rpieee-data-sdc7
root@HQPlayer:/run/media/rpieee-data-sdc7# du -sh * | sort -h | tail -5
68.0K roon
908.0K root
1.5M log
39.0M ropieee-rescue
468.1M rauc
root@HQPlayer:/run/media/rpieee-data-sdc7# ls -l rauc/downloads/ropieeexl_ose_pi4-2023.11.0-stable.20231126.1179.raucb
-rw-r--r-- 1 root root 490770432 Dec 5 15:15 rauc/downloads/ropieeexl_ose_pi4-2023.11.0-stable.20231126.1179.raucb
root@HQPlayer:/run/media/rpieee-data-sdc7#
FYI - i am finally running 2023.11 without a reimage, after:
manually copied “ropieeexl_ose_pi4-2023.11.0-stable.20231126.1179.raucb” to “/data/rauc/bundle”,
on next boot i was notified that an update is available, but after reboot it was still running 2023.09 & no update notification,
ignored it, and after a few hours i was notified again, rebooted and unit upgraded successfully to 2023.11
thanks for your help & patience; out of curiosity i will review /data/logs maybe i can find an explanation for the sudden change of heart
EDIT: nothing interesting in the logs; the manually copied bundle failed some checks, but a few hours later bundle downloaded successfully and i was able to upgrade; for unknown reasons, the bundle & manifest DLs failed at 80-90% until than; for your reference i generated a feedback archive roughly 10 hours after the upgrade - ed1c0ae55c7693b8.
The extension time-outs when it is initially registering itself with the Roon server. As you have 2 of them, I suspect it has something to do with that.
Try to register it with a Roon server while the other one is not available.
I’ll increase the time-out a bit.
Here is another one with odd issue but this one dies needing a pair again. Feedback from this un paired state. Only thing was probably a nightly reboot
Two (2) of my 4 ROPIEEE alert me and want to install 1171 - but this version was buggy. Is there a way to skip that (or delete the already downloaded 1171) and install the most current version 1179?? (Well etch a SD-Card and do a new install of course…)