jshc1

not_logged_in_yet does not occur with omv, at least I never saw it after logging in.

Quoting @ryecoaaron

It's hard to say, at the moment it works for me. Try deleting this script "armbian-check-first-login.sh" and reboot, check cron ...

Not only xrdp, omv cron has problems too.

My HC1, after exceeding 110, just went out. I'd rather avoid going over 100. With a well-matched kernel has 1500 and 2000 on the BIG. When all the cores are working intensively, samsung heats up very quickly and is just reaching those 90-100C. Much depends on the ambient temperature and HDD / SSD. This passive cpu cooling is very inefficient. If you often have a large load, think about a fan. Also make sure you have scaling_governor on demand. Mine in the area over 60 starts to go down to 1400/1900 - 1300/1800 and so on ... You can also check if the cpu touches the surface well, or replace the thermo pad.

I think the update messed up something. Many things that had "bin/sh" like xrdp have a problem now. Changing to bin/bash helps in some cases...

I can confirm 5.4.19 works on HC1.

If I find time after Sunday, I will check my Hc1.

More or less. The blue LED can say a lot, especially if the person cannot connect the console. This was useful not so long ago in the 5.x kernel where after upgrading from 4.14 simply Odroid HC does not boot and the diode just lights up all the time indicating that the sbc is hanging. For example, if the sd card were damaged and the boot partition is missing, the LED would not light up at all, the same effect as without an sd card. For novice users it is always best to stick to the standards because later unnecessary problems are created especially with headless sbc and no uart.

I would recommend changes to settings only for advanced users. Changes for fun can only make future diagnostics more difficult when someone changes the heartbeat and then it can only result in unnecessary confusion.

I'm not sure. It is possible that somewhere on the odroid forum / wiki something is about it. I wrote it from my own observations based on Odroid HC1, which I had for two years.

ssh -v may tell you something more. (ssh -v root@IP) I have never had a problem with armbian and ssh on the first login. Try again from the beginning ...

Odroid does not behave like PI. Odroid has one blue diode which signals heartbeat signal. After connecting the power it will light up. If it finds a boot and starts booting, it will start flashing. The blinking speed depends on the load. The red LED is on all the time when the current reaches the sbc. The green LED lights up when HDD is connected, blinks when HDD has activity. The first start of Armbian needs about 30 seconds before it is ready for the first login.

Maybe not use dd .... 1. Install the latest version of balenaEtcher. 2. Make sure your sd card is ok and the system is able to save files / create partitions on it. 3. Download the correct Armbian file, maybe https://dl.armbian.com/odroidxu4/Buster_legacy 4. Extract Armbian from 7z. 5. Run balenaEtcher (as root) select the Armbian_20.02.0-rc1_Odroidxu4_buster_legacy_4.14.165.img and write to the card. 6. Must work. If nothing is dumped on the sd card then try on a different system / sd card. If that's such a problem then I can make a clean copy of the system with the help of acronis true image and you will use it ... But I don't see such a need.