Recent content by beriapl

That does not explain why even "initial" conf doesn't work. Anyway - fixed by reinstall :)

Fixed by a clean reinstall, unfortunately. I didn't find much that I was able to fix... But, for further discussion: - "initial interfaces" - a copy of working one (but that works only when the update was failed and I revert it for the first time - after I was able to run update once again -...

Hello, One of nodes in my cluster failed after update to 6.4 - it doesn't start with the network When doing pveveriosn -v some packages got the error "not correctly installed" So, I got an idea to revert /etc/network/interfaces to old one, and it worked - after systemctl restart networking...

Sure: (I'm going to upgrade to newest on upcoming weekend) root@pve-07-06:~# pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve) pve-manager: 6.1-3 (running version: 6.1-3/37248ce6) pve-kernel-5.3: 6.0-12 pve-kernel-helper: 6.0-12 pve-kernel-5.3.10-1-pve: 5.3.10-1 ceph: 14.2.18-pve1...

A lot of tose errors only: May 05 14:18:31 pve-07-06 kernel: nfs: server 10.2.128.43 not responding, timed out May 05 14:18:34 pve-07-06 pvestatd[2084]: storage 'BACKUP01-NFS' is not online May 05 14:18:43 pve-07-06 pvestatd[2084]: unable to activate storage 'BACKUP01-NFS' - directory...

rpcinfo: root@pve-07-06:~# rpcinfo -p 10.2.128.43 program vers proto port service 100000 2 udp 111 portmapper 100000 3 udp 111 portmapper 100000 4 udp 111 portmapper 100000 2 tcp 111 portmapper 100000 3 tcp 111 portmapper...

That doesn't change anything. root@pve-07-08:~# pvesm set BACKUP01-NFS --disable 0 root@pve-07-08:~# pvesm status storage 'BACKUP01-NFS' is not online Name Type Status Total Used Available % BACKUP01-NFS nfs inactive...

I have big issue with NFS storage that is used only for backups in my proxmox cluster (12 physical nodes). Every time NFS server is rebooted i need to remove NFS share from proxmox, restart all 12 nodes, and the remount NFS share again, by adding it from scratch Is there any way to force...

I've tried almost all of those, and it worked with: LSI53C810 + HDDs on IDE. Thanks for suggestions!

Right, but what type of controller I should choose to install any driver then?

Hello, I'm a bit stuck here. I need to recover the old VM from died ESXi 6.0 I've got only files from VMWare, and in .vmx I've got this line: scsi0.virtualDev = "lsisas1068" I've converted .vmdk to qcow2 using qemu-img convert. I'm able to see boot same as in this thread...

So any way - why my bond0.52 aka vlan52 works, while tagged VM doesn't? For me it is the same vlan52 is "same" as tagged VM? Right? Or no?

So, it is not the same as this... auto vlan52 iface vlan52 inet static address 192.168.52.11/25 gateway 192.168.52.1 vlan-raw-device bond0

Yup. Since interface vlan52 works fine - it is good confirmation that it works.

That's what I'm doing. I'm tagging VM.