Recent content by TomNick

This is it. Thank you

Hello everybody, I did an upgrade 8 to 9 and everything worked out without any errors. After an reboot it suddenly goes to bios, Secure boot is disabled, I did verify the boot order and it is in UEFI mode. Then I started Proxmox from an USB stick in rescue mode (9.2.1) and boom I was in the...

Hi everybody, I was experimenting and learning with 4 server in a cluster. It worked fine so far until I somehow messed up one server and that one is now not in the cluster anymore. The server who is not in that cluster was used for shared and backup data. Since I installed all my VMS using the...

Did the restart, nothing changed, syslog enclosed

root@pbs:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 32G 0 disk ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 512M 0 part └─sda3 8:3 0 31.5G 0 part ├─pbs-swap 252:0 0 3.9G 0 lvm [SWAP] └─pbs-root 252:1 0...

Hello everybody, after an upgrade to 3.2-7 I am not able to show my storage disk and I am not able to backup anymore: This is my log: 2024-10-18T06:00:00+02:00: Starting datastore sync job 'instabackup:dateninsta:remote::s-730fc624-fc85' 2024-10-18T06:00:00+02:00: task triggered by...

Hi everybody,, I am trying to backup my VMS on Hetzner Storage for a brand new system and getting the following error: INFO: starting new backup job: vzdump 103 --mode snapshot --compress zstd --node Debian-109-buster-64-minimal --storage hetznerbackup --remove 0 INFO: Starting Backup of VM...

Name: T Config Version: 5 Transport: knet Secure auth: on Quorum information ------------------ Date: Thu Nov 30 14:12:51 2023 Quorum provider: corosync_votequorum Nodes: 2 Node ID: 0x00000001 Ring ID: 1.341 Quorate...

Meaning to complete delete node 3 and then adding it again to the cluster of 1 and 2?

Yes they are up and running but the VMS and CTS are "dead" since the root data are located on node 3

Hello everybody, I am running 3 instances in a cluster. Every VM or CT on instance 1 and 2 are running their root disk on a shared drive on instance 3. Now instance 3 is messed up and I would like to move all the shared root disks to the local disk on instance 1 and 2. So I did copy all the...

Well, that was easy....disk was broken....thanks for help

root@pve3:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content backup,images,vztmpl,iso shared 0 lvmthin: local-lvm thinpool data vgname pve content images,rootdir nodes pve1,pve3,pve4,pve2 lvm: local-lvm3 vgname...

Hi everybody, I am running 3 pve in a cluster. Pve3 needed a restart and after it, I am not able to start any VM anymore. Getting the following error: Command failed with status code 5. command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5 Volume group "local-lvm3" not...

This is it, thanks a lot for your help. Running like a charm