Jump to content

MMGen

Members
  • Posts

    38
  • Joined

  • Last visited

Other groups

Long-term editor

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @DIYprojectz: Thanks for the feedback and support! First of all, make sure your Internet connection is active as you perform the steps in the tutorial. If it is, you should have a non-empty /etc/resolv.conf file, and the cat command will successfully create a copy of the file's contents in the target. If that doesn't solve the problem, then here are some things you might try: What does `ls -l /etc/resolv.conf` on the host produce? Is the resolv.conf file on the host a symlink? If so, you might try running `systemctl restart resolvconf` and then rechecking the file. If the host is using systemd-resolved for address resolution, try restarting that instead.
  2. The tutorial and automated script have been updated for Debian bookworm and Ubuntu noble images. Here's a summary of the changes required to make everything work: replace eth0 with end0 replace cryptsetup-bin with cryptsetup replace lsinitramfs /boot/initrd.img* with lsinitramfs /boot/initrd.img-* replace etc/dropbear-initramfs with etc/dropbear/initramfs replace etc/dropbear-initramfs/config with etc/dropbear/initramfs/dropbear.conf before exiting the chroot, execute ssh-keygen -A
  3. @DIYprojectz: It should be possible to put the encrypted root filesystem on a different device than the boot partition, though I've never tried it with an SoC or Armbian. Thanks for the idea. I promise to look into it, but don't expect immediate results as I'm busy with other things at the moment.
  4. Sorry for the extreme delay in replying to your post. Since the errors are coming from APT, this could be a distro-specific problem. Have you tried the Bullseye image?
  5. Glad you got it to work. Instead of setting up the LUKS partition manually, erasing everything with the -z option might have solved the problem here.
  6. Are you able to unlock the device via SSH as per the instructions? Can you ping the device at the expected address? Note that the script has been updated, so you might clone or pull the new version from Github and try running it again.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines