Those are on the cheaper and slower side of consumer SSDs. They will not perform well with sustained load and the primarily sync writes that Ceph does.
The recommendation for enterprise SSDs with power loss protection (PLP) is there for good...
I don't run nested virtualization using Windows guests but do with Linux guests especially with Proxmox, ie, phystical Proxmox -> vitual Proxmox -> Linux guest.
I do use CPU type of 'host' as your screenshot shows. As for number of cores, I see...
I run Proxmox on 10th through 14th-generation Dells at work. Yup, this is with latest Proxmox 9.1.x with latest 7.0.x kernel. No issues.
I just made sure the machines has the latest firmware and BIOS/UEFI.
I do NOT use any RAID controllers...
You are better off flashing the 12th-gen PERCs to IT-mode via https://fohdeesha.com/docs/perc.html
Do NOT skip any steps and record the SAS address.
No issues in production.
Dell HBA330 mini-mono versions are definately for 13th- and 14th-gen Dells.
For 12th-gen Dell PERCs (H310/H710/H710P/H810), use https://fohdeesha.com/docs/perc.html. No issues in production.
Do NOT skip any steps and take your time. If you want...
Been testing EC pools with plugin=ISA technique=reed_sol_van with VMs with additional storage optimizations. Weirdly enought, it's faster in read operations than replication. Not complaining.
I've been migrating from VMware vSphere to Proxmox Ceph at work on 13th-gen Dells.
Ceph really, really, really wants homogeneous hardware, ie, same CPU, RAM, NIC, storage, storage controller, firmware, etc, etc. I swapped out PERCs for Dell...
Seeing that the MD3200i is a legacy SAN, maybe cheaper to migrate to Ceph. Been migrating VMware legacy SAN infrastructure to Proxmox Ceph. IMO, need a minimum of 5-nodes. So, can lose 2 nodes and still have quorum. Isolated switches for Corosync...
A better option, IMO, is to use a pure IT-mode storage controller like a Dell HBA330. Extremely cheap to get.
Uses the much simpler mtp3sas driver and don't have to deal with PERC storage drama.
No issues in production.
Been migrating 13th-gen Dells (R630s & R730s) from VMware to Proxmox Ceph. Clusters range from 3- to 9-nodes, all odd number for quorum.
All hardware is the same (RAM, CPU, NIC, storage, storage controller, firmware). Swapped out PERCs for Dell...
Considered best practice that cluster traffic have it's own network/vlan.
I just create a additional vmbr (ie, vmbr1 or whatever number you want [best to use a VLAN number, if used]) and when I create the cluster, make sure it uses that network...
Most large organizations treat Proxmox VE in terms of accrediation/ATO as an appliance. Since PVE is a hypervisor platform. It's NOT meant to directly run workloads. Workloads are done via VMs/LXCs.
Same with PBS & PDM. It's treated as an...
A better option is to avoid the PERC HBA-mode drama and get a Dell HBA330. It's a true IT-mode storage controller based on the LSI3008 chip. Real cheap to get.
Just make sure to remove any existing virtual disks prior to use and flash to latest...
Currently using a full-mesh 3-node Proxmox Ceph cluster using Resource Pools.
Created individual accounts and have them log in using the Proxmox VE authentication realm.
Each VE account has PVEAdmin permissions to the Ceph pools and Networking...
Use consumer SSDs at your peril. They fail and fail spectacularly.
Only real solution is enterprise SSDs with PLP (power-loss protection) and for endurance.
Don't know if matters but latest firmware for Dell HBA330 is 16.17.01.00 A08. May or may not help your issue.
No issues on 16-drive bay R730s in production.