Only way I finally got this image to work, was by disabling UAS, BEFORE!! first boot. Adaptor is UAS compatible, and works fine on other images with UAS enabled, but not this one. So it will work if one does that, albeit at the expense of drive speed, which you probably wont notice anyway.
Shutting the gate after the horse has bolted is no good here
It must be done 'before' you boot the device, else it will not boot again, until you start from the beginning again.
My theory is that, files are getting corrupted during the extending process on first boot, with UAS enabled, thus the system will not boot again after this process. Disabling UAS 'beforehand' allows the process to complete, without error, thus boot successfully thereafter.
Now. Could one simply re-enable UAS once system is booting fine? I don't know? I may just try that, out of curiosity