Enable Restore-on-AC-Power-Loss on kai-desktop-tower BIOS (no remote power-cycle path today) #256

New issue

Closed

opened 2026-06-07 04:28:04 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-07 04:28:04 +00:00

Owner

Problem

kai-desktop-tower (and its WSL node) is the planned local-LLM host, but it sits offline whenever it has been powered down - e.g. found offline 18h after a qwen-ask test, both kai-desktop-tower (Windows) and kai-desktop-tower-wsl last seen 18h ago in tailscale status. Unlike kai-server, the tower is not on the Kasa HS300 (see machine-power-strip skill - index 4 is kai-server, the tower is absent), so there is no remote AC power-cycle path to it. If it loses power or is shut down, nothing in the fleet can bring it back without physical access.

Ask

Enable the BIOS/UEFI "Restore on AC Power Loss" setting (vendor names vary: "AC Power Recovery", "Power On After Power Failure", "After Power Loss -> Power On") so the tower auto-boots when mains power returns, instead of staying off.

Note on scope: this only recovers from a power event (outage, blip, accidental unplug). It does not cover a clean OS shutdown or sleep - for that you also want Wake-on-LAN configured, or the tower added to a switchable outlet. Treat WoL as a follow-up if remote wake from a soft-off state is also wanted.

Acceptance

BIOS set to power-on after AC loss, verified by pulling power and confirming auto-boot.
Document the chosen setting name + value in machine-kai-desktop-tower skill.
Decide + note whether WoL is also wanted (separate follow-up if so).

coilyco-flight-deck/infrastructure#242 - always-on hardening for the tower WSL k3s node (WSL lifecycle, the OS-level sibling of this hardware-level ask).
coilyco-bridge/agentic-os-kai#609 - k3s-agent disabled on tower-wsl.
machine-power-strip / machine-kai-desktop-tower skills.

## Problem `kai-desktop-tower` (and its WSL node) is the planned local-LLM host, but it sits offline whenever it has been powered down - e.g. found offline 18h after a `qwen-ask` test, both `kai-desktop-tower` (Windows) and `kai-desktop-tower-wsl` last seen 18h ago in `tailscale status`. Unlike `kai-server`, the tower is **not** on the Kasa HS300 (see `machine-power-strip` skill - index 4 is kai-server, the tower is absent), so there is no remote AC power-cycle path to it. If it loses power or is shut down, nothing in the fleet can bring it back without physical access. ## Ask Enable the BIOS/UEFI **"Restore on AC Power Loss"** setting (vendor names vary: "AC Power Recovery", "Power On After Power Failure", "After Power Loss -> Power On") so the tower auto-boots when mains power returns, instead of staying off. Note on scope: this only recovers from a *power* event (outage, blip, accidental unplug). It does **not** cover a clean OS shutdown or sleep - for that you also want Wake-on-LAN configured, or the tower added to a switchable outlet. Treat WoL as a follow-up if remote wake from a soft-off state is also wanted. ## Acceptance - [ ] BIOS set to power-on after AC loss, verified by pulling power and confirming auto-boot. - [ ] Document the chosen setting name + value in `machine-kai-desktop-tower` skill. - [ ] Decide + note whether WoL is also wanted (separate follow-up if so). ## Related - `coilyco-flight-deck/infrastructure#242` - always-on hardening for the tower WSL k3s node (WSL lifecycle, the OS-level sibling of this hardware-level ask). - `coilyco-bridge/agentic-os-kai#609` - k3s-agent disabled on tower-wsl. - `machine-power-strip` / `machine-kai-desktop-tower` skills.

coilysiren referenced this issue

2026-06-07 05:00:12 +00:00

kai-desktop-tower: 2:50am Windows maintenance reboot drops both tailnet nodes, no remote recovery (~19h offline) #257

coilysiren added the

label

2026-06-17 07:05:40 +00:00

coilysiren commented

2026-06-17 08:22:35 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:22:35 +00:00