They Built a Proxmox Homelab From Dusty Laptops. Everyone Argued About the Screens.

Old laptops can run useful Proxmox homelab workloads, but 24/7 operation raises cooling, battery and recovery concerns. In one four-machine setup, retired laptops complemented a refurbished HP ProDesk and supported home services, monitoring and backups.

The build was already working when the discussion began. Its most debated details were the open laptop lids, Linux power-management behavior, display wear and how the smallest backup machine would recover the others.

Can old laptops run Proxmox 24/7?

Old laptops can serve as always-on Proxmox nodes when cooling, power and failure recovery have been checked.

The heart of the setup was a refurbished HP ProDesk 600 G6 with 32 GB of RAM and roughly 1.25 TB of storage. It handled cloud services and monitoring through two Linux containers running Docker workloads. The cloud side included Nextcloud, Immich, Frigate, and Actual Budget: personal files, photos, camera-related processing, and household finances, each with a different reason to stay available. The monitoring and management side included Arcane, Beszel, Homarr, Nginx Proxy Manager, Gitea, and Uptime Kuma. That is a lot of everyday infrastructure to squeeze into a machine that wasn't originally purchased to run a private cloud.

If the laptop is becoming a permanent server, the Proxmox installation guide is a useful checklist for network and disk assumptions.

The other nodes had simpler responsibilities. An older Dell laptop, with 16 GB of RAM and approximately 1.5 TB of storage, carried the media side: a Jellyfin LXC and another LXC running Docker for an arr application stack. A Lenovo Z50-70 with 8 GB of RAM ran Home Assistant. Finally, a separate HP laptop with 4 GB of RAM and a 750 GB drive was assigned to Proxmox Backup Server. External drives provided additional media storage. The inventory reads like an argument against the idea that every home service needs a brand-new mini PC, provided the workloads fit and the hardware remains dependable.

The practical design helps explain the warm reaction. Some people praised the improvisation. Another mentioned running a Proxmox host on an ASUS VivoBook alongside an HP thin client and a 2014 Mac mini. Someone else said they also kept a laptop running Proxmox around the clock. A commenter admired the table supporting the equipment, treating the ordinary furniture as part of the charm. This was a different kind of infrastructure showcase: no polished racks, no carefully matched chassis, just an arrangement that demonstrated how accessible self-hosting can be when the first hardware purchase is already behind you.

How should Linux handle laptop lids on a server?

Linux systemd-logind can control lid-close behavior, but consoleblank=0 disables console blanking rather than turning the screen off.

The most popular practical response went straight to Linux power management. A commenter pointed the owner toward /etc/systemd/logind.conf, suggesting HandleLidSwitch=ignore, HandleLidSwitchExternalPower=ignore, and HandleLidSwitchDocked=ignore, followed by a restart of systemd-logind. The goal was straightforward: closing a laptop lid shouldn't suspend a host that needs to keep running services. The systemd documentation confirms that ignore is an available action for lid events. It also explains that behavior can depend on external power, docking, and other software that handles those events, so the configuration needs to be checked on the actual machine.

There was an amusing twist. The owner had already configured the lid switch to be ignored. They had also deliberately avoided stacking the laptops because of airflow. The remaining problem was more cosmetic and more physical: perhaps the lids could be lowered a little further so the screens switched off, without sealing off a route for heat to escape. That is a very specific compromise, familiar to anyone who has pushed aging consumer hardware into a job it wasn't designed around. A closed lid looks tidier. An open lid can make cooling easier on some models. A half-open lid is the messy answer when both things matter.

Other participants proposed turning off the displays directly, dimming or blanking the console, using function keys where supported, or even disconnecting a screen. One person recommended vertical laptop stands, subject to the placement of the ventilation openings. The discussion also contained a useful trap: a suggested consoleblank=0 boot argument was presented as a way to blank the display. According to the Linux kernel parameter documentation, zero disables the console blank timer. It is therefore the wrong value if the goal is to make the console go dark automatically. A great many homelab fixes live in tiny configuration details like that, where one character can reverse the intended behavior.

