[SOLVED] stuck after unlocking luks device

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 !!
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.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!