Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Kernel 6.18.1-arch1-2 update breaks boot - missing vfat module prevents /boot mount
Reported by KhlifiIsmail · filed Jan 9, 2026Closed upstream on 2026-01-11 by ryanrhughes. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Dual NVMe setup (nvme0n1 and nvme1n1, both ~476.9GB), Dual boot Windows 11 + OmArchy, Bootloader: Limine, Linux root: /dev/nvme0n1p6 (225.3GB), EFI/Boot: /dev/nvme1n1p5 (1GB vfat, UUID: FA2C-5AA6)
What's wrong?
After updating OmArchy today (January 9, 2026), the system failed to boot and dropped into emergency mode. The kernel was updated to version 6.18.1-arch1-2.
Error Details:
System entered emergency mode on reboot
systemctl --failed showed two failed services:
boot.mount - failed to mount /boot partition
ufw.service - firewall service failed (secondary issue)
Root Cause:
The updated kernel (6.18.1-arch1-2) was missing the vfat kernel module. Since my /boot partition uses vfat filesystem (common for EFI partitions), the system couldn't mount /boot, which prevented normal boot.
When attempting modprobe vfat from emergency mode, got error:
FATAL: Module vfat not found in directory /lib/modules/6.18.1-arch1-2
System Configuration:
Dual boot setup (Windows + OmArchy)
/boot partition: vfat filesystem on /dev/nvme1n1p5 (UUID: FA2C-5AA6)
Bootloader: Limine
Fix:
Had to boot from OmArchy live USB, chroot into the system, and reinstall the linux package:
bashmount /dev/nvme0n1p6 /mnt
mount /dev/nvme1n1p5 /mnt/boot
arch-chroot /mnt
pacman -S linux
mkinitcpio -P
This regenerated the kernel with all necessary modules including vfat.
Impact:
Complete system boot failure - requires live USB to recover.
View raw text
### System details Dual NVMe setup (nvme0n1 and nvme1n1, both ~476.9GB), Dual boot Windows 11 + OmArchy, Bootloader: Limine, Linux root: /dev/nvme0n1p6 (225.3GB), EFI/Boot: /dev/nvme1n1p5 (1GB vfat, UUID: FA2C-5AA6) ### What's wrong? After updating OmArchy today (January 9, 2026), the system failed to boot and dropped into emergency mode. The kernel was updated to version 6.18.1-arch1-2. Error Details: System entered emergency mode on reboot systemctl --failed showed two failed services: boot.mount - failed to mount /boot partition ufw.service - firewall service failed (secondary issue) Root Cause: The updated kernel (6.18.1-arch1-2) was missing the vfat kernel module. Since my /boot partition uses vfat filesystem (common for EFI partitions), the system couldn't mount /boot, which prevented normal boot. When attempting modprobe vfat from emergency mode, got error: FATAL: Module vfat not found in directory /lib/modules/6.18.1-arch1-2 System Configuration: Dual boot setup (Windows + OmArchy) /boot partition: vfat filesystem on /dev/nvme1n1p5 (UUID: FA2C-5AA6) Bootloader: Limine Fix: Had to boot from OmArchy live USB, chroot into the system, and reinstall the linux package: bashmount /dev/nvme0n1p6 /mnt mount /dev/nvme1n1p5 /mnt/boot arch-chroot /mnt pacman -S linux mkinitcpio -P This regenerated the kernel with all necessary modules including vfat. Impact: Complete system boot failure - requires live USB to recover.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.