Dangerous to reboot without a backup when facing errors during upgrade. When those errors happened during or affected a kernel upgrade, this can make the system unbootable.
The errors look bad indeed, like systemd hangup. Filesystem corruption likely.
~# uname-a
-bash: uname-a: command not found
It’s uname -a with a space. uname is the command/executable, -a an option to show all details about your kernel.
Do you have another Linux system where you can attach and inspect/repair this Odroid’s system drive?
Yes, a full image backup is best of course. A dietpi-backup onto another drive, or even the same, is simpler to setup as regular task, and allows as well to restore kernel and boot configs e.g., when broken.
Filesystem errors:
fsck /dev/sdb1
or whatever the drive is named . And then, try to mount and check its /boot directory.
More like a GUI for rsync with some wrapping features. rpi-clone clones a disk, dietpi-backup copies the files within the filesystem, excluding partitioning, bootloader etc. Files can be restored from a running system, a disk clone/image not, but from an external system instead.
Actually doing more regular a dietpi-backup (which doesn’t take so much time and writes, as it is incremental), and less regular a full disk clone/image, either via something like rpi-clone or manually from an external system, is a good combination.
I was able to check for filesystem errors, none found. went into /boot and all looks good but I am no expert and don’t know what to look for.
Guess I will retry with a new SD card.