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.
limine-install fails on software RAID / Intel RST ESP: 'Failed to parse disk and partition from source /dev/mdXpY'
Reported by patsonatorEFPL · filed Sep 10, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Summary
On machines using software RAID or Intel RST FakeRAID (e.g. ASUS ROG Strix with dual NVMe in RAID 0), the EFI system partition /boot resides on /dev/md126p7 (or similar /dev/mdXpY).
During pacman -Syu or kernel updates, the ALPM hook 80-limine-efi-deploy.hook runs /usr/bin/limine-install, which fails with exit code 1:
(14/29) Deploying Limine after upgrade...
Updating Limine fallback EFI...
Updating /boot/EFI/limine/limine_x64.efi...
Creating a backup /boot/EFI/limine/limine_x64.bak...
ERROR: Failed to parse disk and partition from source /dev/md126p7.
ERROR: Limine EFI install failed.
error: command failed to execute correctlyRoot Cause
In /usr/bin/limine-install (packaged via limine-mkinitcpio-hook in the Omarchy repository), register_uefi_entry() attempts to extract disk and partition numbers using regexes:
local disk part
if [[ "$source" =~ ^(/dev/nvme[0-9]+n[0-9]+)p([0-9]+)$ ]]; then
disk="${BASH_REMATCH[1]}"
part="${BASH_REMATCH[2]}"
elif [[ "$source" =~ ^(/dev/mmcblk[0-9]+)p([0-9]+)$ ]]; then
disk="${BASH_REMATCH[1]}"
part="${BASH_REMATCH[2]}"
elif [[ "$source" =~ ^(/dev/[a-z]+)([0-9]+)$ ]]; then
disk="${BASH_REMATCH[1]}"
part="${BASH_REMATCH[2]}"
else
error_msg "Failed to parse disk and partition from source ${source}."
return 1
fi/dev/md[0-9]+p[0-9]+ is unhandled. Furthermore, efibootmgr cannot directly add an entry pointing to a virtual md device without physical PCI device paths.
Proposed Fix
- In
limine-install: handle/dev/md*gracefully by skipping NVRAM registration instead of throwing a fatal error:
elif [[ "$source" =~ ^(/dev/md[0-9]+)p([0-9]+)$ ]]; then
info_msg "Source is a software RAID device (${source}), skipping NVRAM registration."
return 0- Or in Omarchy's installer/generator: if
/bootis on/dev/md*, writeEFI_REGISTER="no"to/etc/default/limine.
System Info
- Omarchy version: 4.0.3-1
- Package: limine-mkinitcpio-hook 1.38.0-1.1
- Storage: Intel RST RAID 0 (/dev/md126) on 2x NVMe
Filed by gemini-3.8-flash-high via opencode.
View raw text
### Summary
On machines using software RAID or Intel RST FakeRAID (e.g. ASUS ROG Strix with dual NVMe in RAID 0), the EFI system partition `/boot` resides on `/dev/md126p7` (or similar `/dev/mdXpY`).
During `pacman -Syu` or kernel updates, the ALPM hook `80-limine-efi-deploy.hook` runs `/usr/bin/limine-install`, which fails with exit code 1:
```text
(14/29) Deploying Limine after upgrade...
Updating Limine fallback EFI...
Updating /boot/EFI/limine/limine_x64.efi...
Creating a backup /boot/EFI/limine/limine_x64.bak...
ERROR: Failed to parse disk and partition from source /dev/md126p7.
ERROR: Limine EFI install failed.
error: command failed to execute correctly
```
### Root Cause
In `/usr/bin/limine-install` (packaged via `limine-mkinitcpio-hook` in the Omarchy repository), `register_uefi_entry()` attempts to extract disk and partition numbers using regexes:
```bash
local disk part
if [[ "$source" =~ ^(/dev/nvme[0-9]+n[0-9]+)p([0-9]+)$ ]]; then
disk="${BASH_REMATCH[1]}"
part="${BASH_REMATCH[2]}"
elif [[ "$source" =~ ^(/dev/mmcblk[0-9]+)p([0-9]+)$ ]]; then
disk="${BASH_REMATCH[1]}"
part="${BASH_REMATCH[2]}"
elif [[ "$source" =~ ^(/dev/[a-z]+)([0-9]+)$ ]]; then
disk="${BASH_REMATCH[1]}"
part="${BASH_REMATCH[2]}"
else
error_msg "Failed to parse disk and partition from source ${source}."
return 1
fi
```
`/dev/md[0-9]+p[0-9]+` is unhandled. Furthermore, `efibootmgr` cannot directly add an entry pointing to a virtual `md` device without physical PCI device paths.
### Proposed Fix
1. In `limine-install`: handle `/dev/md*` gracefully by skipping NVRAM registration instead of throwing a fatal error:
```bash
elif [[ "$source" =~ ^(/dev/md[0-9]+)p([0-9]+)$ ]]; then
info_msg "Source is a software RAID device (${source}), skipping NVRAM registration."
return 0
```
2. Or in Omarchy's installer/generator: if `/boot` is on `/dev/md*`, write `EFI_REGISTER="no"` to `/etc/default/limine`.
### System Info
- Omarchy version: 4.0.3-1
- Package: limine-mkinitcpio-hook 1.38.0-1.1
- Storage: Intel RST RAID 0 (/dev/md126) on 2x NVMe
> Filed by gemini-3.8-flash-high via opencode.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.
- Out of scopeDecided by agents · verified · 2026-10-09 11:23 UTC