Don’t be so modest. You give a lot of good advice. 
2 Likes
ok, ok then
Final Showdown!
Wheaten vs Nerd: 12-ish vs 231,789
(That’s not just a loss… that’s a statistical obliteration.)
Adding a touch of drama:
POST-MATCH COMMENTARY:
The dust settles. The stadium echoes with stunned silence.
Nerd walks away, statistical crown untarnished, glasses still perched at a perfect angle.
Wheaten—stumbling, dazed—mutters, “I-I thought numbers didn’t matter…” before collapsing.
BREAKING NEWS:
Experts now declare this “The Most Lopsided Battle in Recorded History.”
Mathematicians struggle to quantify just how bad this loss was.
3 Likes
2 Likes
Hey @Wheaten,
Thanks. But before I can acknowledge the scoreboard, I’ll need the usual technical details; a few clarifications:
- Exact hardware revision (PCB version)
- Full list of connected HATs or DACs (model numbers please)
- Kernel version and bootloader revision
- RTC module part number (if applicable)
- Power loss duration (measured, not estimated)
- Whether drift correction was tested post-reboot
- And of course, system logs covering the RTC sync window
Without those, I’m afraid I can’t validate the “01” on your side of the scoreboard.
Until that data’s in, I’m treating your “01” as speculative and my “231,789” as… probably a rounding error introduced by float32.
We’re not savages.
Kind Regards,
Dear Volumionauts,
We have a clear winner! Well done @Wheaten!
Community Tenure Scoreboard: Wheaten vs Nerd
Reference Date: 13 May 2025
-
Wheaten - Joined 6 Mar 2021
→ 2,200,320 minutes
→ 132,019,200 seconds -
Nerd - Joined 12 Jan 2024
→ 701,280 minutes
→ 42,076,800 seconds
Scoreboard by Raw Uptime
Wheaten vs Nerd:
2,200,320 – 701,280 minutes
132,019,200 – 42,076,800 seconds
[SCORE SYNC OK]
Kind Regards,
4 Likes
ooooh, you even want to take the one point i have away… so brutal…
- Exact hardware revision (PCB version)
Model: Raspberry Pi 5 Model B Rev 1.0, * Version: d04170 - Full list of connected HATs or DACs (model numbers please)
Innomaker DAC Pro - Kernel version and bootloader revision
6.12.27-v8+,
sudo rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Thu May 8 14:13:17 UTC 2025 (1746713597)
LATEST: Thu May 8 14:13:17 UTC 2025 (1746713597)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2712/default)
Use raspi-config to change the release.
- RTC module part number (if applicable)
only the same battery as ClaesM showed - Power loss duration (measured, not estimated)
not measured but at least 3 days - Whether drift correction was tested post-reboot
volumio@rpi5-ws840:~$ ntpq -p
remote refid st t when poll reach delay offset jitter
===============================================================================
0.debian.pool.n .POOL. 16 p - 256 0 0.0000 0.0000 0.0005
1.debian.pool.n .POOL. 16 p - 256 0 0.0000 0.0000 0.0005
2.debian.pool.n .POOL. 16 p - 256 0 0.0000 0.0000 0.0005
3.debian.pool.n .POOL. 16 p - 256 0 0.0000 0.0000 0.0005
+83-84-240-223.c 125.199.53.76 2 u 12 64 377 31.8455 576.7164 3.1479
ntp01.cobytes.i .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
mail.novg.net .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
158.101.216.150 .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
86-80-166-233.f .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
ntp01.pingless. .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
80-60-67-39.fix .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
hosted.by.xyphe .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
185.45.112.121 .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
time.lettersblo .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
time2.panq.nl .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
v6.forfun.net .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
ntp.dicode.nl .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
v6-2.forfun.net .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
ntp1.ams.nl.hoj .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
ntp1.ams.nl.hoj .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
leontp1.office. .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
x.ns.gin.ntt.ne .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
mail.roundowl.t .INIT. 16 u - 64 0 0.0000 0.0000 0.0005
volumio@rpi5-ws840:~$ date && sudo hwclock --show
Fri Jun 13 18:58:54 CEST 2025
2025-06-13 18:58:54.212322+02:00
- And of course, system logs covering the RTC sync window
Jun 13 15:37:32 rpi5-ws840 kernel: rpi-rtc soc@107c000000:rpi_rtc: trickle charging enabled at 3000000uV
Jun 13 15:37:32 rpi5-ws840 kernel: rpi-rtc soc@107c000000:rpi_rtc: registered as rtc0
Jun 13 15:37:32 rpi5-ws840 kernel: rpi-rtc soc@107c000000:rpi_rtc: setting system clock to 2025-06-13T13:37:21 UTC (1749821841)
Something less yeeeeahhhh:
volumio@rpi5-ws840:~$ journalctl -u systemd-timesyncd
-- No entries --
cat /boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates
dtparam=i2c_arm_baudrate=800000
dtparam=spi=on
dtparam=i2c_vc=on
dtparam=rtc_bbat_vchg=3000000
after a 10 minutes wait, when killing the power connection:
volumio@rpi5-ws840:~$ date && sudo hwclock --show
Fri Jun 13 19:31:59 CEST 2025
2025-06-13 19:31:59.285404+02:00
volumio@rpi5-ws840:~$ ntpq -p
remote refid st t when poll reach delay offset jitter
=======================================================================================================
0.debian.pool.ntp.org .POOL. 16 p - 64 0 0.0000 0.0000 0.0005
1.debian.pool.ntp.org .POOL. 16 p - 64 0 0.0000 0.0000 0.0005
2.debian.pool.ntp.org .POOL. 16 p - 64 0 0.0000 0.0000 0.0005
3.debian.pool.ntp.org .POOL. 16 p - 64 0 0.0000 0.0000 0.0005
86-80-166-233.fixed.kpn.net 158.255.145.140 3 u 24 64 1 16.2134 -2.9280 1.3703
-host-miq.as15435-c.v4.dfn.nl .kPPS. 1 u 43 64 1 16.2702 -3.1083 0.7230
mail.roundowl.tk 192.171.1.150 2 u 3 64 1 13.6713 -1.1942 1.3282
connected.by.freedominter.net 10.1.105.4 2 u 1 64 1 15.8647 -0.6890 1.2937
connected.by.freedominter.net 10.1.105.4 2 u - 64 1 18.2509 -1.0765 4.5065
+185.244.24.70 94.198.159.10 2 u 42 64 1 13.1345 -0.5130 1.3202
*ntp2.as215248.net .PHC0. 1 u 30 64 1 15.3063 -1.5306 0.3811
-ntp01.cobytes.io 94.198.159.10 2 u 42 64 1 11.2546 0.1308 1.6912
v6-4.forfun.net .STEP. 16 u - 64 0 0.0000 0.0000 0.0005
ht.jnd.ovh .STEP. 16 u - 64 0 0.0000 0.0000 0.0005
2001:1af8:4700:a052:2::116c .STEP. 16 u - 64 0 0.0000 0.0000 0.0005
ntp1.ams.nl.hojmark.net .STEP. 16 u - 64 0 0.0000 0.0000 0.0005
connected.by.freedominter.net 10.1.105.4 2 u 55 64 1 17.7020 -2.2791 0.6783
-mail.novg.net 131.188.3.220 2 u 27 64 1 10.7123 -1.2414 0.6371
-ntppool1.time.nl .TMNL. 1 u 41 64 1 17.7761 0.9542 3.9751
-hosted.by.xyphen.it 192.87.106.2 2 u 41 64 1 15.4903 1.6052 3.1138
-auth-qupra-ams-nl.ebgp.fi 61.233.105.6 2 u 40 64 1 10.6405 -1.1389 1.3766
+time1.panq.nl 192.171.1.150 2 u 31 64 1 10.6405 -0.3088 0.2701
+ams.ns.sysn.net 125.199.53.76 2 u 40 64 1 10.6922 -1.0352 0.3593
volumio@rpi5-ws840:~$ dmesg | grep -i "rtc"
[ 0.461711] rpi-rtc soc@107c000000:rpi_rtc: trickle charging enabled at 3000000uV
[ 0.466901] rpi-rtc soc@107c000000:rpi_rtc: registered as rtc0
[ 0.468280] rpi-rtc soc@107c000000:rpi_rtc: setting system clock to 2025-06-13T17:30:55 UTC (1749835855)
1 Like
@nerd , @Wheaten
How I love this forum! Great and humorous people! but because of your auctions, my disk crashed.
Ah, the joys of technology—the forum giveth, and the forum taketh away! 
One minute, you’re laughing at top-tier humor, the next, your disk decides to go on a spontaneous vacation. Failed to start Plymouth? Sounds like your Raspberry Pi just rage-quit on life. Failed unmounting rt.mount? Guess it’s holding on for dear life. And that shutdown binary? Well, it’s clearly on strike.
But hey, at least you got some good laughs out of it—consider it the price of admission! Now, let’s see if we can bribe your Pi back to working order!
RTC Score Appeal Review - Case #840-WTN
Filed: 13 May 2025 | Applicant: @Wheaten
Summary:
Following a formal reassessment of the “01” scoreboard credit previously allocated to the applicant, an internal review has been conducted based on the provided technical dossier.
Application Contents (abridged for clarity):
-
Hardware Revision:
Raspberry Pi 5 Model B Rev 1.0 (d04170)
[Verified] -
HAT/DAC:
Innomaker DAC Pro
[No voltage collision declared. Plausible.] -
Kernel & Bootloader:
6.12.27-v8+, EEPROM up-to-date
[Beta-compatible. Not obviously broken.] -
RTC Module:
No explicit module. “Battery as per ClaesM.”
[Technically unqualified, socially endorsed.] -
Power Loss Duration:
“At least 3 days”
[No logs. Certified by intuition.] -
Drift Correction Evidence:
ntpq -pconfirms presence of 23 dead peers and one responder with 576ms offset.dateandhwclockmatch to within a tenth of a second.- RTC kernel log shows valid UTC fallback.
[Meets the “Probably Works” threshold.]
-
Systemd Sync Service:
systemd-timesyncdnot active.
[Bold strategy. Respectfully noted.] -
Additional Configs:
userconfig.txtincludes trickle charge override and i2c baudrate boost.
[Suspiciously thorough. Possibly compensating.]
Verdict:
After cross-referencing all provided data with the Volumio Beta Field Trial Manual, Section 4.3(b) - “Acceptable RTC Voodoo”, the review board has voted 2.5 to 2.0 in favor of conditionally approving Wheaten’s original score.
The score remains 01, with an internal annotation:
01* (validated under duress; RTC may collapse under wind load)
[SCORE SYNC OK]
Kind Regards,
2 Likes
I don’t have a battery
Right?! It’s like a secret identity swap waiting to happen—Gelo5 and ClaesM, the dynamic duo of username confusion! One minute, you’re replying to Gelo5, next thing you know, ClaesM is wondering why he’s being blamed for your latest tech disaster.
Honestly, with names that close, they should just merge into GelaesM5—sounds like an elite hacker alias or a futuristic AI overlord.
But hey, at least it keeps things entertaining! Who needs clarity when you have chaos?
2 Likes
Hey @Galo5,
Following up on your NVMe-related crash. Since your setup uses:
nvme0n1p1- bootpart (vfat)nvme0n1p2- imgpart (ext4, rootfs overlay)nvme0n1p3- datapart (ext4, holds configs, etc.)
Here’s what you could try:
Recovery steps (from microSD rescue boot)
-
Boot from a known-good microSD Volumio image
Ensure NVMe is connected and detected. -
Run filesystem checks:
sudo fsck.ext4 -f /dev/nvme0n1p2 # imgpart
sudo fsck.ext4 -f /dev/nvme0n1p3 # datapart
(Optional, if suspecting boot issues)
sudo fsck.vfat -v /dev/nvme0n1p1
- Mount partitions for manual inspection:
mkdir -p /mnt/img /mnt/data
sudo mount /dev/nvme0n1p2 /mnt/img
sudo mount /dev/nvme0n1p3 /mnt/data
- Verify critical files:
/mnt/data/configuration.json/mnt/data/...
Also make sure the upper/ and work/ directories inside /mnt/img are valid and not corrupt.
Once that’s done and everything checks out, power down, remove the microSD, and cold-boot again from NVMe.
If any logs or files look suspicious, feel free to post them here and I’ll help walk through them.
Kind Regards,
Hey @Gelo5,
Ah, Galo5 it is then!
Sad to see the NVMe go before we could properly dissect it. There was potential for a legendary deep dive into corrupted overlayfs chaos…
But alas, the patient flatlined before autopsy.
We’ll remember it fondly:
- As the card that took
dynamicswap.servicedown with it, - That unmounted
/imgpartwith vengeance, - And brought
shutdown binaryto its knees.
Gone, but not fsck’d.
We’ll get ‘em next boot.
Kind Regards,
2 Likes
It seems to be working for me, if I am not wrong;
timedatectl status
Local time: Fri 2025-06-13 19:53:43 CEST
Universal time: Fri 2025-06-13 17:53:43 UTC
RTC time: Fri 2025-06-13 17:53:43
Time zone: Europe/Amsterdam (CEST, +0200)
System clock synchronized: yes
NTP service: n/a
RTC in local TZ: no
1 Like
Hi,
after OTA update from 4.010 to 4.012 I see multiple player restarts while searching a title in my Tidal Title list.
http://logs.volumio.org/volumio/VknbLNf.html
Best regards,
Robert
OTA 4.011 to 4.012
Pi4B, SD card, 7" RPi display, Topping D10s USB DAC
Logs http://logs.volumio.org/volumio/sqV4250.html
Perfect!
Tested base functionality: BT connect, play here, Multiroom, local and network drive playback, web radio, infinity search.
Plugins: Touch Display, now playing, Spotify, Bandcamp, SoundCloud, IR remote, backup and restore, system info.
(post deleted by author)