Search results

After configure and activate firewall on a proxmox 7 cluster, webinterface stop show node status on 2 of 4 nodes after some minutes. If i disable proxmox cluster firewall again this 2 nodes return to show status. If i keep firewall on and do stop and start pvestatd nodes become on again for...

Some my vms have 2 disks: one small to SO and another big to data (share files, database etc). 9 in 10 problems on SO no need restore the big data disk...but web interface dont allow that. Its possible by command line i restore only one vm disk ?

Bug filled

If u have a template and clone to a LVM resource, cloud init drive is cloned on same LVM...after stop and start this Virtual Machine proxmox try create a new LV to cloud init and fail...so vm dont start. Seens same happens w Ceph and fixed...but lvm still failed. Please help.

Same problem Here. Proxmox ppl can check and solve this ?

Time to time proxmox main console stop showing CEPH status in Datacenter level and CEPH storage show a question mark (?):

About AES-NI issue on proxmox: Westmere CPU on proxmox support it .... i just tested in 5.2 and seens work. Anyone have any info about performance issues or others problems using guest CPU Westmere (or anyother) ?

I just upgrade servers memory from 8 gb each to 16 gb each and all problems desapear

I run a lot proxmox servers and cluster and almost all have PFsense as Firewall to network. All fine Until upgrade some this Proxmox to 5.2 and upgrade Pfsense on this Proxmox to 2.4 and 2.4.4.... Time to time PFsense network traffic stop on LAN (most times) or Wan... not all network cards die...

almost all clear (sticks to OS..crush map and so...). But no clear about "flash the Controller from IR to IT Mode" : U say i need change controller firmware or is just some setting on controller ?

You are Correct about H330 (its raid controller to R230). Ok. Lets try remove raid layer... Next questions is How do that ? - All hds are connected on H330, to make then visible to SO its need create a VD (i sopose only one disk per VD using raid 0) - After that i will finish with 4 vds: 2 vds...

For sure raid and 2 nodes are a problem. But why OSD disconect and reconect all time? Raid thing supose affect read/write osd daemon just stop respondind for some moments then return again...

Are 2 Dell R230 Servers w R430 hard controllers, raid 1 sata-disks disks Pvevesion -v show: proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve) pve-manager: 5.3-6 (running version: 5.3-6/37b3c8df) pve-kernel-4.15: 5.2-12 pve-kernel-4.15.18-9-pve: 4.15.18-30 pve-kernel-4.15.17-1-pve: 4.15.17-9...

My Ceph cluster 5.2 show very frequent erros on logs. I Upgrade to 5.3 and same happens: Logs show thins like it: 2018-12-22 06:55:01.142920 osd.1 osd.1 192.168.0.200:6804/2869 427 : cluster [ERR] 1.52 shard 1: soid 1:4a2819a2:::rbd_data.55156b8b4567.0000000000015ac0:head candidate had a read...

I installed some weeks ago a cluster w 3 nodes. Ceph network id done c 10 gb cards wo switch. I used the bond0 w broadcast. Each node have 2 or 3 ssds w arround 3 tb total. Some days ago i notice only in node 3 latency in all 3 ssds there(like 30 /60 apply/commit). OSDs in other two nodes...

Thx. I already done it. But maybe a fix on grub2 its a better solution (no sure how rare is that setup - xen inside proxmox).

I start using a CLoud datecenter solution... the cloud provider use XEN and give me a Debian7 64 bits instaled SO. I convert this debian to Proxmox server using this directions: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy Worked like a charm... but this move Proxmox until...

I have a cluster runing proxmox 3.4. Vms on DRBD. Guest SO is 2003 and 2008. Backup log show: INFO: Starting Backup of VM 103 (qemu) INFO: status = running INFO: update VM 103: -lock backup INFO: backup mode: snapshot INFO: ionice priority: 7 INFO: creating archive...

I will do on both servers... but can take weeks until new event (or not more events). Any idea whats can be problem source ?

Both servers are Dell T110. Pve Version output: proxmox-ve-2.6.32: 3.2-136 (running kernel: 2.6.32-32-pve) pve-manager: 3.3-1 (running version: 3.3-1/a06c9f73) pve-kernel-2.6.32-32-pve: 2.6.32-136 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.7-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2...