Recent content by jdancer

During the next kernel update, dracut will only install the required drivers required for booting up.

I'm still on Proxmox 8 at home. I do NOT use a transceiver at home. I use a direct-attached cable (DAC) from the NIC to the switch. I believe I the issues with the ConnectX-3 not working with Proxmox 9 may have to do with transceiver compatibility. Won't know until I migrate my server during...

True this. The Proxmox team may want to consider just using GRUB bootloader exclusively in future versions like how other operating systems do it. And to avoid the issues from systemd-boot to GRUB migrations. Can confirm that the GRUB bootloader can still boot with Secure Boot disabled. Have...

No issues on 13th-gen Dells. Time to upgrade the 12th-, 11th-, 10th-gen Dells. On 13th-gen Dells, I have UEFI, Secure Boot, X2APIC, I/OAT DMA enabled. SR-IOV disabled.

You'll probably want to use the alternative method created by member PwrBank to overcome the built-in EXSi throttling https://github.com/PwrBank/pve-esxi-import-tools/tree/direct-send More info about this method at https://forum.proxmox.com/threads/import-from-esxi-extremely-slow.173450

Assuming it's a 3-node Ceph cluster with no switch per https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Example I put the Ceph public, private, and Corosync network traffic on this network. I also set the datacenter migration network to use this network (either via GUI or CLI) and...

If this 3-node cluster is never going to be expanded, create a full-mesh broadcast network per https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Example and https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Broadcast_Setup This setup removes the switch and put the...

I use Dell R630s in production as Proxmox Ceph clusters. These were converted from VMware/vSphere. They all have the same hardware (CPU 2 x 2650v4, Storage SAS 10K, Storage controller HBA330, RAM 512GB, NIC Intel X550 10GbE) running latest firmware. Ceph & Corosync network traffic on isolated...

May be the issue is with the megaraid_sas driver not able to use "mixed-mode" RAID configuration (RAID and HBA [passthrough]-mode) is the root cause. No idea since I don't use mixed-mode. Still stand with my recommendation on getting a used Dell HBA330 controller. They are cheap to get. Got one...

If it matters, the Dells in production are 13th-generation using Intel Broadwell CPUs. Still firmware supported by Dell. They will eventually get EOL'd by Dell but then again, I have 10th-, 11th-, 12th-gen Dells running Proxmox. I recommend single-socket servers. If you want to save even more...

Yes, for live migration, manual/HA. Hence, should really have same amount memory across nodes.

Migrating Dell VMware clusters at work to Proxmox. I just make sure all the hardware is the same (CPU, memory, storage, storage controller, networking, firmware, etc). Swapped out Dell PERCs for Dell HBA330s since ZFS & Ceph don't work with RAID controllers. Standalone Dells are running ZFS...

Ceph really, really wants homogeneous hardware. Meaning same CPU, memory, networking, storage, storage controller, firmware, etc. While it's true you can run a 3-node cluster, you can only have a 1-node outage. With 5-nodes, can have 2-node outage. So, for production, 5-node minimum. With that...

I use a Dell PERC H730P in a Proxmox Backup Server (Dell R530). I deleted the virtual disks before converting it to HBA-mode. It's also running the latest firmware from Dell. Proxmox uses the megaraid_sas driver. As for the other Dells in production, I swapped out the PERCs for Dell HBA330s...

The 2 x R530s in question are Proxmox Backup Servers. I did a clean install of PBS 4. It was previously running PBS 3. May want to double check the PERC settings in the BIOS again and confirm it's in HBA mode. Another option it put in a single unrelated drive and see if at least Proxmox and...