Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1727GitHub issuePublicDecided· Out of scope

Dual-boot install fails when the free space is on a different disk than Windows itself

Reported by igor-gorohovsky · filed Aug 17, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

Dual-boot install fails when the free space is on a different disk than Windows itselfrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

AMD 5900x, RX9070XT, Omarchy 4.0.0

What's wrong?

Dual-boot install fails when the free space is on a different disk than Windows itself

System details

  • Omarchy: 4.0.0
  • ISO: omarchy-4.0.0.iso, SHA256 verified against the published checksum
  • Boot media: SanDisk 64 GB USB written with balenaEtcher, Secure Boot disabled
  • Machine: two NVMe drives — Samsung SSD 980 PRO 2 TB (data) + a 465.8 GB drive (Windows system)

What I did

I wanted to dual-boot alongside Windows. Following the Quattro release notes, I freed up space for it: I shrank an NTFS volume in Windows Disk Management, leaving ~290 GB of unallocated space. Then I booted the Omarchy ISO and chose the dual-boot install into that free space.

What happened

The installer ran through disk setup, created the LUKS container, the btrfs filesystem and all subvolumes, then died at the last step trying to mount the EFI partition:

mount: /mnt/boot: fsconfig() failed: Can't find a SQUASHFS superblock on nvme0n1p3.
       dmesg(1) may have more information after failed mount system call.
mounting the ESP failed (exit 32)

I managed to install omarchy only on the same physical disk with windows, but in this case I had to copy windows loader to /boot by myself anyway, because there was only omarchy option to choose for booting

Happy to help with any information you need to fix that.

View raw text
### System details

AMD 5900x, RX9070XT, Omarchy 4.0.0

### What's wrong?

# Dual-boot install fails when the free space is on a different disk than Windows itself

## System details

- **Omarchy:** 4.0.0
- **ISO:** `omarchy-4.0.0.iso`, SHA256 verified against the published checksum
- **Boot media:** SanDisk 64 GB USB written with balenaEtcher, Secure Boot disabled
- **Machine:** two NVMe drives — Samsung SSD 980 PRO 2 TB (data) + a 465.8 GB drive (Windows system)

## What I did

I wanted to dual-boot alongside Windows. Following the Quattro release notes, I freed up space for it: I shrank an NTFS volume in Windows Disk Management, leaving ~290 GB of unallocated space. Then I booted the Omarchy ISO and chose the dual-boot install into that free space.

## What happened

The installer ran through disk setup, created the LUKS container, the btrfs filesystem and all subvolumes, then died at the last step trying to mount the EFI partition:

```
mount: /mnt/boot: fsconfig() failed: Can't find a SQUASHFS superblock on nvme0n1p3.
       dmesg(1) may have more information after failed mount system call.
mounting the ESP failed (exit 32)
```

I managed to install omarchy only on the same physical disk with windows, but in this case I had to copy windows loader to /boot by myself anyway, because there was only omarchy option to choose for booting

Happy to help with any information you need to fix that.

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 04:33 UTC