Problem updating runit on raspberry pi 5

[idlecodinggoats]

I am running void on a raspberry pi 5 - I can boot from the current (25/01/2026) musl image and update xbps using xbps-install -Su and xbps-install -u xbps, but if i don't do a xbps-pkgdb -m hold runit and xbps-pkgdb -m hold runit-void before doing another xbps-install -Su then I end up in an unbootable system. Caveat, I am assuming it it unbootable, I cannot ssh in, but I don't have a cable for plugging in the raspberry pi via hdmi, nor a working serial cable to see if I get any output before networking. Any help would be much appreciated.

[classabbyamp]

the current (25/01/2026) musl image

the latest image is from 2025-02-02, not 2026-01-25

if i don't do a xbps-pkgdb -m hold runit and xbps-pkgdb -m hold runit-void

what package versions?

[Duncaen]

One thing to keep in mind is that it takes a really long time until ssh is able to accept connections due to the kernel rng taking time to be usable.

[idlecodinggoats]

Sorry, the image is 2025-02-02 - the font on the page is really small and its hard to see that date, so I just gave the date which I downloaded the image on.

I've got runit-2.1.2_15 and runit-void-20231124_6 installed (and that I've held) and runit-2.3.0_2 and runit-void-20250212_2 are what I get with xbps-query -Rs runit.

I actually managed to get a Touch Display 2 working this evening so I can see what is posted at boot, and after the update to the new versions of runit and runit-void I get an error whilst checking filesystems

/dev/mmcblk0p2 was not cleanly unmounted, check forced.
/dev/mmcblk0p2: Deleted inode 8429 has zero dtime. FIXED.
/dev/mmcblk0p2: ***** REBOOT SYSTEM *****
/dev/mmcblk0p2: 40742/1619904 files (0.2% non-contigous), 617011/7725947 blocks

Cannot continue due to erros above, starting emergency shell.
When ready type exit to continue booting.
/bin/sh: 0: can't access tty; job control turned off
#

I shut down properly so nothing should have been unclearly unmounted but I thought I'd try rebooting again - this time it showed the same thing but a different deleted inode, so I rebooted again with a different inode deleted and finally it booted properly. I'm not quite sure why this would happen. I've now tested this several times with different sd cards and always the same, but eventually I end up with a working system. Happy that I've got a working system, bit confused about whats happening and whether this should be noted somewhere for other raspberry pi void users.

Fortunately it doesn't seem to be waiting a long time to accept connections - I can connect in less than a second from power on.