Will Santana

Hi, Just yesterday I had to reinstall my server (odroid-xu4 based). I've been using Armbian a few years now. But this time, no matter if just after a fresh install or after firmware and packages update/upgrade, it fails to reboot I no long have the release number of the previous install I've used, but tryied this time with 22.11.1 and 23.01.1 and both fail the same way After a few debuging it turned out to be that the /etc/fstab entry for the microSD starts just with the UUID code, but adding the "UUID=" string to the line begin, solves the issue Don't know when the bug began or where to properly report the bug, so I started this thread, but I'll be glad to help if more info is needed Thanks in advance!

Just an update I made a fresh install of the same (armbian image 22.01 and then upgraded all available packages), on another SD card and proceeded to load test again with armbianmonitor All cores peaked arount 100% as usual. Installed OMV and even greyhole and no change. All kept working Got back to my installation and thought the only big piece missing was the docker serivce. Stoped docker (and thus it's containers) and all the cores got back to normal. At least for a few minutes. After 1 or 2 tests I realized two cores stuck at 0% again A few reboots (no changes made) and I was able to use all cores even with docker and some containers running as shown bellow Unfurnatelly after some load tests, some cores got stuck again The last thing I'm thinking of is that the new installation runs out of an SSD and a new USB to SATA bridge. The SSD is healthy and fine, but maybe it's causing an overrun. Or maybe a faulty SATA brigde stalling IO operations and locking the cores I'll be back as soon I can with further tests Att, Will

I'm using OMV ontop of armbian with multiple containers despite the processes (like greyhole and mariadb) running in the host itself Maybe it's something related to the kernel mods that OMV does to Armbian I've been using armbian + OMV for a few years now and never noticed this behaviour before. If it wasn't such a job switching back to an old release to test again, I would do it I moved some containers to a C2 I had for the moment but using "half" the processing power of the XU4 is such a shame

Hi, gotta ask a question Recently I just reinstalled all my XU4 based server from scratch. Brand new armbian Bullseye with OMV on top installed via armbian-config Then I noticed as seem bellow that half the cores (the low power ones) are idling, even when the system is fully under load on the high power cores The cores are enabled in the /sys/devices/system/cpu/cpuX/online files So the question is "what's wrong"? I don't have prints but I remember all the cores working before Thanks in advance Will

Thanks internet Completely random, but about 1 year later I just had the same issue with another kernel upgrade a few minutes ago This thread just popped in my searchs and I took some time to realize I was the OP Hahahahahha

Sorry it took so long to reply. As a new user I got a 2 posts/day limit and had to wait until it refreshed. Just to let you know that (as expected) it worked Mapped the SD partition to /mnt (mount /dev/mmcblk1p1 /mnt), then mapped /mnt/boot to /boot (mount --bind /mnt/boot /boot) and ran the upgrade via armbian-config again with no errors at all All my apps are back up and running Thank you so much for your help If I could add something to the discution, that would be that when detected that the OS is running from and external device (it seems to have been done as you can't run "nand-sata-insall" twice), then the kernel upgrade procedure in armbian-config should map de SD to the proper location automatically, saving more unexperienced people from crashing their systems with something quite simple Once more, HUGE thanks for your help Att, Will

Sorry it took so long to reply. As a new user I got a 2 posts/day limit and had to wait until it refreshed.

Thanks for the fast reply, Igor You mean I should overwrite the zImage, uInitrd and dtb "files" (links, but the files they point to) copying form the HDD to the SD Card? What about the System.map and config files? Their dates are older, but also named as 4.14.195 HDD /boot content: SD Card /boot content Att, Will

Hi, guys. Little help here After being tired of my docker containers loosing connectivity to the internet I've decided to fully update/upgrade armbian (including the kernel) Now my system boots but most applications don't work. Most cases are missing kernel modules The /lib/modules dir contains the new updated content as the /boot too But the system keeps booting the old kernel image (4.14.176) and not the new one (4.14.195). It makes no difference if I upgrade the kernel via apt or via armbian-config I guess the issue is the files still in the SD card used for boot (they are 4.14.176 by it's names). Shouldn't armbian-config update those files? If not, how do I update them so my apps can get back to work? I've mounted /dev/mmcblk1p1 and have access to the files, just don't know which ones I should overwrite Thanks in advance Will