Recent content by SunBlack

As noted: The BCM57416 works fine with Kernel 6.14. Since Proxmox 9.0, this has been the default kernel, so no configuration adjustments are currently anymore necessary (although it would still be useful to have an option to switch to a newer kernel in the installer if Proxmox is already...

Ok, reinstalled the system to collect logs with fixed IP (so setting same IP the DHCP server would set): - Directly after install: <tool>after_install.log - Directly after "service networking restart" (without restart): <tool>after_install.log - Restart: <tool>after_restart.log - After "apt...

Yes, but was not successful: apt install unzip wget https://www.thomas-krenn.com/redx/tools/mb_download.php/ct.YuuHGw/mid.y9b3b4ba2bf7ab3b8/bnxtnvm.zip unzip bnxtnvm.zip chmod +x bnxtnvm for i in $(./bnxtnvm listdev | grep 'Device Interface Name' | awk '{print $5}') do ./bnxtnvm -dev=$i...

It is a Supermicro H13SSL-NT motherboard, so the network card is a Broadcom BCM57416 10GBase-T. Edit: Related older thread.

I had the issue even after several restarts. Even after starting the network manually, running "apt update && apt dist-uppgrade" so I'm on 8.4.1 instead of just 8.4 (including reboot). // Edit: If you need some logs to help you decide whether to put a newer kernel in the offline package, let me...

I had to restart the installation of Proxmox yesterday, because our network has no fixed IPs, but only via DHCP (which is not optimal, but not the topic here). I therefore restarted to the pre-installed Windows to find out the IP that the DHCP sever has assigned to the Mac address. However...

We got a new server yesterday. Instead of the usual 10 minutes to install Proxmox, it took me a few hours because the network card was recognized, but after every restart I had to reactivate the connection manually. It was only the message on reboot that made me think that it could be a driver...

ok, maybe you could avoid the warning when you are using adduser --system --no-create-home tss internally

Thanks for the fast fix. There is still an issue: Warning: The home dir /var/lib/tpm you specified can't be accessed: No such file or directory Adding system user `tss' (UID 111) ... Adding new user `tss' (UID 111) with group `tss' ... Not creating home directory `/var/lib/tpm'.

The required packages are already published in the community repo, but there seems to be a issue in it: You need to call upgrade twice as the first call is failing, see below (care: there are two calls to upgrade within it): account@host:~$ sudo apt-get update && sudo apt-get -V dist-upgrade...

Hi all, I want to create a backup of our a VM on a existing Thinpool. As it is only a temporary backup before an upgrade of the VM (and we have an external backup job as well) it is okay when the backup is on the same machine as the VM itself (as I don't know where Proxmox is storing snapshots...

What is is the opposite of this? So I can add a `post-down` event?

Thanks, this works :)

Hi all, I had to setup a fresh installation of Proxmox. As we don't have enough IPv4 adresses, we had used a NAT on our old installation. But this works now only partially. I can connect from outide to my VM via port 20222, but the VM can't reach any internet adress (e.g. for updating the...

Well thank you. Before I could store remaining VMs with DD the RAID destroyed itself completely be losing partition data. Nevertheless thank you :-)