pygr

A prior version (Armbian_23.5.1_Odroidn2_bookworm_current_6.1.30.img.xz) doesn't show the failures shown in the original post. And for that older version, "lsusb -t" shows the uas driver is being used. To get U-boot to load the kernel, I modified boot.cmd so root_dev is set to the UUID of the SSD file system partition and recompiled with mkimage. I've bitten the bullet and ordered the UART to USB module to see if I can get some better diagnostics from the console.

Hi Igor, Thank you for your suggestion. Unfortunately I couldn't get it to work. 1) Flashed CLI Bookworm image to SD card. 2) Booted up and answered the first startup questions. 3) "lsusb -t" showed uas driver was being used. 4) Edited /boot/armbianEnv.txt, so it now has usbstoragequirks=0x174c:0x55aa:u. 5) Rebooted. "lsusb -t" showed usb-storage was being used instead of uas for an SSD attached through a powered hub. 6) Executed armbian-install. 7) Reboot showed the same behavior as shown in the first post in this thread.

Armbian_23.11.1_Odroidn2_bookworm_current_6.1.63.img.xz was downloaded and flashed to SD card. System booted OK from the SD card and successfully started the OS. Then I used armbian-config to write the root file system to an SSD. After reboot, the system appears to get through the boot stage OK. It also proceeds to start up the OS OK, but then services fail to start. Further action stops temporarily, but pressing the escape key or a function key makes the screen go black for a second or so, returning with what's shown in the last image. No other keys have any effect. The system appears to be locked up and unusable at that point.