leafybasil

At the time of posting I had tested all released images, and used the framework to build current and edge. None of them worked. I also used petitboot to install Debian in case that had fixes, but it did not. I have picked up a spare SD card so I can periodically test new releases. It's just a media NAS for me so as long as my drives remain safe I can test various images.

@amissogen glad you posted, I thought I had tried all the 5.x Armbian images, but it turns out I did not, and I now have one that works thanks to you. Issues around this stuff go back a year or two, so it's not hugely likely it would get fixed unless someone with particular knowledge tries. I will comment on the hardkernel/odroid forums too and add another voice. I have tried looking into this myself, but there are too many moving pieces and I know nothing about any of them, so it's challenging to say the least.

I recently installed the latest precompiled Bullseye image on my Odroid HC4 and plugged in two Samsung 870 QVO 8TB SSDs. After configuring the system I noticed that they were not present, checking output from `/var/log/syslog` I can see the "SATA Llink down" messages for both channels. After several reboots I tried seating them after booting, both drives cause some messages about a soft reset failing, then eventually within 30-60 seconds are recognised until I reboot. I then one Crucial MX500 4TB SSDs which was recognised at first, after some reboots it would no longer be present, or strangely, be present with a much lower capacity (1TB). When seating the drive after boot, it instantly becomes available/recognised. I went back to trying an old 250GB Kingston SSD (SA400S37240G) which is detected every single boot, just fine. The same is also true for some old Seagate/Western Digital HDDs. I eventually tried some other distros, namely DietPI which behaves exactly the same. I eventually tried all available precompiled Armbian 5.x and 4.x images but they all behaved the same way. Finally I tried the Hardkernel Odroid Ubuntu image, and this seems to work fine, for all of the drives listed above. Noting it's a 4.9 kernel, I assumed I might get the same functionality from Armbian if I compiled it myself, however the build system seems specifically geared toward current/edge, judging by the configs, this is usually 6.x and 5.x. After some fiddling I was able to start the process of building a 4.9 image, but due to other expectations the compilation fails much later on. I've seen posts here and elsewhere online about faulty NCQ for the Samsung drives, apparently fixed with my firmware version and also blacklisted by the driver anyway. I've seen posts about the Crucial MX500 and other drives appearing and disappearing between boots. Those people had access to even earlier kernels and managed to downgrade to keep things working, but they are no longer available. So I'm at a loss. Any advice would be appreciated. armbianmonitor: https://paste.armbian.com/gexecuzuja