mortee

I'm using Armbian bullseye on an Odroid HC2 with 2 GB of RAM with OpenMediaVault. Its memory usage used to be around 10% before starting any docker services, and a cool 50-60% while running things like Nextcloud, Vaultwarden etc. It used to jump to around 80% when some headless Chromium processes ran intermittently, but overall, it's been quite stable. I don't recall to make any significant changes to the system, yet suddenly the baseline memory usage jumped to around 50%, making my system extremely slow and unstable, with service and system restarts now occuring several times a day. I couldn't extract any useful clue about what's using all that RAM, with `systemd-cgtop -m` showing system.slice using half my memory, without any services therein apparently making up that amount. Unfortunately, I can't make comparisons of `/proc/meminfo`, output of `free` or any other method relative to the before-state, because I obviously haven't monitored these until it became an issue, and now I can't restore the normal state. How would I go about addressing this problem?

Hi, I've got an Odroid HC2 with Armbian Buster and OMV on it, and the SD card I used it with got corrupted. So I salvaged all the files from it and backups, and restored the whole file structure onto a new SD card, with an ext4 MBR primary partition. Now, my concern is, how can I make this bootable? I can boot the HC2 off a throwaway newly installed Armbian, and access the target SD card through a USB card reader. I could google that armbian-config is used to install the bootloader, but apparently it can only do that to the card which has been used to boot the device in the first place. Any suggestions? thanks