linda

I cannot boot into lvm encyprypted root partition: mount: mounting "/dev/mapper/vg-root on /root failed: No such file or directory␍␊ Failed to mount "/dev/mapper/vg-root as root file system.␍␊ The flollowing step i made (short version) - create the lvm partition - mount lvm partition and and copy file system auf lvm partition, bind /dev, sys, proc - chroot in the lvm root partition (vg-root) - change /etc/fstab : insert /dev/mapper/vg-root / ext4 errors=remount-ro 0 1 UUID=<UUID-Partiion> /mnt/mnt ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 2 #UUID=<UUID-Partiion> / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 - create the initramfs: update-initramfs -u -k $(uname -r) - change armbian.txt: rootdev="/dev/mapper/vg-root cryptdevice=/dev/mmcblk0p2:lvm" During boot, the device ask the PW: Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Please unlock disk lvm: ␍␊ After inserting the password, lvm seems alright ("cryptsetup: lvm: set up successfully␍␊done.␍␊") But the boot file system is not fount Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems␍␊ done.␍␊ Begin: Will now check root file system ... fsck from util-linux 2.33.1␍␊ Checking all file systems.␍␊ done.␍␊ mount: mounting "/dev/mapper/vg-root on /root failed: No such file or directory␍␊ Failed to mount "/dev/mapper/vg-root as root file system.␍␊ i am very grateful for any comments and tips. I have already done such LVM boot encryption 2 years ago on Pine 64 and Pine LTS. BUT NOW I HAVE NO IDEA HOW TO LOOK FURTHER.

I managed to reconnect via DHCP again with the following steps: Insert these lines in /etc/network/interfaces auto eth0 iface eth0 inet dhcp pre-up ifconfig $IFACE up pre-up ethtool -s $IFACE speed 100 duplex full autoneg off and change the line in /etc/NetworkManager/NetworkManager.conf to [ifupdown] managed=false

I'm using a Pine 64 LTS. For this I have downloaded the SoPine images Armbian_21.08.1_Pine64so_buster_current_5.10.60.img and Armbian_21.08.1_Pine64so_focal_current_5.10.60.img Both images boot normally (including network connection), but after the update (apt update, apt upgrade) no IP4 network connection is established for eth0. For help I am very grateful for any help.

I am using an old Sopine image (Armbian 21.02.3 Bionic with Linux 5.4.88-sunxi64). It works very well with the Pine LTS hardware. However, there is a new Pine LTS hardware (LTS-V2) that seems to have changed the network chip, so with the old Sopine image it is no longer possible to connect to the network. Is there any way to reinstall the current network drivers in my image? How can I use the kernel configs to do this? Thanks a lot in advance

Hello, I'm using a Pine 64 LTS with the SoPine image Armbian 21.02.3 Bionic with Linux 5.4.88-sunxi64 I have made various changes and installations to this image, so I want/need to continue using this image. Unfortunately, with the new hardware of the Pine 64 LTS (Pine64 LTS-V2) network connection is no longer possible. (Note: With the current SoPine image there is a network connection). Is there any way to reinstall the current network drivers in my image? I would be very grateful for any help.