Search results

I run H310 flashed to IT-mode in production. Zero issues. And yes, queue depth does matter.

Migrated a production 5-node 16-drive bay R730 VMware cluster over to Proxmox Ceph. Swapped out the PERC H730 for HBA330 for "true" HBA mode. Updated HBA330 to latest firmware. First two drives are Intel DC S3710 SATA boot drives using ZFS RAID-1. Rest of drives are OSDs. Workloads range from...

My reply also works for 8.2.x https://forum.proxmox.com/threads/d...t-works-with-vmware-pvscsi.144806/post-652170

You'll want to see my reply here https://forum.proxmox.com/threads/best-practices-for-setting-up-ceph-in-a-proxmox-environment.148790/post-673329 Since migrating off of VMware to Proxmox, no issues besides the typical drive dying and needing replacing. Will be migrating a 15-host VMware...

I believe 64GBs is the minimum. Don't think 32GB is enough. I do have a server using 100GB SSDs to ZFS RAID-1 Proxmox. So, 128GB is plenty. Since ZFS is a volume manager just like LVM, I would skip the LVM and use ZFS. You can JDOD ZFS, ie, ZFS RAID-0. Of course, backup it up.

Considered best practice to mirror the OS using RAID-1. In my case, I use two small drives to ZFS RAID-1 Proxmox itself. As for the rest of the storage, it depends on the use case. If a single drive, I do use ZFS RAID-0 (stripe), so can use snapshots, rollbacks, compression, error checking...

I found installing Proxmox in UEFI mode on 12th-gen Dells is unpredictable. Luckily, the VMs are already in BIOS mode, so just installed Proxmox using BIOS mode. However on 13th-gen Dells, Proxmox UEFI install with Secure Boot enabled works fine. Go figure.

I use SAS HDDs in production. Since they are meant to be used on HW RAID controllers with a BBU, their write cache is turned off. May want to check if the HDDs have their cache enabled. VMs range from databases to DHCP/PXE servers. Not hurting for IOPS. I use the following optimizations learned...

Migrated off TrueNAS SCALE to Proxmox because didn't have full CLI functionality. Used the LXC *Arr scripts from here https://tteck.github.io/Proxmox I am using privileged containers because didn't want to configure UID/GUID remapping. Using Homarr as the jumping point to other *Arr LXCs. Boot...

I use POM in production on stand-alone bare-metal servers (which also doubles as a PBS server) and in a Debian 12 VM. It works. Just make sure to change /etc/apt repo files to point to the POM server.

When I migrated 13th-gen Dells to Proxmox Ceph, I swapped out the PERC for a Dell HBA330 (which is a pure IT-mode controller). Then I used ZFS RAID-1 to mirror Proxmox. Rest of drives are OSDs. I don't think the HW RAID PERC can be configured in both HW RAID mode and pass-through mode at the...

I've used the Proxmox ESXi migration tool on production VMs with no issues. You'll need to disable session timeouts on the ESXi host(s). Make sure the VMs are off and NO snapshots. ZFS works fine on SATA drives. ZFS provides snapshots, rollbacks, compression, and error checking of data and...

Should show up in the Proxmox installer as a boot target. Was for me on a BOSS-S1 and showed up as DELLBOSS-VD.

You need to disable maxSessionCount and sessionTimeout on the ESXi host per https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Automatic_ESXi_Import:_Step_by_Step

Yeah, really. By default, SAS HDDs ship with write cache disabled. The reason being that these drives were meant to be used on a HW RAID controller with BBU. The HW RAID will do the caching on behalf of of the drives. So, when I converted the Dells over to Proxmox Ceph and replaced the HW RAID...

See my reply at https://forum.proxmox.com/threads/debian-11-not-booting-with-virtio-scsi-single-but-works-with-vmware-pvscsi.144806/post-652170 It's still valid for Proxmox 8.2.x

For proof-of-concept, 3-nodes will suffice. For production, you really, really want a minimum of 5-nodes. That way, 2-nodes can fail and still have 3-nodes for quorum. I converted a fleet of 13th-gen Dells which used to run VMware vSphere over to Proxmox Ceph. Made sure all the nodes had the...

Since Proxmox is Debian with a custom Ubuntu kernel, pretty much runs on a 64-bit CPU with Intel VT/AMD-V hardware virtualization. Have it running on Intel Sandy Bridge, Haswell, and Broadwell CPU generations with high CPU core counts with no issues.

Supposedly someone over at r/Proxmox got it working at 6.0 and 5.5. Can always manually copy over the .vmdk and .vmdk-flat files over and do a 'qemu-img convert'.

I manage several production 5- and 7- node Proxmox Ceph clusters. Why 5 or 7 nodes? Well, with 3 nodes, you can only tolerate a single node failure and I believe because of lack of quorum, no writing of data will occur. Strongly suggest 5-nodes at minimum that way one can tolerate 2 node...