Power blips at 4 a.m. Three minutes later the lights are back, your switch is back, your router is back — and your mini PC homelab is still dark. You’re SSHing into nothing because the box never restarted.
The fix is almost always a single BIOS setting that ships disabled on consumer mini PCs. Vendors default to off because their typical customer wants to be present when the PC boots. For a headless 24/7 homelab, that default is exactly wrong. If that box is your router, the whole house goes dark with it; see mini PC hardware for a pfSense firewall.
This guide covers the setting name on every common mini PC vendor, two failure modes the setting alone doesn’t solve, and how to confirm it works without standing next to the breaker box.
The setting you’re looking for
It has different names on different boards but it does the same thing: tells the firmware what to do when AC power is restored after being cut.
The three values you’ll see, in some combination:
- Power Off (or “Stay Off” / “Last State Off”) — default on almost every consumer mini PC. After AC returns, board stays off until you press the button.
- Power On (or “Always On” / “Last State On”) — what you want for a homelab box. After AC returns, board powers on automatically.
- Last State — restores whatever state the machine was in when power was lost. If it was running, it boots; if it was off, it stays off. Acceptable, but Power On is more predictable for a server.
Pick Power On. “Last State” sounds clever but it bites you the first time you shut the box down to add RAM, forget to power it back on, and then lose power three weeks later — it stays off because that was its last state.
Intel NUC: After Power Failure
Intel’s NUC BIOS glossary calls the setting After Power Failure, under Power → Secondary Power Settings in Aptio V BIOS. Visual BIOS adds Advanced before that path. Choose Power On; Last State restores the previous on/off state.
Check the documentation for your exact NUC model and firmware. A similarly shaped mini PC is not necessarily using NUC firmware. NUCs are now built by ASUS; Intel NUC vs mini PC for a homelab covers current models.
Minisforum: Restore AC Power Loss
Look for Restore AC Power Loss, but treat that as a search term rather than a guaranteed Minisforum menu label. The official Minisforum support catalogue provides model-specific BIOS and auto-power-on instructions. Follow the entry for the model printed on the chassis.
For example, the Minisforum N40 instructions use BOOT → Auto Power On → Enable, then F4 to save. If your firmware uses Restore AC Power Loss, choose its power-on value. Do not assume another model’s menu path or undocumented unlock shortcut applies.
Dell: AC Recovery
For the Wyse 5070, open Power Management → AC Recovery and choose Power On. Dell documents the setting in the Wyse BIOS reference. Last Power State is a different choice: a machine shut down before the outage can remain off.
Set this during a Wyse 5070 homelab build and verify it after saving the firmware configuration.
HP: After Power Loss
The HP t630 troubleshooting guide places After Power Loss under Advanced → Power-On Options. Choose Power on; the other choices are Power off and Previous state.
HP explicitly notes that available Computer Setup options depend on the hardware. Use the matching manual for a T620 or T640 rather than assuming the t630 path carries over. The HP thin client guide compares the models before you choose a firmware package.
Lenovo: After Power Loss
The ThinkCentre M73 Tiny guide uses Power → After Power Loss → Power On in Setup Utility. Save with F10 and confirm when prompted.
This is distinct from Automatic Power On, which also contains wake scheduling on that model. Match the guide to your particular ThinkCentre Tiny before relying on a menu path from another generation.
ASUS: Restore AC Power Loss
ASUS documents Advanced → APM Configuration → Restore AC Power Loss → Power On in its Restore AC Power Loss support note. Availability still depends on the board and firmware. If the option is absent, consult the model’s support page instead of treating an unrelated BIOS screenshot as proof.
Two failure modes the BIOS setting alone doesn’t fix
Setting AC Recovery → Power On handles the common case. There are two scenarios where it isn’t enough.
1. Brownouts and rapid power cycles
If AC drops for less than the firmware considers a real outage — or if power flickers off and back on inside a second or two — some BIOSes treat it as noise and don’t re-trigger the auto-power-on. The box ends up off even though “Power On” is configured.
The fix is upstream of the BIOS: put the mini PC behind a small UPS that smooths brownouts into either a clean ride-through or a clean shutdown. A 600–900VA UPS with pure sine wave output handles the typical homelab mini PC fleet easily and costs roughly $90–$170. How long a UPS will hold your box, which unit to buy, and why VA is the wrong number to shop on at these loads are worked through in UPS sizing for a mini PC homelab; most 10W boxes get 30+ minutes of runtime on a small UPS, which is more than enough to survive any blip and gracefully shut down for a real outage. What your box actually draws is covered in the mini PC power consumption post.
2. The box boots but the OS doesn’t come up
A second silent-failure mode: the hardware powers on after AC returns, but the boot path stalls. Common culprits:
- GRUB waiting for input because the last boot was unclean. Set
GRUB_RECORDFAIL_TIMEOUT=5in/etc/default/gruband runupdate-grubon Debian/Ubuntu. - A network-mount blocking systemd boot. An NFS or CIFS mount in
/etc/fstabwithoutnofail,x-systemd.device-timeout=10swill hang boot for minutes if the file server isn’t up yet. Add those options. - A docker-compose stack with hard dependencies. Use
restart: unless-stoppedon every service — let containers crashloop until their database is up rather than relying on boot order.
The pattern: the box powered on fine, but you can’t tell because you can’t SSH in. The next section covers how to catch this before it happens at 4 a.m.
Verify recovery after a clean shutdown
Save the firmware setting, shut down the operating system cleanly, and wait until the machine is off. Disconnect power to the mini PC’s adapter, wait for its standby light to go out if it has one, then reconnect it. With an always-on recovery setting, it should start without pressing the power button.
Use a planned maintenance window. Keep shared networking and storage powered while checking this one machine; there is no need to interrupt the entire circuit. A normal reboot does not exercise AC-loss recovery, and a clean shutdown followed by power restoration does not prove recovery from an unclean filesystem state.
If the machine powers on but services remain unavailable, attach a monitor and inspect the boot process. Check the bootloader, storage mounts and service status before changing the AC-recovery setting again.
A related setting worth turning on while you’re in there
Wake-on-LAN is the other thing every homelab box should have configured, for the reverse situation: deliberately powering the box off and waking it later without standing next to it.
In BIOS, look for Wake on LAN, Power On by PCIe, or Resume on LAN and enable it. In Linux, confirm the NIC supports it and that it’s armed for magic-packet wakeup with ethtool -s <iface> wol g (the wol g argument means “wake on magic packet”). The ethtool man page documents the full WOL flag set (source) — g is the one almost everyone wants.
Test it from another box on the same LAN: wakeonlan <mac> (install the wakeonlan package on Debian/Ubuntu). If the box wakes, you’re done. If it doesn’t, check that the BIOS option is actually enabled and that ethtool <iface> reports Wake-on: g rather than Wake-on: d (disabled).
TL;DR
- The setting is AC Recovery → Power On (or whatever your vendor calls “After Power Failure”). Set it before you install the OS, not after the first outage.
- Add a small UPS to smooth brownouts that confuse the BIOS into not re-triggering auto-on.
- After a clean shutdown, remove and restore power to the adapter in a maintenance window. A normal reboot does not check AC recovery.
- Fix the boot-path stalls that prevent SSH from coming back: GRUB recordfail, dirty-fsck pauses, blocking NFS/CIFS mounts.
- Enable Wake-on-LAN in BIOS and arm it with
ethtoolwhile you’re already in there.
Most “my homelab didn’t come back from the outage” stories trace to one of two things: this BIOS setting was never enabled, or the OS booted but something on the boot path stalled. Both are fixable in ten minutes. Worth doing before you actually need it.
For sizing the UPS you put in front of your fleet, the UPS sizing guide covers how to translate idle wattage into UPS runtime; if the fleet is still on paper, how to build a low power homelab works the same numbers forward from a watt budget instead. And if you’re still picking the box itself, the N100 buying guide covers what to check in the BIOS before buying, AC recovery included, and N150 vs N100 covers what the 2026 Twin Lake refresh changed if you are buying new.
While the machine is open in front of you, this is not the only firmware default that suits a desktop rather than a server. Wake-on-LAN, the virtualization extensions, boot mode, the C-state limit that decides idle draw, and the radios a headless box never uses are all worth changing in the same sitting — the full pass is in mini PC BIOS settings for a 24/7 homelab.
Related across the network
- MPPT vs PWM Charge Controllers for Homelab Solar — solarhomelabs.com
