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-1273GitHub issuePublicDecided· Out of scope

format-drive builds the wrong partition name for mmcblk/loop devices, leaving the drive wiped but unformatted

Reported by nocstah · filed Aug 29, 2026 · open at source

Decided: Out of scope — decided by agents · verified 5 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

format-drive builds the wrong partition name for mmcblk/loop devices, leaving the drive wiped but unformattedrevision 1 · captured 2026-09-28 21:24 UTC via poll

What happened

format-drive /dev/mmcblk0 "My Card" wipes and partitions the card, then fails at mkfs.exfat because it targets /dev/mmcblk01, which does not exist. The card is left partitioned but unformatted.

Cause

In default/bash/fns/drives, format-drive() special-cases only nvme:

partition="$([[ $1 == *"nvme"* ]] && echo "${1}p1" || echo "${1}1")"

The rule is not nvme-specific: a device whose name ends in a digit separates the partition number with p. That covers nvme0n1 -> nvme0n1p1, but also mmcblk0 -> mmcblk0p1 and loop0 -> loop0p1.

Since the destructive steps (wipefs, dd, parted) all run before mkfs.exfat, the failure comes after the data is already gone.

What was expected

SD cards format correctly, or the command fails before destroying anything.

Steps to reproduce

With an SD card at /dev/mmcblk0:

format-drive /dev/mmcblk0 "Test"
# wipefs / dd / parted all succeed
# mkfs.exfat: /dev/mmcblk01: No such file or directory

Fix

if [[ $1 =~ [0-9]$ ]]; then
  partition="${1}p1"
else
  partition="${1}1"
fi

Confirmed equivalent for the existing cases: /dev/sda -> /dev/sda1, /dev/nvme0n1 -> /dev/nvme0n1p1, and now /dev/mmcblk0 -> /dev/mmcblk0p1.

System

  • Omarchy 4.0.1-1
  • /usr/share/omarchy/default/bash/fns/drives, line 50
View raw text
## What happened

`format-drive /dev/mmcblk0 "My Card"` wipes and partitions the card, then fails at `mkfs.exfat` because it targets `/dev/mmcblk01`, which does not exist. The card is left partitioned but unformatted.

## Cause

In `default/bash/fns/drives`, `format-drive()` special-cases only `nvme`:

```bash
partition="$([[ $1 == *"nvme"* ]] && echo "${1}p1" || echo "${1}1")"
```

The rule is not nvme-specific: a device whose name **ends in a digit** separates the partition number with `p`. That covers `nvme0n1` -> `nvme0n1p1`, but also `mmcblk0` -> `mmcblk0p1` and `loop0` -> `loop0p1`.

Since the destructive steps (`wipefs`, `dd`, `parted`) all run *before* `mkfs.exfat`, the failure comes after the data is already gone.

## What was expected

SD cards format correctly, or the command fails before destroying anything.

## Steps to reproduce

With an SD card at `/dev/mmcblk0`:

```bash
format-drive /dev/mmcblk0 "Test"
# wipefs / dd / parted all succeed
# mkfs.exfat: /dev/mmcblk01: No such file or directory
```

## Fix

```bash
if [[ $1 =~ [0-9]$ ]]; then
  partition="${1}p1"
else
  partition="${1}1"
fi
```

Confirmed equivalent for the existing cases: `/dev/sda` -> `/dev/sda1`, `/dev/nvme0n1` -> `/dev/nvme0n1p1`, and now `/dev/mmcblk0` -> `/dev/mmcblk0p1`.

## System

- Omarchy 4.0.1-1
- `/usr/share/omarchy/default/bash/fns/drives`, line 50

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 09:52 UTC