For a while, one small thing was driving me crazy every time I powered on my Proxmox machine. Not the CPU. Not the storage. Not the software. The fan. It was loud. Constantly loud. Full speed from the moment the machine started. And once I noticed it, I couldn’t ignore it anymore. That’s the annoying part about hardware problems like this — they don’t stay in the background. They slowly take over your attention until fixing them becomes the only thing you can think about. So I started digging. I checked the socket type. I removed the motherboard. I measured the mounting holes. I confirmed what I needed. Only then did the search begin. The setup itself was nothing exotic: an Intel Core i5-6500 sitting on a Lenovo ThinkCentre M900 motherboard, model IQ1X0MS (30BC), with an LGA1151 socket. A budget CPU on a budget OEM board — simple on paper, but not so simple when the fan refuses to behave. At that point, the goal was clear. I didn’t need the biggest cooler. I needed the quietest practical solution. So I compared a few options: Noctua NH-D15 - extremely powerful, but probably more cooler than this CPU really needed. be quiet! Dark Rock Pro 5 - premium, silent, and also a bit overkill here. Endorfy Fortis 5 - a strong, balanced option with good value. Endorfy Fera 5 - compact, affordable, and practical. be quiet! Pure Rock 3 - quiet, sensible, and enough for a 65 W processor. And after thinking it through, the choice became obvious. I went with the be quiet! Pure Rock 3. It was reasonably priced was more than enough for the i5-6500.And it solved the problem without turning the build into something unnecessarily expensive or oversized. But the cooler alone was not the whole story. No more background irritation. No more fighting the machine every time I wanted to use it. Just a simple fix that made the whole setup feel right again. And honestly, sometimes that’s the best kind of upgrade - not the flashy one, but the one that quietly removes a problem you were tired of living with.

The default Proxmox installation includes enterprise repositories. These repositories are paid, and you need a subscription token to access them. Without a token, you'll see errors during updates. These errors are harmless but annoying! :) First image (1) To eliminate these update errors, you need to disable or remove those enterprise repositories. Run these commands:mv /etc/apt/sources.list.d/ceph.sources /root/ceph.sourcesmv /etc/apt/sources.list.d/pve-enterprise /root/sources.list.d/pve-enterprise These commands safely move the enterprise repo files out of the active sources directory. Second image (2) No more error message :)

Hey everyone! 👋 I just open-sourced a new project: job-forge — an LLM-powered CV & job-matching assistant that runs entirely in your browser. ✅ Paste a job offer → get a tailored, ATS-optimized resume in seconds ✅ Matches job requirements against your skill profile automatically ✅ Supports Anthropic Claude, Gemini, Ollama (local), or any OpenAI-compatible proxy ✅ 100% private — all data stays in your browser, nothing stored on any server ✅ Built with TypeScript + React + Vite Whether you're actively job hunting or just want to stay sharp, this tool can save you hours of CV tweaking. Would love your feedback, stars, or contributions! 🔗 https://github.com/codemonkey-df/job-forge Let me know what you think! 🚀

Hello engineers, I recently configured my Proxmox instance with ZFS RAID1 (I need to test the recovery process :)). I then added three additional SSD disks and partitioned them with this command: mkfs.ext4 -L SSD-256GB /dev/sdX - -L: label flag - SSD-256GB: label (adjust for each disk, e.g., SSD-1TB, SSD-128GB) After that, I mounted them via /etc/fstab like this: UUID=4c1cebaf-8142-4b79-a0ea-45c26253ed75 /media/ssd-1-TB ext4 defaults,noatime,nofail 0 2UUID=b012b34c-bb86-408a-bebf-a91d1a1d3a49 /media/ssd-256-GB ext4 defaults,noatime,nofail 0 2UUID=55c39d33-8665-4ba6-9b45-1c513df36296 /media/ssd-128-GB ext4 defaults,noatime,nofail 0 2 Now I have three extra disks for playing around with :) Let me know how you use additional disks in Proxmox.

I recently installed Proxmox on my home lab server. I wanted to start deploying network apps and services on the Proxmox instance, but something didn't feel quite right. I knew everything wasn't fully ready. I wondered what I should do to make it solid. Then it hit me: I needed to ensure all my data and configs were safely backed up and recoverable at any moment. My first thought was RAID1. The challenge? I didn't know how to set it up properly in Proxmox. After some searching and learning, I discovered it's actually super simple :) I just reinstalled Proxmox with the right settings. I pulled two 1TB SSDs out of my laptop (I had four total) and installed them in the home lab server. During installation, on the target harddisk screen I just selected the ZFS RAID1 option, chose the correct disks, and that was it :) Now I've got RAID1 up and running. Of course, I should test the recovery process next, but I'm too excited and want to start playing around right away!