Search results

... thanks for the help. it worked!

Hi, yes, sorry: /dev/sda2 and /dev/sdb2 (tired from one hell of a week...)

BTW: Just did the init on /dev/sdb2 and /dev/sda1 # cat /etc/kernel/proxmox-boot-uuids 6DF4-519B 6E2E-4A8C Looks strange? Tobias

Hi, Ok. So the steps would be: - Remote the lines from /etc/kernel/proxmox-boot-uuids (no, that was not copied... probably got mangled during an update?) What do you mean with "add existing ESP Partitions" using proxmox-boot-tool? Do you mean: proxmox-boot-tool format /dev/sda2...

Hi... # cat /etc/kernel/proxmox-boot-uuids 2025-74B9 2025-D0CE and # lsblk -o NAME,FSTYPE,SIZE,UUID NAME FSTYPE SIZE UUID sda 223.6G |-sda1 1007K |-sda2 vfat 512M 6DF4-519B `-sda3 zfs_member 223.1G 11576862949081681133 sdb 223.6G |-sdb1...

No errors, unfortunately. # proxmox-boot-tool kernel list Manually selected kernels: None. Automatically selected kernels: 5.11.22-3-pve 5.15.39-1-pve It just NEVER boots the 5.15.39-1-pve and it's not displayed in GRUB W: This system is booted via proxmox-boot-tool: W: Executing...

All, I have one system that does not want to boot any other kernel than 5.11.22-3-pve I have installed those two: ii pve-kernel-5.11.22-3-pve 5.11.22-7 amd64 The Proxmox PVE Kernel Image ii pve-kernel-5.15.39-1-pve 5.15.39-1...

Hi Mira, I have this error on one installation, too. I think it could be Proxmox 6 (to be upgraded in the next days) in combination with pbs2.2. I have no other installation where this error occurs (and my setup at our datacenter is very similar to the one at the customer side - except: The...

Hi, In our case it wasn't the developers - it was me wondering why some servers got unresponsive... after some trials I found out it had to do with the ZFS... If you search the forum there are older posts about this... Tobias

Hi, We have had similar issues when using local disks, unfortunately... We have since moved all data to NFS Shares. Tobias

All, I found the solution (at least: it seems to work again) log into each node in the cluster and issue: cd /etc/pve/local ; rm pve*ssl.* ; pvecm updatecerts --force ; service pveproxy restart Tobias

All, When trying to upload new certs to my pve cluster... the first node went pretty well. The others didn't. Secure Connection Failed An error occurred during a connection to burfell.scnr.ch:8006. PR_END_OF_FILE_ERROR pvecm updatecerts -f && service pveproxy restart didn't help. Any idea...

Hi, Gerat... but one question regarding the scheduler: Why don't you just allow the entry of crontab-style values directly? At least, when I tried, it didn't work. Thanks Tobias

Hi, Yes, I did try this - no change in behaviour. As I wrote above: If I let one interface in vlan1, vlan10 or any other vlan (without having any sort of traffic from that interface) it works. I haven't tried this but will just create the interface without an IP.... and see what happens. BTW...

No, the VM having the Issue is a KVM VM. But I noticed some strange behaviour with LXC systems and migrated them. Tobias

Hi From the netapp side -> difficult (i.e. not supported). From the VM side -> no information at all.... it just gets slower and slower until it locks up. I have checked the switches again - and all VLANs are set up identically... Spanning-Tree seems to be OK. I am going to check again...

Hi, Yes... thanks a lot. Out of an unknown reason LUN0 & LUN1 got exchanged (i.e. lun0 was mounted on lun1-mountpath and vice verca). fun enough it did somehow work for some backups - which is why I was puzzled. Got it sorted (and forgot to tell here) Tobias

All, I rebooted the PBS Server and now get this message: INFO: starting new backup job: vzdump 90001 --mode snapshot --storage zz_pbslun1 --remove 0 --node pve01c01-am64c INFO: Starting Backup of VM 90001 (qemu) INFO: Backup started at 2021-09-19 18:12:55 INFO: status = running INFO: VM Name...

Checked that, not the case. and btw... the added interface in vlan10 does not do anything - nfs server inside vlan1001 is used... As I said: it's weird.

only from the VM to the NFS Share.... and unfortunately no logs. tcpdump doesn't show anything bad either - it just seems like the traffic is stopping / getting delayed.