Recent content by teddyh2o

humm still not to run after 5.3 install. qm works fine. pveversion -v proxmox-ve: 5.4-2 (running kernel: 5.4.106-1-pve) pve-manager: 5.4-8 (running version: 5.4-8/51d494ca) pve-kernel-5.4: 6.3-8 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-4.15: 5.4-19 pve-kernel-4.15.18-30-pve: 4.15.18-58...

accidently upgraded to Proxmox 6.3 buster from 5.1 stretch without following the procedure. the end user used deb http://download.proxmox.com/debian/pve buster pve-no-subscription on stretch. i changed the repository to stretch and try to install proxmox-ve but getting this error Reading...

thank you that make sense now.

doh. I thought i could do daisy chain. (eg: 01-02->03->04->05->01) what is the performance like if 100GB connection goes through the switch instead?

any suggestion?

Hello, I was looking into Proxmox set up with Ceph on my full NVME servers. At first, I was looking into 40GB but that wasn't enough with SSD. Used following documents as guide line but wanted to get some feedback on my setup/settings (not implemented yet)...

public_network is on OSD = 4 x 10GB LACP bond Mon = 2 x 10GB LACP bond I just read the benchmark paper and it really helped me visualizing it.

I was using 4 x 10GB SFP+ bond with 802.3ad. But i guess i need to change it to 100GB QSFP28. Hopefully, i get better result with with it. I will make sure my pool are 3/2. thanks,

I am new to Proxmox/Ceph and looking into some performance issues. 5 OSD nodes and 3 Monitor nodes Cluster vlan - 10.111.40.0/24 OSD nod CPU - AMD EPYC 2144G (64 Cores) Memory - 256GB Storage - Dell 3.2TB NVME x 10 Network - 40 GB for Ceph Cluster Network - 1GB for Proxmox mgmt MON nod CPU -...