Unable to install OSMC on Pi 3a+

I have tried multiple times to install OSMC on a Raspberry Pi 3a+ with no success, and failure at the same point each time.

I have downloaded the disk image (OSMC_TGT_rbp2_20210808.img) and used Balena Etcher to flash it to 2 different SD cards, each of which have been able to complete successful installs of other OS’s on the same Pi. I downloaded the image again to make sure there was nothing wrong with the downloaded image and no success when using that image either.

I used the installation tool in Windows and provided the SSID and WPA key for my network. No success there on either SD card.

When powering on the Pi when putting in a freshly flashed SD card it goes through ‘Formatting Device’ pretty quickly, then takes a few minutes to go through the ‘Installing Files’ progress bar. That completes and then it reboots. Upon reboot I get a flashing sad face screen with “A start job is running for Set Time using HTTP query (xxs / no limit)” at the top, after about 90s that will go away and we get ‘Started Network Time Service’ and the Multi-User and Graphical Interface Targets met.

Then it starts “Update UTMP about System Runlevel Changes.” and hangs there (forever?) for up to as much as 10 minutes before I give up and unplug the Pi.

Here’s one of the install.log files

Thu Jan 1 00:00:09 1970 Starting OSMC installer
Thu Jan 1 00:00:16 1970 Detecting device we are running on
Thu Jan 1 00:00:16 1970 Mounting boot filesystem
Thu Jan 1 00:00:16 1970 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:00:16 1970 Using device->boot: /dev/mmcblk0p1 and FS: fat32
Thu Jan 1 00:00:16 1970 Filesystem defined by /mnt/boot/filesystem.tar.xz
Thu Jan 1 00:00:16 1970 Preseed file found, will attempt to parse
Thu Jan 1 00:00:16 1970 Found a definition for storage: sd
Thu Jan 1 00:00:16 1970 Creating root partition
Thu Jan 1 00:00:16 1970 From a root partition of /dev/mmcblk0p2, I have deduced a base device of /dev/mmcblk0
Thu Jan 1 00:00:16 1970 Determined 320 MiB as end of first partition
Thu Jan 1 00:00:16 1970 Calling mkpart for device: /dev/mmcblk0 and fs: ext4 with start 320MiB and end 100%
Thu Jan 1 00:00:18 1970 Calling fmtpart for partition /dev/mmcblk0p2 and fstype ext4
Thu Jan 1 00:00:31 1970 Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=2 blocks, Stripe width=1024 blocks
1875968 inodes, 7490560 blocks
374528 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
229 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000

Allocating group tables:   0/229187/229       done                            
Writing inode tables:   0/229       done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information:   0/229       done


Thu Jan 1 00:00:31 1970 Mounting root
Thu Jan 1 00:00:31 1970 Trying to mount to MNT_ROOT (/mnt/root)
Thu Jan 1 00:00:31 1970 Using device->root: /dev/mmcblk0p2
Thu Jan 1 00:00:31 1970 Extracting files to root filesystem
Thu Jan 1 00:00:31 1970 Starting extract process ...
Thu Jan 1 00:00:31 1970 Extracting from /mnt/boot/filesystem.tar.xz
Thu Jan 1 00:03:18 1970 Extraction of root filesystem completed
Thu Jan 1 00:03:18 1970 Configuring bootloader
Thu Jan 1 00:03:18 1970 Configuring bootloader: moving /boot to appropriate boot partition
Thu Jan 1 00:03:24 1970 Configuring boot cmdline
Thu Jan 1 00:03:24 1970 Configuring /etc/fstab
Thu Jan 1 00:03:24 1970 Successful installation. Dumping log and rebooting system

Suggestions? Troubleshooting steps? Logs to look in for clues?

I haven’t switched power supplies, but the one I’m using is able to run Raspbian, RetroPi, and Kali just fine on the same Pi that OSMC is failing on, and it reads 5.25 V across the test pads with a multimeter.

This function is currently broken. Don’t use the preconfiguration for network.

I’ve tried multiple times without that function and install fails in exactly the same manner.

Successful install with older release (20201227)

The Pi 3A has only 512 MB of memory.

In a recent thread, the latest version of OSMC was running out of memory after a fresh install: Sad face loop on first boot (FS fresh from image) - #11 by dillthedog

With the move to Kodi 19 and kernel 5.10, Sam has dropped support for the Pi 1 and Zero models, both of which are ARMv6 devices. They are also 512 MB devices, so perhaps @sam_nazarko can say definitively whether 512 MB ARMv7 devices are still supported.