Ulrich

my last "findings" I have now permanently enabled the power supply for the SD card for testing. Now booting from the SSD works without the SD card being "lost"... My rhyme - at some point the SD card is deprived of the supply voltage and the system "forgets" to reinitialize the card. In my opinion, this is supported by the fact that after removing and reinserting the SD card, it was recognized normally. However, my hopes that the reboot would also work were disappointed. Even if the card is permanently supplied with power, it is not recognized after a reboot and removing and reinserting it does not work either. But I can do without the reboot, now I can at least carry out kernel updates and the kernel is loaded from the SD card as intended.

Addendum... If I remove the SD card after the system has booted from the SSD and then reinsert it, it is recognized: blkid /dev/mmcblk0p1: LABEL="armbi_root" UUID="61748c7e-b234-40e8-b6b6-592f845c3699" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4dfba17f-01" If I then remove the commented lines in the fstab, the SD card is mounted correctly with mount -a as intended. and a very last... screen /dev/tty.usbserial-1420 115200 ..... [ ***] A start job is running for /dev/disk/by-uuid/61748c7e-b234-40e8-b6b6-592f845c3699 (1min 30s / 1min 30s) [ TIME ] Timed out waiting for device /dev/disk/by-uuid/61748c7e-b234-40e8-b6b6-592f845c3699. [DEPEND] Dependency failed for /media/mmcboot. [DEPEND] Dependency failed for /boot. [DEPEND] Dependency failed for Unattended Upgrades Shutdown. [DEPEND] Dependency failed for Local File Systems. [DEPEND] Dependency failed for Mark the need to relabel after reboot. ... ... Give root password for maintenance (or press Control-D to continue): A Control-D does absolutely nothing. Bravely pulled the SD card and reinserted it and the next message was Armbian 23.02.2 Jammy ttyAML0 OdroidC4 login: With my system, unfortunately, it stays the same - without removing and reinserting the SD card, the system hangs on a cold start. Only removing the SD card in the fstab on the SSD card allows the system to boot without an SD card. For me -> freeze kernel updates and if there is really something urgently new, comment out again to get the update on the SD card AND on the boot folder on the SSD. It seems to me that this also has something to do with the bug restart... If I'm brave enough, I'll try to tinker with the Odroid hardware and set the SD card's power supply to fixed 3.3 volts... It's a shame - the way it is, the C4 is really only for "hobbyists"...

Armbian Armbian 22.11.4 Jammy on Odroid C4 boot from SD card system on an ext4 SSD. First of all - everything I need works correctly... However, I have a question about the SD card. During the first installation on the SSD disk, the system hung on the first reboot and you could see from the console that the SD card with UUID=61748c7e-b234-40e8-b6b6-592f845c3699 was being waited for. After the timeout, the only way to fix the "error" was to log into the system via terminal. Long story - only after commenting out the SD card in the fstab on the SSD: UUID=61748c7e-b234-40e8-b6b6-592f845c3699 /media/mmcboot ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 0 /media/mmcboot/boot /boot none bind 0 0 the system booted from the SSD as requested. Since then, the SD card is not mounted and just shows up as: Disk /dev/mmcblk0: 30.61 MiB, 32096256 bytes, 62688 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes at fdisk -l. No UUID etc nothing... The SD-Card is 32G and is readable on other systems... Question now - is this normal? Can I live with that? Can it be fixed? A "curiosity" - after booting from the SSD and updating the kernel to 6.0.13, the update ended up on both the SSD and the unmounted SD card. How - is a mystery to me (;-)