[SOLVED] stuck after unlocking luks device

waltar said:
Don't think it's a network card or driver for problem. You should set ip and pve-name in /etc/hosts to not request dhcp (in debian before "upgrading" to pve as then it seems too late) !! And comment 127.0.1.1 hostname to be not valid also !!
Click to expand...
I tried your suggestions but no other result :(

I'm grateful for any other idea/suggestion :)
 
I just checked it again to be sure, but yes, still the same message

But just for my understanding: I changed /etc/hosts and got later still an ip address from my router. Is this normal?

My question gave me an idea. I disconnected the server from the router and it booted. I still got some messages like before but i reached the login prompt. But ip a gives me no ip address
 
Last edited:
For a fresh debian to pve inst it should look like somethink this - change to your interface (eno1 here) and your network static IP :
cat /etc/network/interfaces
# Don't activate subfolder for pve !
#source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.5.5/24
gateway 192.168.5.254
bridge-ports eno1
bridge-stp off
bridge-fd 0
 
Thank you all very much for your help.
I got it fixed.
The solution was to remove the network cable during boot. I still get the message but it works so far.
 
Pechvogel said:
Thank you all very much for your help.
I got it fixed.
The solution was to remove the network cable during boot. I still get the message but it works so far.
Click to expand...
After some tinkering I found out: The problem were the multiple nics and the /etc/network/interfaces which Debian generated. After I deleted all the nics (without eno1) in the file, proxmox rebuilt them and since then it is working fine without any problems.
 
  • Like
Reactions: waltar
You must log in or register to reply here.
Top Bottom