Search results

  1. S

    [SOLVED] Corosync.conf is read-only after adding Qdevice

    Sorry. Immediately after I posted this I realized I needed to stop the cluster on the failed nodes to gain access. systemctl stop pve-cluster systemctl stop corosync pmxcfs -l Then I could edit the corosync.conf and move it to an exact copy of the original. All is good again.
  2. S

    [SOLVED] Corosync.conf is read-only after adding Qdevice

    I decided to add a qdevice to my cluster. Turns out that was a mistake. After adding, I started by rebooting a node and it fails to join the cluster again. I figured i could just revert back to a backup corosync file, however it looks like i can no longer modify them at all. I tried stopping...
  3. S

    [SOLVED] Yet Another IOMMU Not Detected Thread

    Thanks for the fast response ! Ironically I swapped the hard drive 5 minutes ago, reinstalled the OS and made the changes for GRUB. Now it is working. Appreciate the response. Sorry I kind of wasted some time over a hardware issue.
  4. S

    [SOLVED] Yet Another IOMMU Not Detected Thread

    Thanks for sharing. I have a Lenovo X 3550 M5 that I cannot get IMMU to work. I see similar results as the above, however when I follow the grub or the systemd-boot process, I brick proxmox. Basically it cannot boot up after a reboot. Messages like this: ""pve" not found" Anyone have any...


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!