How to Fix Failed to Start Load/Save RFKill Status in Ubuntu

During Ubuntu system boot, users may encounter a red failure notice stating Failed to start Load/Save RFKill Status, corresponding to the failure of systemd-rfkill.service. The systemd-rfkill daemon is tasked with tracking and persisting the hardware and software killswitch states of wireless peripherals – including Wi-Fi chips, Bluetooth transceivers, and mobile broadband modems – across reboots. When this service fails, wireless adapters may default to a permanently disabled or soft-blocked state upon starting the machine. This defect typically stems from corrupted state files in /var/lib/systemd/rfkill/, ACPI firmware miscommunication, or permission restrictions.

Inspect systemd-rfkill Service Diagnostic Logs

Evaluating the system journal reveals whether the failure is triggered by a corrupted state file, missing device nodes in /dev/rfkill, or hardware driver crashes.

  1. Open a terminal window in Ubuntu.
  2. Check the status of the service:
    systemctl status systemd-rfkill.service
  3. Query the systemd journal for specific failure logs:
    journalctl -u systemd-rfkill.service -b
  4. Common failure messages include Failed to open rfkill device: No such file or directory, Failed to write /var/lib/systemd/rfkill/...: Input/output error, or rfkill state file is corrupted.

Purge Corrupted RFKill State Cache Files

The primary cause of the service failing to start is a zero-byte or malformed binary state file inside the systemd state repository, often produced following a kernel panic, battery loss, or improper power cut.

  1. Stop the active service:
    sudo systemctl stop systemd-rfkill.service
  2. Navigate to the RFKill state storage directory:
    ls -la /var/lib/systemd/rfkill/
  3. Inspect the listed files (such as pci-0000:00:14.3-wifi or platform-thinkpad_acpi-bluetooth). If any file shows a file size of 0 bytes or contains corrupted characters, it blocks the daemon from loading.
  4. Remove all cached state files:
    sudo rm -f /var/lib/systemd/rfkill/*
  5. Test starting the service cleanly:
    sudo systemctl start systemd-rfkill.service
  6. Confirm that the service is now active and clean:
    sudo systemctl status systemd-rfkill.service

Verify and Unblock Wireless Devices via RFKill Utility

If hardware devices are trapped in a soft-blocked condition, systemd cannot register their operational states properly during boot sequences.

  1. Check the physical and software states of all wireless radios:
    rfkill list all
  2. Review the output for any device indicating Soft blocked: yes.
  3. Unblock all wireless interfaces simultaneously:
    sudo rfkill unblock all
  4. Re-run rfkill list all to verify that both Soft blocked and Hard blocked show no across Wireless LAN and Bluetooth.
  5. If a device reports Hard blocked: yes, verify whether your laptop has a physical sliding hardware switch, or press the dedicated function key (e.g. Fn + F2 or Fn + PrtScr) to disengage the physical circuit lock.

Mask the Service on Virtual Machines or Desktops Without Radios

On virtual machines (such as KVM, VirtualBox, or VMware) or desktop motherboards that do not contain Wi-Fi or Bluetooth hardware, the Linux kernel creates no /dev/rfkill device node. Attempting to start the service on such hardware predictably results in a boot failure. Masking the unit prevents systemd from attempting to load it unnecessarily.

  1. If running Ubuntu on a virtual machine or a desktop PC without wireless adapters, mask the service:
    sudo systemctl mask systemd-rfkill.service systemd-rfkill.socket
  2. Masking links the unit to /dev/null, eliminating the red failure message during boot without affecting wired networking.
  3. If you later install a wireless card, you can easily restore the service with:
    sudo systemctl unmask systemd-rfkill.service systemd-rfkill.socket

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.