You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please create an image of any existing armbian installation. Then (assuming it is in armbian.img file) do as following (attention: if test is done please make sure that UUIDs of source system are different that the system on which test is done):
losetup -P /dev/loop0 armbian.img
then:
mkdir /tmp/armbian mount /dev/loop0p1 /tmp/armbian
... now it is good idea to mount some of other directories (by bind mount):
mount --bind /proc /tmp/armbian/proc mount --bind /dev /tmp/armbian/dev mount --bind /sys /tmp/armbian/sys mount --bind /run /tmp/armbian/run mount --bind /tmp /tmp/armbian/tmp
and run "chrooted" environment:
chroot /tmp/armbian
next steps will be to use scripts etc. They should be applied to /dev/loop0 (if we are talking about devices) or /dev/loop0p1 (if partition is in the scope). NOT to the block devices of host (test) system (which is actually the problem when reading /proc/cmdline.
When using nand-sata-install script the issue is with line which recognizes root device:
This code ignores the fact, that root device may be eg. chrooted from image (loopback). It is always returning UUID of root of host system.
The fix would be to replace (line 43) it with:
Then it is correctly recognizing root device and later partitions etc.:
non-chrooted:

chrooted (image is mounted as looppack device):

The text was updated successfully, but these errors were encountered: