php

Thanks @umiddelb, that sounds much more elegant than my approach of powering up without the microSD card inserted :-)

Thanks for that tip @Igor Is there any diagnostic value in gathering those logs even after I changed my boot args to get back up and running? I could revert the change to the boot args if helpful.

I don't know what precipitated the change from mmcblk0 to mmcblk1, but after upgrading to armbian 5.38 I'm running kernel 4.14.14

Hi @chrisf, you're quite right, the uboot environment variables use /dev/mmcblk0p1. So for anyone else who has this problem, these instructions (for ubuntu, but still apply) show bootmmc and bootcmd, both of which need to be changed to /dev/mmcblk1p1 (but don't change anything else). Thanks for the tip!

Hi @umiddelb, thanks for your suggestion but I'm confused. In my log above, it's trying to boot from mmcblk1p1. My armbianEnv.txt file looks like this, already with the UUID of my microSD card (verified in Ubuntu) verbosity=1 emmc_fix=off eth1addr=00:50:43:25:fb:84 eth2addr=00:50:43:84:25:2f eth3addr=00:50:43:0d:19:18 rootdev=UUID=dc2768b6-c4f5-466e-83c1-6cf4aa49a898 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u For kicks I changed it to `rootdev=/dev/mmcblk1p1` but got the same result. Can you provide a reference to the change you mention? I looked at the commit history for boot-espressobin.cmd but it doesn't show recent changes.

I've been running 5.36 successfully on my espressobin. Saw the upgrade to 5.38, so ran apt-get update and upgrade. Now the boot process shows this log snippet: [ 6.251662] md: autorun ... [ 6.254188] md: ... autorun DONE. [ 6.258090] Waiting for root device /dev/mmcblk0p1... [ 6.267577] mmc1: new high speed SDHC card at address aaaa [ 6.273478] mmcblk1: mmc1:aaaa SL16G 14.8 GiB [ 6.279091] mmcblk1: p1 [ 201.869175] random: crng init done I've let it sit for a while after this (200 seconds in), but no more log lines. Any other espressobin users successfully running 5.38?