Proof Portal

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-3610GitHub issuePublicReceived

Manual Arch install dual partitions setup - "Boot partition not found"

Reported by Britnell · filed Nov 1, 2025Closed upstream on 2025-11-03. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

Manual Arch install dual partitions setup - "Boot partition not found"revision 1 · captured 2026-10-04 11:42 UTC via poll

What correction or addition do we need?

Hey,

trying to install arch manually in a dual partition i kept on getting error "Boot partition not found"
took me a couple of back and forth to figure it out so wanted to document here, for any one else who hasn't done it before
I found loads of guides all doing it differently, but actually its easy to setup jsut with the installer

manual install

follow instructions

Partitions

in the archinstall > disk > partitioning :
You should have an empty partition available, if not make space and delete / resize another one.
- Manual Partitioning

create a boot partition :
- 1GiB
- fat32
- mountpoint : /boot
- flags : boot, esp
i already had a 100MB boot partition from windows, but arch needs its own separate one

create a linux partiton out of the rest :
-btrfs
- for btrfs i wasn't able to edit mountpoint , but can add subvolumes instead
- create / and /home subvolumes
i once ran arch "suggested partition layout" to see how it would set things up,
and it created two separate ones, it created '/' root with 47GiB , and '/' home with the rest,
but for submodules don't need the size

done

then follow the rest from the manual

View raw text
### What correction or addition do we need?

Hey,

trying to install arch manually in a dual partition i kept on getting error "Boot partition not found"
took me a couple of back and forth to figure it out so wanted to document here, for any one else who hasn't done it before
I found loads of guides all doing it differently, but actually its easy to setup jsut with the installer

## manual install
[follow instructions](https://learn.omacom.io/2/the-omarchy-manual/96/manual-installation)  

## Partitions

in the `archinstall` > disk > partitioning : 
You should have an empty partition available, if not make space and delete / resize another one.
- `Manual Partitioning`

**create a boot partition :** 
-  `1GiB` 
- `fat32` 
- mountpoint : `/boot` 
- flags : `boot, esp`
i already had a 100MB boot partition from windows, but arch needs its own separate one

**create a linux partiton out of the rest :** 
-`btrfs`
- for btrfs i wasn't able to edit mountpoint , but can add `subvolumes` instead
- create  `/`  and `/home` subvolumes
i once ran arch "suggested partition layout" to see how it would set things up, 
and it created two separate ones, it created '/' root with 47GiB , and '/' home with the rest, 
but for submodules don't need the size

## done

then follow the rest from the manual

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.