I am 95% sure this happens even on a plain Armbian install. I'll double check. Some news: - it does not happen on all SATA devices (booted fine with 1 SSD) - power supply seems fine; marked 4.0 A There is a workaround! press any key to interrupt boot (be fast, 2 second timer) scsi scan # wait under 2 minutes boot # similar output to "failed" boots # but after under 2 minutes, it will continue into the boot process Does anyone know how I could put these steps into the boot process automatically?

Hello everybody, With 6.18.10-current-rockchip64 and rk3399-kobol-helios64.dtb-6.18.18-opp dtb file, Ok With 6.18.35-current-rockchip64 and overlay helios64 patch with armbian-config, Ko With 6.18.35-current-rockchip64 and k3399-kobol-helios64.dtb-6.18.18-opp dtb file, Ko The crash is random... sometime crash: - At the boot with red system light blinking - At the opening of my LUKS ciffers drives - At a high cpu load - With nothing special, all led are blue, system blinking but network and ssh is Ko Is it possible to explain me how to see the problem or how to have log because I am in blind to have more details ? Is it possible to explain me how to pass to the last 6.18.36 kernel to seen if it is better than 6.18.35 ? Thanks a lot.

I suggest to ask at dietpi forums, since we cannot help with 3rd party os/scripts.

Thank you, bro. I'll try it this evening after work. I'll post the results.

I want to install an image from the sd card to the internal memory in x96q tv box, it boots perfectly from sd card, without having to press anything, and everything works ok, even bluetooth adapter and video reproduction, my question is "do i still need to modify boot files to install in emmc or is not necessary? thanks in advance....