jiko

Is this still an issue? A nice way to backup DB's these days is to use either LVM or BTRFS snapshots for crash-consistent backups. Each of them is done differently, but they give you point in time recovery. The right way to get clean backups of Postgres is to dump the data out and put that somewhere safe. It's been a long time since I've used LVM for this, so I'm not going to recommend anything there. For BTRFS snapshots, you can use snapper for local backups or btrfs-sxbackup for local and/or remote backups. The advantage of btrfs-sxbackup here is that it will do filesystem level incremental backups which is faster than checking and copying files. For the PG backups there's a tool to automate it for you: autopostgresqlbackup. Remember you will still need to get those backups off the system.

Unfortunately I've had issues with all kernels on the NanoPi M4v2., and thanks to your post I've successfully switched between legacy, current & dev kernels after updating `LINUXFAMILY` in `/etc/armbian-release`. One thing I'd warn about is that when you switch to the rockchip64 family the legacy kernels there failed to boot for me and I had to recover my `/boot` volume via a fresh SD card boot using a legacy image. After manual recovery I was able to use my old eMMC installation, and eventually when I was ready I switched back to the rockchip64 family where I've found the _current_ (5.4.49) and dev (5.6.17 and 5.7.6) kernels all successfully boot.

I modified a script from another thread for my fan via the SATA hat on a NanoPi M4v2: https://gitlab.com/snippets/1993413 I had some strange behaviour with the needed PWM values getting inverted between reboots, but that seems to have settled now.