Recent content by dafydd

  1. D

    [SOLVED] Quorum failure and recovery

    Using the built-in backup scheduler to back up all containers to a node in the cluster which runs an NFS server. There was no backup process in the log for 27 October. I did get a brief ping monitoring outage for one node, which would have been the first node in the backup list.
  2. D

    [SOLVED] Quorum failure and recovery

    For anyone reading this in future, this issue coincided exactly with the backup job starting at 4am (and then running again the next day which recovered quorum). The backup failed on the 27th but worked the following night. Never seen that before in 15 years of running Proxmox,
  3. D

    [SOLVED] Quorum failure and recovery

    Hmm it recovered by itself just about 24 hours later. I don't know if that was due to processes restarting or whether it was a networking issue. The local VLAN was working the whole time because the nodes could all see the NFS storage on another node. I was planning on asking the hosting...
  4. D

    [SOLVED] Quorum failure and recovery

    All nodes left the cluster in the early morning Oct 27 03:53:51 corosync[1602]: [QUORUM] Sync members[1]: 2 Oct 27 03:53:51 corosync[1602]: [QUORUM] Sync left[3]: 1 3 4 Oct 27 03:53:51 corosync[1602]: [TOTEM ] A new membership (2.ba4) was formed. Members left: 1 3 4 Oct 27 03:53:51...
  5. D

    [SOLVED] Quorum failure and recovery

    I should add - I've spotted that corosync is consuming 100% on all servers (possibly because of losing quorum?).
  6. D

    [SOLVED] Quorum failure and recovery

    These are the errors showing on the 3 other nodes pvescheduler[1505772]: jobs: cfs-lock 'file-jobs_cfg' error: no quorum! pvescheduler[1505771]: replication: cfs-lock 'file-replication_cfg' error: no quorum! On the node I updated, just lots of this corosync[2837]: [KNET ] loopback: send...
  7. D

    [SOLVED] Quorum failure and recovery

    I have a 4 node cluster running Proxmox 9. I just updated one node with the latest packages and kernel. I spotted something odd and realised that the cluster had no quorum. I don't know if that was due to the upgrade or whether it happed previously (I suspect it did). I rebooted the first node...
  8. D

    [SOLVED] Debian 9 lxc shutdown issue

    No difference. I had initially created the fresh container with nesting enabled (by mistake as it doesn't really need it). But the old containers work without nesting.
  9. D

    [SOLVED] Debian 9 lxc shutdown issue

    Don't think it's the config. It matches the old container details. arch: amd64 cores: 2 hostname: test memory: 2048 net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.0.1,hwaddr=XX:XX:XX:XX:XX:XX,ip=192.168.0.29/24,type=veth onboot: 1 ostype: debian rootfs: vmdata:vm-114-disk-0,size=21G swap...
  10. D

    [SOLVED] Debian 9 lxc shutdown issue

    A VM may be an option. What I've done now is take a backup and restore of the original working container to a new one. This works fine even on a different physical server. The one difference I can spot is that the fresh install is running systemd-networkd and systemd-resolved which the old one...
  11. D

    [SOLVED] Debian 9 lxc shutdown issue

    Hi, I am running the latest Proxmox v9 with a container running Debian 9 (yes it's very old, running an application which is currently being upgraded). It was originally created more than 6 years ago and is running fine. I've now created a new container with the same original Debian 9 template...
  12. D

    [SOLVED] Dell R340 - not booting on kernels 6.8+

    Ok so the answer as seen in a few places is Amend /etc/default/grub amend this to turn off iommu GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=off"
  13. D

    [SOLVED] Dell R340 - not booting on kernels 6.8+

    Thanks. the RAID controller is: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] [1000:005f] (rev 02) Subsystem: Dell PERC H330 Adapter grub.cfg looks ok and has the corrrect VG/LV. The megaraid driver is in the initramfs as I would expect I've now found this thread, which implies a bug with the...
  14. D

    [SOLVED] Dell R340 - not booting on kernels 6.8+

    I have a Dell R340 running Proxmox VE 8. It is fully up-to-date but is running kernel 6.5.13. A couple of years ago there was an update to kernel 6.8 but it didn't boot up, so I reverted. I'm now trying to see if I get it running on 6.8 or 6.14 in preparation for upgrading to Proxmox 9. I have...
  15. D

    Boot Failure on upgrade to VE 7.2 with kernel 5.15.35-1-pve

    I've seen the same issue on a Dell R340 - it was failing to find or load megaraid_sas. So it failed to boot further and went into busybox (unfortunately I didn't get a screenshot of the errors before rebooting).