Hello, I've been trying to use the automated script on an Odriod HC4 running Ubuntu Jammy 5.17.5, but it always fails at some point after running APT with some illegal instruction errors. I pasted the output of the script below. I've never really asked for help on one of these forums before and I'm kind of a noob, so if I'm doing something wrong or if more information is needed then let me know.
┌───────────────────────────────────────────────────┐
│ ⣎⣱ ⡀⣀ ⣀⣀ ⣇⡀ ⠄ ⢀⣀ ⣀⡀ ⣏⡉ ⣀⡀ ⢀⣀ ⡀⣀ ⡀⢀ ⣀⡀ ⣰⡀ ⢀⡀ ⢀⣸ │
│ ⠇⠸ ⠏ ⠇⠇⠇ ⠧⠜ ⠇ ⠣⠼ ⠇⠸ ⠧⠤ ⠇⠸ ⠣⠤ ⠏ ⣑⡺ ⡧⠜ ⠘⠤ ⠣⠭ ⠣⠼ │
│ ⣏⡱ ⢀⡀ ⢀⡀ ⣰⡀ ⣏⡉ ⠄ ⡇ ⢀⡀ ⢀⣀ ⡀⢀ ⢀⣀ ⣰⡀ ⢀⡀ ⣀⣀ │
│ ⠇⠱ ⠣⠜ ⠣⠜ ⠘⠤ ⠇ ⠇ ⠣ ⠣⠭ ⠭⠕ ⣑⡺ ⠭⠕ ⠘⠤ ⠣⠭ ⠇⠇⠇ │
│ ⢎⡑ ⢀⡀ ⣰⡀ ⡀⢀ ⣀⡀ │
│ ⠢⠜ ⠣⠭ ⠘⠤ ⠣⠼ ⡧⠜ │
└───────────────────────────────────────────────────┘
For detailed usage information,
invoke with the '-h' switch
get_armbian_image OK
apt_install_host OK
close_loopmount OK
umount_target OK
remove_build_dir OK
Will write to target /dev/sda (Mass Storage Device 59.5G)
check_sdcard_name_and_params OK
create_build_dir OK
Enter the IP address of the target machine.
Enter 'dhcp' for a dynamic IP or 'none' for no remote SSH unlocking support
IP address: 192.168.1.5
Enter the netmask of the target machine,
or hit ENTER for the default (255.255.255.0):
Enter a boot partition label for the target machine,
or hit ENTER for the default (ARMBIAN_BOOT):
Enter a device name for the encrypted root filesystem,
or hit ENTER for the default (rootfs):
Choose a simple disk password for the installation process.
Once your encrypted system is up and running, you can change
the password using the 'cryptsetup' command.
Enter password: 123
Unlock the disk from the serial console. WARNING: enabling this will
make it impossible to unlock the disk using the keyboard and monitor,
though unlocking via SSH will still work.
Enable unlocking via serial console? (y/n): n
Unlock the disk via SSH over USB (g_ether). Enable this only if your board
supports USB gadget mode, i.e. if it has a USB OTG port. WARNING: enabling this
will make it impossible to unlock the disk over the Ethernet interface (eth0).
Enable unlocking via SSH over USB? (y/n): n
The following user options are in effect:
+ use local 'authorized_keys' file
Armbian image: Armbian_22.05.1_Odroidhc4_jammy_edge_5.17.5.img
Target device: /dev/sda (Mass Storage Device 59.5G)
Root filesystem device name: /dev/mapper/rootfs
Target IP address: 192.168.1.5
Target netmask: 255.255.255.0
Boot partition label: ARMBIAN_BOOT
Disk password: 123
Serial console unlocking: no
SSH over USB unlocking: no
Are these settings correct? (Y/n) y
get_authorized_keys OK
Copying boot loader (8192 sectors, 4M):
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.421957 s, 9.9 MB/s
copy_boot_loader OK
partition_sd_card OK
Copying files to boot partition:
101,080,678 99% 10.77MB/s 0:00:08 (xfr#145, to-chk=0/152)
copy_system_boot OK
create_bootpart_label OK
Copying system to encrypted root partition:
1,186,326,943 99% 16.16MB/s 0:01:09 (xfr#37888, to-chk=0/47428)
copy_system_root OK
mount_target OK
Host Target
---- ------
distro: jammy jammy
kernel: vmlinuz-5.17.5-meson64 vmlinuz-5.17.5-meson64
Unable to copy '/etc/apt/apt.conf.d/*proxy' to target (file does not exist)
armbian_rootenc_setup.sh:891: _copy_to_target() failed at command 'false'
Host script exiting with error (1)
armbian_rootenc_setup.sh:905: copy_etc_files() failed at command 'false'
Host script exiting with error (1)
copy_etc_files OK
copy_etc_files_distro_specific OK
edit_initramfs_conf OK
edit_initramfs_modules OK
copy_authorized_keys OK
create_etc_crypttab OK
create_fstab OK
edit_dropbear_cfg OK
netman_manage_usb0 OK
ifupdown_config_usb0 OK
create_cryptroot_unlock_sh OK
edit_armbianEnv OK
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
bash-completion*
0 upgraded, 0 newly installed, 1 to remove and 31 not upgraded.
After this operation, 1,499 kB disk space will be freed.
(Reading database ... 41456 files and directories currently installed.)
Removing bash-completion (1:2.11-5ubuntu1) ...
Processing triggers for man-db (2.10.2-1) ...
(Reading database ... 40694 files and directories currently installed.)
Purging configuration files for bash-completion (1:2.11-5ubuntu1) ...
Generating 256 bit ecdsa key, this may take a while...
256 SHA256:kcNv1yOFs+xQjuvdzjF23A6r/Qy4BK6dKaLf7A1bK3c /etc/dropbear/initramfs/dropbear_ecdsa_host_key (ECDSA)
+---[ECDSA 256]---+
| |
| . . . |
| = + . |
| + = = |
| S * * o |
| o * o o.|
| . + + * +|
| .ooO.*E* X |
| .o.o*+B.+o*.+|
+----[SHA256]-----+
Generating Dropbear ED25519 host key. Please wait.
Generating 256 bit ed25519 key, this may take a while...
256 SHA256:M2QMUYkhLLtOLyRZRDUfguhidpEAEp5o6i9WNmBoc1w /etc/dropbear/initramfs/dropbear_ed25519_host_key (ED25519)
+--[ED25519 256]--+
|==o+* ==.. |
|= =o.E.+. |
|+=.oo . + |
|=Oo+ o |
|Bo=. S |
|+ ++ o |
| *o.. |
| o+ . |
|. .o |
+----[SHA256]-----+
update-initramfs: deferring update (trigger activated)
Dropbear has been added to the initramfs. Don't forget to check
your "ip=" kernel bootparameter to match your desired initramfs
ip configuration.
rmdir: failed to remove '/etc/dropbear-initramfs': Directory not empty
ERROR: Couldn't remove directory /etc/dropbear-initramfs
Processing triggers for libc-bin (2.35-0ubuntu3) ...
Illegal instruction
Illegal instruction
dpkg: error processing package libc-bin (--configure):
installed libc-bin package post-installation script subprocess returned error exit status 132
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for initramfs-tools (0.140ubuntu13) ...
update-initramfs: Generating /boot/initrd.img-5.17.5-meson64
Illegal instruction
Illegal instruction
update-initramfs: Converting to u-boot format
Errors were encountered while processing:
libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
armbian_rootenc_setup.sh:1149: apt_install_target() failed at command 'apt --yes install $pkgs'
Target script exiting with error (100)
armbian_rootenc_setup.sh:1213: configure_target() failed at command 'chroot $TARGET_ROOT "./$PROGNAME" $ORIG_OPTS 'in_target''
Host script exiting with error (100)
Cleaning up, please wait...
close_loopmount OK
umount_target OK
update_config_vars_file OK
remove_build_dir OK
