kabo

I'm having a very weird issue. I've encrypted a 5TB USB drive on my computer with LUKS sudo cryptsetup luksFormat /dev/sda1 And it works great on my computer. But when I plug in into my Helios64 and try to use it: sudo cryptsetup luksOpen /dev/sda1 secret Enter passphrase for /dev/sda1: No key available with this passphrase. It just refuses. And if I try to encrypt the drive from the Helios64 using cryptsetup it never finishes, the command runs forever. Anyone had similar issues? Any ideas?

OK, so mounting the microSD on my computer, cd boot/dtb/rockchip and running sudo ln -s rk3399-kobol-helios64.dtb rk3399-helios64.dtb allowed me to boot the NAS again I run sudo apt update && sudo apt upgrade regularly, but wasn't aware I needed to run the armbian-config thing to update the bootloader. Thanks for the help!

Is this the same issue I'm having over in this thread? The armbianEnv.txt on my microSD card looked like this verbosity=1 bootlogo=false overlay_prefix=rockchip rootdev=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x3322:u I removed the last usbstoragequirks as that didn't seem to present in anyone else's example I've seen. Made no difference.

Hi, For some reason my Helios64 took a nose dive today, so I hit the reset button and it wouldn't boot up. Plugged in to the serial console and this came out: I'm guessing the relevant lines are libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ... ERROR: Did not find a cmdline Flattened Device Tree Loading Ramdisk to f4f09000, end f5ee4ba4 ... OK FDT and ATAGS support not compiled in - hanging Any ideas on what to do from here please? I'm booting from an SD card which I have checked that it's OK by plugging it into my stationary computer and checking the fs. Crossing my fingers that there's just some command I need to run to generate some file and it'll just work again...