rosbeef

  • Content Count

    10
  • Joined

  • Last visited

  1. I can not run it because i can not boot on my ssd and in chroot i can not execute systemctl poweroff. Thank you
  2. Hi @belegdol Do you think this thread is more or less the same problem ? 17371-no-access-after-reboot-odroid-hc1-fde Each time kernel upgrades my server stop working and i have to reinstall from scratch . Then i don't really understand what you did to correct the bug.
  3. Hello Just adding more informations in case someone could help. I tried to rsync my sdcard to my ssd and the problem is the same. booting on sdcard ( specifying root="root=UUID=sdcard uuid" in the boot.ini ) open initramfs then ask for cryptrootunlock pass then switch well on sdcard file system. from there ssd is uncrypted and is accessible. booting on ssd ( specifying root=/dev/sdg/root cryptopts=source=/dev/sda,target=sdc,lvm=sdg in the boot.ini) open initramfs then ask for cryptrootunlock pass then close the ssh connection and ... nothing.
  4. I set verbosity to 7 and view that : There is some problem with the network but i don't understand what. Someone have any idea about that ?
  5. Hi !as title say i can not fully boot after reboot for electric failure. I have the boot partition on my sdcard then normaly boot on the encrypted ssd system debian buster with 5,4 system.(Linux gre 5.4.102-odroidxu4 #21.02.3 SMP PREEMPT Mon Mar 8 07:55:51 UTC 2021 armv7l GNU/Linux) I can access to initramfs run cryptroot-unlock script ,unlock the encrypted drive, then initramfs disconnect me and ... nothing, i can not view my HC1 on the network So I tried to boot on the sdcard system and could unlock the SSD and chroot on the ssd. i see logs but nothing helps me to resol
  6. It seems that the mmcblk number change from 0 to 1 so my boot folder didn't mount, so automatic "sudo update-initramfs -u" doesn't work. i started from scratch and replace sudo sed -e '2i/dev/mmcblk0p1 /media/sdcard ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 2\' -i /mnt/etc/fstab by sudo sed -e '2i/dev/mmcblk1p1 ... What should be the origin of this change ?
  7. I tried from a fresh image flashed on sdcard and just sudo mkfs.ext4 /dev/sda -E discard sudo mount /dev/sda /mnt sudo rsync -ahPHAXx --delete --exclude={/boot/*,/dev/*,/proc/*,/sys/*,/tmp/*,/run/*,/mnt/*,/media/*,/lost+found} / /mnt sudo sed -e 's/UUID=[^ ]*/UUID=MY_SDA_SSD_SPECIFIC_UUID"/' -i /boot/boot.ini That does not change the problem
  8. just what i do after flashing armbian on my sd. # $erver mkdir /etc/dropbear-initramfs/ apt install armbian-config vim rsync lvm2 cryptsetup dropbear-initramfs busybox nmap thin-provisioning-tools lxc nftables ebtables libxml2-utils iproute2 bridge-utils uidmap unattended-upgrades zram-tools # €lient cat .ssh/id_*.pub # $erver vi /etc/dropbear-initramfs/authorized_keys #change ssh ports sed -e "s/#Port 22/Port 2222/g" -i /etc/ssh/sshd_config sed -e "s/^#CRYPTSETUP=/CRYPTSETUP=y/" -i /etc/cryptsetup-initramfs/conf-hook sed -e "s/^#DROPBEAR_OPTIONS=/DROPBEAR_OPTIONS=\"-p 22222\"
  9. i don't know if it's related but i answer an other post here with a similar problem : " no network access ". resume : my HC1 boot well on unencrypted sdcard but when i try to boot on my full root encrypted ssd, it fail after successfully run cryptroot_unlock from initramfs . Do you have any clue ?
  10. I'm in the same trouble. It boot well on my SDcard then i do a rsync of the root to the encrypted ssd change the boot.ini to boot to the ssd as everytime i did. ~ # sudo sed -e 's/root=[^ ]*/root=\/dev\/sdg\/root cryptopts=source=\/dev\/sda,target=sdc,lvm=sdg /' -i /boot/boot.ini ~ # sudo update-initramfs -u then it boot first on the initramfs well and i have access to the busybox ssh. then I execute cryptroot_unlock it seems to start initializing well but without network, so i can't access. I have access to the ssd from the initramfs using /sbin/cryptsetup