meesha

It actually is. After rsync'ing files to another device, remove the directory /boot from there. Then, after restart, mount the filesystem on the sdcard to somewhere on the new filesystem. Mine is at /mnt/sdcard. To achieve this, add a line to /etc/fstab like: /dev/mmcblk1p1 /mnt/sdcard ext4 defaults, noatime,nodiratime 0 2 after creating the actual directory in /mnt. Then, issue just once a command: ln -s /mnt/sdcard/boot /boot And it will be there each time you restart, also allowing the updater to put firmware files where they should be. And it runs now perfectly.

Guys, on the topic, but with my own variation of the problem. Got me a rockpi 4b which I run headless. Since I have a history with many SBCs of other well-known manufacturer and a lot of microsd cards that died on me, I immediately moved my armbian install into usb attached ssd, but was not aware of that fine tool that already comes with the system. I just rsync'ed the root filesystem and changed the rootdev in armbianenv.txt. It works, but had issue with some of last major updates - the system couldn't boot. I had to change the rootdev to point the microsd card back, update the system on the card, and then change the rootdev again to ssd. Then it booted (but still had to manually install kernel modules for some devices to work). Now, the question - is there any way to tell the updater that it should change firmware (i.e. kernel image) on the microsd despite having rootfs on other device?