Comment 9 for bug 1969529

@mardy I would be very surprised if SD card corruption was the issue here. The cards I'm using for test have had no issues booting any of the images so far (and typically whenever I've seen SD corruption before it's usually pretty obvious from boot time).

Which I/O errors in the logs have caught your attention, particularly? Some are "expected" unfortunately. For example:

Apr 20 12:23:25 localhost.localdomain systemd-modules-load[318]: Failed to find module 'ipmi-devintf'

This is because that modules is not included in the stripped down linux-modules package from linux-raspi.

Apr 20 12:23:29 localhost.localdomain kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2

This one is because the wifi firmware blob first tries to load a device-specific configuration (the "raspberrypi,400" bit in the filename) and falls back to a generic configuration if no device-specific one is found (unfortunately it falls back rather noisily!).

Apr 20 12:25:02 localhost.localdomain pulseaudio[832]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.

I forget the reason for this one, but it's another of "expected" errors we see on the Pi (but audio still works happily so cleaning the false report up hasn't been a high priority).

Anyway, I'll try another replication later today and see if I can gather any more info. Thanks for you attention!