Recent content by breakaway9000

Ok its fixed. I think there are a few things at play here. First, I think the system ran out of space because the boot volume is quite small, and then this caused the ifreload package to glitch. In typical fashion there were kernels going back to 6.4 on this system taking up many gigs of space...

I have a 3 node cluster. I updated the first one & rebooted, went smoothly. Then I went to update and reboot the second, but it wouldn't boot up: VFS: Unable to mount root fs on unknown-block(0,0) I rebooted and went into advanced options, and tried to load the kernel that was previously...

Something has changed, these steps no longer work. I was running into some issues on a Win 2022 VM. In summary, all that was needed was Take your migrated VM and boot it using IDE Uninstall VMWare Tools; Install qemu-guest-agent, shut down VM Add a new disk (1GiB in size is enough) as virtio0...

I've got a bunch of drives in my system (note last 6) NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 3.5T 0 disk ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 1G 0 part /boot/efi └─sda3 8:3 0 3.5T 0 part...

@zimm , can you share your vm config file & driver install within the VM itself? I am running into a lot of issues getting the same setup (7950x3d) to work. I am sure I am missing something simple! The system sees the GPU, but /dev/dri does not appear, I have installed these packages that the...

I just hit this issue on both my pve host (9.1.4, up to date as of writing) and also my proxmox backup host (also up to date at 4.1.1). I use CloudFlare DNS-01. This worked for over a year but randomly broke today. The error reported in the WebGUI was: Proxmox Host: Loading ACME account...

I used to have 2 node cluster. I setup a 3rd node using a qDevice (Just a VM running on one of my servers) to be a tiebreaker. But now I have a 3rd node to add. However, adding it has not been easy. First, I went to remove the qDevice with pvecm qdevice remove which succeeded. Then, I went to...

I'm experiencing this issue right now. I was told there were no snapshots but there in fact were. The Disk names had that weird 000001.vmdk suffix. Right Click -> Snapshots -> Consolidate solved it for me. Looks like VMWare had lost track of the snapshots. Good riddance to this awful and now...

I recently migrated some of my infrastructure to Proxmox and now run my first 2-node cluster using a qdevice for quorum. Each node is connected to a Synology NAS over NFS. The setup works smoothly overall, except for backups. With qcow2 disks on NFS, the CBT (changed block tracking/disk...

Hi everyone I just set this up a few days ago. Setup went very smoothly (no errors). But when testing, seem to be running into an issue when I reboot one of my two nodes. It says something like "No quorum on node1" in Datacenter -> HA (where node1 is the remaining online node). From what I...

Probably going to get smacked with a stick for posting this, but I browsed to my proxmox backup server repository (which is a CIFS share on my synology). I drilled down into `vm` folder, then found a file in there called `owner`. I edited this with the name that my PBS is expecting (per the...

Output is `0` on both vmbr0 and vmbr1 from the system that doesn't have VLAN aware ticked but is passing vlans.

And, output of ethtool -k vmbr0 from a system that doesn't have "VLAN Aware" ticked but does pass VLANs through. Features for vmbr0: rx-checksumming: off [fixed] tx-checksumming: on tx-checksum-ipv4: off [fixed] tx-checksum-ip-generic: on tx-checksum-ipv6: off [fixed]...

Ok, here's ethtool from a system that is working properly with the "VLAN Aware" box ticked: I will get output from a system without the box ticked soon. The system has a realtek nic (output of lspci -v with respect to the NIC below) root@proxmox02:~# ethtool -k enp1s0 Features for enp1s0...

Hmm, I saw inconsistent behaviour on two NICs (both are Intel Corporation Ethernet Controller I225-LM) attached to two different vmbr on the same system. Neither vmbr had "VLAN Aware" ticked, but one was passing VLANs, the other was not. Output of lspci -v is below 58:00.0 Ethernet controller...