Radxa Zero intermittently won't boot; is my eMMC faulty?

My Radxa Zero doesn’t boot about 1 in 2 times that I plug it in. I have the 2GB RAM variant with 8GB eMMC and I use the eMMC.

I attached to the serial console to try to see what was going on.

I think the interesting parts are as follows:

Bad (no) boot

Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
unable to select a mode : -5
starting USB...
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus usb@ff500000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

(Notable: unable to select a mode : -5)

Good boot

Model: Radxa Zero
SoC:   Amlogic Meson G12A (S905Y2) Revision 28:c (30:2)
DRAM:  2 GiB
MMC:   sd@ffe03000: 0, sd@ffe05000: 1, mmc@ffe07000: 2
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc2(part 0) is current device
Scanning mmc 2:1...
Found U-Boot script /boot/boot.scr
8147 bytes read in 3 ms (2.6 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: amlogic/meson-g12a-radxa-zero.dtb
Current variant:
161 bytes read in 2 ms (78.1 KiB/s)
Current fdtfile after armbianEnv: amlogic/meson-g12a-radxa-zero.dtb
Mainline bootargs: root=UUID=8303053a-4ec2-44c7-b2d2-a548f7341d4f rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=912c31e1-01 libata.force=noncq usb-st
orage.quirks=0x2537:0x1066:u,0x2537:0x1068:u    cgroup_enable=memory swapaccount=1
16178461 bytes read in 752 ms (20.5 MiB/s)
26530304 bytes read in 1232 ms (20.5 MiB/s)
71975 bytes read in 6 ms (11.4 MiB/s)
232 bytes read in 5 ms (44.9 KiB/s)
Applying kernel provided DT fixup script (meson-fixup.scr)
## Executing script at 32000000
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    16178397 Bytes = 15.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04080000
   Booting using the fdt blob at 0x4080000
   Loading Ramdisk to 3f092000, end 3ffffcdd ... OK
   Loading Device Tree to 000000003f018000, end 000000003f091fff ... OK

Starting kernel ...

The full logs are here:
serial_boot.zip (4.9 KB)

Is this a sign of a failing eMMC? I have not used this board very heavily so I am kind of disappointed if it’s that. If not, any ideas on what the cause is and what I can do to avoid this problem?

I’m using Armbian 22.08.6 Jammy if that matters — maybe the UBoot configuration is different?