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.
systemd-stub prints “Failed to read *.cred, Volume corrupt” on boot (Limine + UKI)
Reported by FruitPnchSamuraiG · filed Jan 16, 2026Closed upstream on 2026-02-01 by dhh. 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
Omarchy 3.3.3 (stable, master), Linux 6.18.3-arch1-1, Limine 10.6.2 with systemd-stub (UKI), systemd init, btrfs (encrypted) root, vfat ESP mounted at /boot, Dell Inspiron 5502 (11th-gen Intel i5), dual-boot with Windows, Secure Boot disabled.
What's wrong?
On every boot, an error is printed very early:
systemd/src/boot/cpio.c:413@pack_cpio:
Failed to read nupcr-anchor.<machine-id>/<hash>.cred, ignoring: Volume corrupt
The system continues to boot normally afterward, but the error is always shown.
- The error appears during early boot (systemd-stub stage)
- Boot continues successfully after the message
- Rebuilding initramfs does not remove the error
- Rebooting does not remove the error
- Limine previously appeared as a UEFI bootloader entry, but after an update(cant remember which), the Limine entry is missing; only auto-created SSD entries remain
/boot/EFI/limine/limine_x64.efistill exists on the ESP
View raw text
### System details Omarchy 3.3.3 (stable, master), Linux 6.18.3-arch1-1, Limine 10.6.2 with systemd-stub (UKI), systemd init, btrfs (encrypted) root, vfat ESP mounted at /boot, Dell Inspiron 5502 (11th-gen Intel i5), dual-boot with Windows, Secure Boot disabled. ### What's wrong? On every boot, an error is printed very early: systemd/src/boot/cpio.c:413@pack_cpio: Failed to read nupcr-anchor.<machine-id>/<hash>.cred, ignoring: Volume corrupt The system continues to boot normally afterward, but the error is always shown. - The error appears during early boot (systemd-stub stage) - Boot continues successfully after the message - Rebuilding initramfs does not remove the error - Rebooting does not remove the error - Limine previously appeared as a UEFI bootloader entry, but after an update(cant remember which), the Limine entry is missing; only auto-created SSD entries remain - `/boot/EFI/limine/limine_x64.efi` still exists on the ESP
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.