When I check the eMMC from the Disk utility, it shows that it's normal. I can also boot the android distro that came with it normally.

 

Help? 🥲

AFAIK armbianinstall expects an empty eMMC without partitions. This should be easily achievable by overwriting the first few sectors of it. Like dd if=/dev/zero of=/dev/mmcblkX bs=512 count=1

A reboot might be required to make the OS aware of the altered partition table. Then retry installing.

Thank you Werner!! I will try and share the results.

Well turns out my eMMC drive is mounted at /dev/mmcblk0p1...but armbian-config tries to install at /dev/mmcblk0p2, which doesn't even exist (Nevermind df command didn't show it but fdisk -l did)

Edited March 16, 20251 yr by devmichelcastilho
typo

I've overwritten the first few sectors of mmcblk0p2 as suggested, rebooted and tried again, same result.

 

Deleted all partitions, rebooted and tried again, same result and this returned:

 

Quote

[ 151.337977] ext4: Unknown parameter 'compress-force'

 

I had installed stuff and slightly increased the system space usage, it's likely it was bigger than the partition created for the system on the eMMC. Since the whole system is copied as is, I assume it tried to copy the whole thing with the additional stuff and went over the available space.

After flashing a fresh install into the SD card, I tried it again and it worked first try.

5 hours ago, devmichelcastilho said:

I assume it tried to copy the whole thing

Single board computers are purpose oriented devices, where booting and using live OS is common. This is how installer was designed - you can boot and run OS from SD card. And move OS to internal memory at any moment - freshly & clean, after one year, never.