ip a (continued)
70: tap1103i3: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq master vlan0073 state UNKNOWN group default qlen 1000
link/ether 8a:fb:d5:86:91:d3 brd ff:ff:ff:ff:ff:ff
71: tap1105i3...
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever...
PBS does really, really do random writes. It needs IOPS - as many as it can get.
For ZFS there is the rising problem of fragmentation of the free space --> it is not guaranteed that a single 2-4 MB chunk can be written sequentially at one...
could you double check and post your network configuration/setup, including the switch config? in particular of the two "problematic" nodes? this looks like a network misconfiguration problem, though the logs don't give a clear indication *what*...
ip r
default via 192.168.127.254 dev vmbr0 proto kernel onlink
192.168.125.0/24 dev en05 proto kernel scope link src 192.168.125.11
192.168.125.0/24 dev en06 proto kernel scope link src 192.168.125.11
192.168.125.12 nhid 272 via...
OK so I've just upgraded the remaining 2 nodes and both ran into the same issue, however this time I caught it in the last few lines of output
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new...
Please post the output of
cat /etc/pve/sdn/fabrics.cfg
ip a
ip r
vtysh -c 'show openfabric interface'
vtysh -c 'show openfabric neighbor'
vtysh -c 'show openfabric summary'
on one node
We are excited to announce the release of Proxmox Virtual Environment 9.2. This release focuses heavily on platform refinement, stability, and core optimization.
Proxmox VE 9.2 is built on the robust Debian 13.5 "Trixie" and ships with Linux...
There are many, many posts written about a good setup. My personal key-points (in a very small nutshell) are these:
PBS must be self-contained, on separate hardware; especially when you have only one PVE (no cluster) you want to have access to...
There are many, many posts written about a good setup. My personal key-points (in a very small nutshell) are these:
PBS must be self-contained, on separate hardware; especially when you have only one PVE (no cluster) you want to have access to...
you are using proxmox-boot-tool with grub, so you don't need systemd-boot and should remove it. you can then do the upgrade, and afterwards, install systemd-boot-efi and systemd-boot-tools (this is just so you can easily switch later on if you...
Hi,
My setup is as follows:
Cluster of 3 x Minisforum MS-01, connected via a SDN Fabric over Thunderbolt.
This setup has worked without problems for several month.
Last week I updated from 9.1.9 to 9.1.14, after which SDN prompted me to...
like I wrote above (https://forum.proxmox.com/threads/pve-8-to-9-in-place-upgrade.170013/page-2#post-799095)
- remove systemd-boot before the upgrade
- ensure systemd-boot-efi and systemd-boot-tools are installed after the upgrade
Hi!
The upgrade guide then also states "Then you can remove the old /etc/apt/sources.list.d/pve-enterprise.list file", once you confirmed that apt policy shows that the new repositories have been picked up as expected. I think you might have...
Great!
My own one was decommissioned last year. Finally, after (nearly) 15 years. Basically because I have much better gear for PVE now... and PBS is really hard to make it fly on such an old thing.
Have fun!
How to check if systemd-boot is being used — and how to safely remove it
Step 1: Check which bootloader is in use
(if it is grub for example it is saffe to remove systemd-boot)
Run the following command to inspect your current EFI boot...