[SOLVED] Debian 11 to Proxmox 7 Problems

[Alfio]

Hi, I'm trying to install Proxmox 7 in Debian 11 and I'm having some problems at the installations when the installation try with ifupdown2 the network goes down and i lost all connectivity to the server, I tried with deafferents providers and also in home lab, the results are the same:

Get:531 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 zfsutils-linux amd64 2.0.5-pve1 [471 kB]
Get:532 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 zfs-zed amd64 2.0.5-pve1 [67.5 kB]
Fetched 494 MB in 20s (24.3 MB/s)
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 22951 files and directories currently installed.)
Removing firmware-linux-free (20200122-1) ...
dpkg: warning: while removing firmware-linux-free, directory '/lib/firmware' not empty so not removed
Removing ifupdown (0.8.36) ...

Progress: [ 0%] [.....................


After that the network service doesn't work, I cant even restart the network services because is masked.

Any suggestion where i can see something about it, Thanks in advanced.

 

[oguz]

hi,

do you see the network interface when you run ip a?

how does the /etc/network/interfaces file look?

also have you checked [0]

currently i'd suggest to install on top of debian buster (10) and then upgrade to bullseye after the PVE installation, or just directly install using our latest ISO (based on bullseye)

[0]: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster

 

[vesalius]

Hi, I'm trying to install Proxmox 7 in Debian 11 and I'm having some problems at the installations when the installation try with ifupdown2 the network goes down and i lost all connectivity to the server, I tried with deafferents providers and also in home lab, the results are the same:

Get:531 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 zfsutils-linux amd64 2.0.5-pve1 [471 kB]
Get:532 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 zfs-zed amd64 2.0.5-pve1 [67.5 kB]
Fetched 494 MB in 20s (24.3 MB/s)
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 22951 files and directories currently installed.)
Removing firmware-linux-free (20200122-1) ...
dpkg: warning: while removing firmware-linux-free, directory '/lib/firmware' not empty so not removed
Removing ifupdown (0.8.36) ...

Progress: [ 0%] [.....................


After that the network service doesn't work, I cant even restart the network services because is masked.

Any suggestion where i can see something about it, Thanks in advanced.

have you tried installing ifupdown2 on debian 11 and confirming networking works after reboot prior to installing pve? I think that is what I ultimately did for 2 identical recent installs on devices without video out and only console access, which the Proxmox installer, as far I could tell, can not handle. You may need to run systemctl enable networking from debian console after the ifupdown2 is installed if networking does not come up on initial reboot.

 

[Alfio]

Solved. Hi again, I was doing some test and the solution was to mark ifupdown2 before begin with the PVE install with apt-mark hold ifupdown2, after that everything was fine. after the installation I installed ifupdown2 and everything was right. Solved

Note for Debian 11 to Proxmox 7 Problems for late post:

When I tried to start the networking service it said network is masked when I tried to unmask the network services is complain about missing parameters in lvm.conf.

 

[oguz]

Solved. Hi again, I was doing some test and the solution was to mark ifupdown2 before begin with the PVE install with apt-mark hold ifupdown2, after that everything was fine. after the installation I installed ifupdown2 and everything was right. Solved

Note for Debian 11 to Proxmox 7 Problems for late post:

When I tried to start the networking service it said network is masked when I tried to unmask the network services is complain about missing parameters in lvm.conf.

great, thank you for sharing the solution if you mark the thread as [SOLVED] others will also know what to expect