Search results

Hi, Have you tried to mount the CIFS shares manually using `umount -f /mnt/pve/SwFileServer-cifs` command? If not please can you try? after you unmount the CIFS, try to remove the storage, and re-add it from your PVE Web UI.

Thank you for the output! Can you please also provide us with the output of `pveversion -v`?

Hi, Have you tried to disable the UEFI Boot, since older servers like HP Proliant DL360 may not support UEFI properly! The other solution can be is to install Proxmox VE on top of Debian as described in our wiki guide [0]. [0] https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm

Thank you for the logs! The losing quorum can trigger the HA manager to initiate a node reboot, which is what seems to be happening, since HA requires stable network communication to ensure that resources are available. If you have only one ring_x in your corosync config, please consider...

Hi, Thank you for the outputs! in the server01 there is no `proxvg`: root@server01:~# pvesm status no such logical volume proxvg/proxthin Name Type Status Total Used Available % ThinDisk lvmthin active 9731174400 0...

Hi, Have you run the `ifreload -a` command? If yes, is there an output?

Can you also post the output of the following command? last reboot -n 10

Can you share what happened in the syslog when a node rebooted? This might help us identify what triggered the reboots. Have you enabled the HA on those nodes?

The config you shared look to be fairly standard. However, can you try to add disable automatic reboot after the upgrade [0]? Unattended-Upgrade::Automatic-Reboot "false"; EDIT: If the server shut down again please provide us with more entries of syslog. [0]...

Hi, Thank you for the syslog! Can you please share the unattended-upgrades configuration as well?

Hi, Can you please tell us how you added the directory to your Server and the output of the `pvesm status` command?

Hi, Thank you for sharing more syslog! Have you tried to restart pveproxy service? `systemctl restart pveproxy` Have you tried to log in from a different/private browser as well? If the private login works you may have to clean the cache. If not, try to update the certificate using `pvecm...

Hi, Can you please post your LXC config pct config <CTID>?

Hi, Can you check if the IOMMU is enabled in BIOS and that Proxmox VE boot option include `intel_iommu=on` or `amd_iommu=on`?

Hi, Can you please provide more syslog entries?

Can you please check the storage status and the output of the following commands: pvesm status --storage <CIFS storage> top free -h For more information can you please check the syslog using journalctl since you re-enabled the CIFS share? You can generate the syslog as the following command...

Hi, If your current PCI passthrough setup via CLI is working fine, there's no strict need to change it.

Make sure that you restart the pvestatd on the two remaining nodes.

You can move/remove the `/var/run/pvestatd.pid.lock` and then restart the pvestatd service using systemctl restart pvestatd command.

Hi, Can you please try to manual mount your CIIFS on a test VM or LXC or even your Proxmox VE using `mount`, to narrow down if the issure related to the CIFS connection or not. Did you check the syslog for anything related to?