Fix USB drives, Docker or VPNs failing right after a kernel update
On this 4.0.4-1 workstation kernel-modules-hook 0.1.7-3 is installed, /usr/share/omarchy/install/omarchy-base.packages line 66 lists it, /usr/share/omarchy/install/config/enable-services.sh line 5 runs 'systemctl enable linux-modules-cleanup.service', and the service is enabled. The package's 10-linux-modules-pre.hook and -post.hook trigger on usr/lib/modules/*/vmlinuz and save and restore the modules of $(uname -r), so they also cover the linux-omarchy kernel that 4.0.4 installs through migration 1789325478 (running kernel here is 7.2.5-3-omarchy, owned by linux-omarchy). The Arch package page shows kernel-modules-hook 0.1.7-3 in extra/any depending on rsync. Forum thread 291554 confirms the cause and the reboot fix ('they're no longer on disk after you updated the kernel. Reboot into the new kernel'). 'pacman -S kernel-modules-hook' carries no -u, so the ALPM guard does not block it. Not exercised: no kernel update was performed.
Symptom
Straight after an update, before rebooting, a USB stick shows up in dmesg but will not mount (unknown filesystem type 'exfat'), Docker or WireGuard refuses to start, and loading a module fails:
modprobe: FATAL: Module wireguard not found in directory /lib/modules/7.2.3-arch1-1
Everything that was already loaded keeps working.
Cause
The running kernel stays in memory until reboot, but pacman removes its module tree /usr/lib/modules/$(uname -r) when it installs the new kernel package. Any module not already loaded can no longer be found.
Fix
Reboot into the new kernel, which is the fix for this boot.
**Plain Arch:** prevent it next time with the hook that copies the running kernel's modules back after the upgrade, and the timer-like service that cleans them up later:
sudo pacman -S kernel-modules-hook
sudo systemctl enable linux-modules-cleanup.service
**Omarchy 4:** this is already handled. kernel-modules-hook is in Omarchy's base package list and the installer enables linux-modules-cleanup.service (both confirmed on 4.0.4-1). If you still hit it, check both are present:
pacman -Q kernel-modules-hook
systemctl is-enabled linux-modules-cleanup.service
Verify
After the next kernel update and before rebooting, ls /usr/lib/modules/$(uname -r) still exists and sudo modprobe -n -v exfat resolves the module.