Recent comments on posts in the blog:
It's strange how I reached from - https://github.com/BeWelcome/rox/issues/174 to this page!
Ironically, I left my 9 to 5 job 3 months back, and currently working as a full time freelancer!
Cheers, Yash
It works with Debian Buster but, you need to
mount --bind /run /target/run
Otherwise, apt install lvm2 grub will hang forever.
This is often terribly useful for a freshman. I simply bookmarked this post for future reference. Keep sharing this sort of post. Thanks for sharing. Good read. Thanks for the info. It helps us.
Hi everyone !
Martin, thanks for the big instructions ! (5 life-days saved)
kuschelmaus, thanks for debian 9 network things (2 life-days saved)
FlorianRingbeck, to solve /etc/network/interfaces issue you need to use enp1s0 as follow:
auto enp1s0 iface enp1s0 inet static address [IP]/24 gateway [GW] pre-up /sbin/ip addr flush dev enp1s0 || trueCarefull, in your example, you are using a private IP address.
In grub (IP static) configuration use Netmask and not Slash (as I do during 2h)
NO: GRUB_CMDLINE_LINUX="ip=MY_IP_ADDR::MY_DEFAULT_GW:24::eth0:none" YES: GRUB_CMDLINE_LINUX="ip=MY_IP_ADDR::MY_DEFAULT_GW:255.255.255.0::eth0:none"
That's all folks !
Thank's for the excellent guide. I rented a dedicated server from Kimsufi and tried to setup my machine to boot from the encrypted harddrive.
The unlock via dropbear does work but unfortunately the server does not respond on the network interface afterwards. I assume that there is an error in the network config but I was not able to find it until now. This is the logfile of the boot process (i replaced my real ip with 192.168.0.1): May 16 21:08:24 xxxx kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/vg0-root ro net.ifnames=0 ip=192.168.0.1::37.187.0.254:255.255.255.0::eth0:none May 16 21:08:24 xxxx kernel: e1000e 0000:01:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:21:4f:b3:21:74 May 16 21:08:24 xxxx kernel: e1000e 0000:01:00.0 eth0: Intel(R) PRO/1000 Network Connection May 16 21:08:24 xxxx kernel: e1000e 0000:01:00.0 eth0: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF May 16 21:08:24 xxxx kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready May 16 21:08:24 xxxx kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None May 16 21:08:24 xxxx kernel: e1000e 0000:01:00.0 eth0: 10/100 speed: disabling TSO May 16 21:08:24 xxxx kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready May 16 21:08:24 xxxx kernel: e1000e: eth0 NIC Link is Down
This is my network config: root@rescue:/# cat /etc/network/interfaces
interfaces(5) file used by ifup(8) and ifdown(8)
Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
auto lo iface lo inet loopback
auto eth0 iface eth0 inet static address 192.168.0.1/24 gateway 37.187.0.254 pre-up /sbin/ip addr flush dev eth0 || true
Any ideas what to look at? Thank's in advance.
tincho, yes, the mount command is there, but this one:
chroot /target mount -a
did not mount the boot partition and there were no errors either so I had no idea that it was not mounted 
By the way, thanks for the guide!
Vanix,
Then you missed one step. The mount command is in the guide!
After reading the comments and the tip from kuschelmaus I've made needed changes to /etc/defaults/grub file. And it didn't work, I tried every possible solution out there. But the problem was that I had to manually mount boot partition
mount /dev/sda1 /target/boot
Otherwise, update-grub2 didn't have any effect and I was getting stuck with error message that eth0 unknown device. I had to simulate installation on my local VirtualBox machine because there is no console access available at Kimsufi.