UPDATE: I figured out what I did wrong. I duplicated the image of the os onto the harddrive, it inherited the same uuid. here’s a line to kill the formatting of the hd
sudo shred -vfn1 /dev/sda
I recently obtained an Odroid HC1 (unfortunately right before the HC2 was released). I decided on armbian as OS of choice and came across an issue with the uuid conflicting with the memory card and harddrive. I dug around the internet not knowing what the cause was but I did come across a solution by changing the uuid of the hard drive. Changing the uuid of the memory card would probably stop my armbian from booting.
root@odroidxu4:~$ sudo lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
mmcblk1
└─mmcblk1p1 ext4 ee2ae90b-a2f8-470f-a0f6-ff8feba09358 /
sda
└─sda1 ext4 ee2ae90b-a2f8-470f-a0f6-ff8feba09358
root@odroidxu4:~$ sudo apt-get install uuid-runtime
root@odroidxu4:~$ uuidgen
9856fbf4-d582-42e3-8ab0-b569e73ab6fc
root@odroidxu4:~$ sudo tune2fs /dev/sda1 -U 9856fbf4-d582-42e3-8ab0-b569e73ab6fc
tune2fs 1.42.12 (29-Aug-2014)
root@odroidxu4:~$ sudo lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
mmcblk1
└─mmcblk1p1 ext4 ee2ae90b-a2f8-470f-a0f6-ff8feba09358 /
sda
└─sda1 ext4 9856fbf4-d582-42e3-8ab0-b569e73ab6fc