What are the reliability risks of laptop homelabs?

Aging batteries, limited cooling and single-drive storage can become the weak points of a laptop-based server fleet.

Some readers were uneasy about leaving aging laptops powered up continuously. One said laptops weren't built for constant use; another warned that displays might wear if they remained illuminated. Others pushed back with personal examples of laptops running for years. A participant reported a Dell system operating around the clock since 2013, while another argued that sustained use is reasonable when processor load stays within the machine's cooling capacity. Those anecdotes aren't controlled reliability tests, but neither is the blanket claim that a laptop automatically becomes unsafe or unsuitable the moment it stops being portable.

For media workloads like Plex, the LXC versus VM comparison helps keep memory and GPU allocations realistic.

The more useful objections concerned heat and dust. Several commenters noted that some laptops vent heat through the keyboard area or become noticeably warmer with the lid closed. One person remembered propping laptop lids open while running a similar improvised homelab. Another pointed out that compact cooling assemblies can gradually fill with dust and reduce airflow, leading to thermal throttling even if a machine continues to run. The owner had already anticipated part of this problem by not stacking the systems. Whether that is enough depends on each machine's fan path, ambient temperature, actual load, and maintenance. No one in the discussion supplied long-term temperature readings or failure-rate data.

Battery management produced another suggestion: if a laptop supports a charging threshold, avoid keeping its battery at full charge constantly. One commenter proposed a target around 50 percent. That number was offered as practical advice, not as evidence that every laptop supports it or that it is the correct setting for every battery. Aging batteries deserve attention in a device that rarely leaves the wall socket, and hardware-specific charging controls can be worth checking. At the same time, the value of a battery in this role is easy to understand. Unlike a stripped-down desktop, a laptop can offer limited protection against a brief power interruption, although it should not be mistaken for a monitored UPS with a tested shutdown policy.

The argument became more revealing when the criticisms drifted toward appearances. A working setup could be dismissed as amateur because of the open lids, visible displays, or furniture. The owner, meanwhile, wasn't presenting a rack-mounted product for sale. They were showing how an assortment of household computers supported actual services. Presentation still matters when poor placement causes overheating or makes maintenance dangerous. But an untidy-looking homelab isn't automatically unreliable, and a photogenic one isn't automatically resilient. Fans, backup verification, restore time, and the ability to spot a failing drive are harder to photograph than neatly routed cables.

What makes a recycled Proxmox homelab worth keeping?

Keep recycled hardware only when its services are recoverable and the maintenance burden is lower than the value it delivers.

The backup node was almost lost in the excitement over the laptops. It had the smallest listed memory configuration, 4 GB, and a modest 750 GB drive, but it had a distinct role: Proxmox Backup Server. That decision is worth noticing. The builder didn't simply run a collection of applications and call the project finished. They had set aside a machine for recovery infrastructure. Proxmox Backup Server supports backup verification, which can help detect corruption. A dedicated backup host also keeps a recovery function separate from the three compute nodes, though physical separation by itself doesn't guarantee data safety.

There are unanswered questions. How often are backups taken? Which workloads and data volumes are included? Are copies kept somewhere that survives the loss of the room, the backup laptop, or an attached drive? Has a restore been rehearsed? The discussion didn't say. The mention of external media drives shouldn't be confused with an off-site backup strategy, either. These aren't criticisms of the owner; they're the questions that become relevant once the system holds photos, household records, and services people expect to find available. A cheap homelab can provide real value, but the stakes rise as soon as everyone in the household starts depending on it.

The most memorable detail wasn't the number of containers or the storage total. It was the image of laptops doing useful work while everyone debated how far their lids should close. The discussion showed that success doesn't erase practical compromises. Somewhere between the glowing screens, the cramped cooling systems, and the dedicated backup laptop sits the most honest definition of a homelab: it works, and there is always one more thing to fix.

I would keep the recycled laptops online if temperatures, disks, lid policy and tested backups were all understood. If a swollen battery, overheating or unreliable storage appears, I would remove that machine from continuous service rather than celebrate the recycling story.