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

Upgrade to omarchy 3.4.0 broke mdadm raid

Reported by med502 · filed Feb 27, 2026Closed upstream on 2026-02-27. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
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

Upgrade to omarchy 3.4.0 broke mdadm raidrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Omarchy 3.4.0

What's wrong?

Not sure if this is release issue or kernel upgrade issue.
After upgrade my system crashed on kernel panic due to raid timing out.

Looks like md_mod module was no longer loaded at boot which made mdadm unusable.
Maybe below steps will help someone

Steps I made to fix and find issue

  1. Logged as root to recovery mode
  2. Commented out raid entries in /etc/fstab
  3. Reboot and logged into system normally

I tried to re-assemble raid 

sudo mdadm --assemble --scan

which failed with 

mdadm: Can't open /sys/module/md_mod/parameters/legacy_async_del_gendisk
mdadm: init md module parameters fail
mdadm: No arrays found in config file or automatically
  1. Changed config /etc/mkinitcpio.conf

by removing nvidia modules (I had Nvidia card but switched to AMD few months ago)
uncommenting module for mdadm
5. ran ``mkinitcpio -v -p linux`` which failed with

Using default configuration file: '/etc/mkinitcpio.conf' -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
ERROR: Invalid option -g -- '/boot/initramfs-linux-fallback.img' must be writable

I had to do this to fix it 

> pacman -Rscn linux # Probably not necessary, but I did it out of habit.
> rm /etc/mkinitcpio.d/linux.preset.pacsave
> pacman -Syu linux
> mv /etc/mkinitcpio.conf.bak /etc/mkinitcpio.conf
> mkinitcpio -p linux

source https://bbs.archlinux.org/viewtopic.php?pid=1925244#p1925244

6.Commadn to fix missing module

echo "md_mod" | sudo tee /etc/modules-load.d/md_mod.conf
  1. mdamd started working and I could re-assemble raid and uncomment raid entry in /etc/fstab
  2. ``systemctl daemon-reload`` to load module
  3. sudo ``mount -a`` to mount

--- formating edit

View raw text
### System details

Omarchy 3.4.0

### What's wrong?

Not sure if this is release issue or kernel upgrade issue.
After upgrade my system crashed on kernel panic due to raid timing out.

Looks like md_mod module was no longer loaded at boot which made mdadm unusable.
Maybe below steps will help someone

Steps I made to fix and find issue 

1. Logged as root to recovery mode
2. Commented out raid entries in /etc/fstab
3. Reboot and logged into system normally
I tried to re-assemble raid 
```
sudo mdadm --assemble --scan
```
which failed with 
```
mdadm: Can't open /sys/module/md_mod/parameters/legacy_async_del_gendisk
mdadm: init md module parameters fail
mdadm: No arrays found in config file or automatically
```
4. Changed config /etc/mkinitcpio.conf
by removing nvidia modules (I had Nvidia card but switched to AMD few months ago)
uncommenting module for mdadm
5. ran ```mkinitcpio -v -p linux``` which failed with
```
Using default configuration file: '/etc/mkinitcpio.conf' -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
ERROR: Invalid option -g -- '/boot/initramfs-linux-fallback.img' must be writable
```

I had to do this to fix it 
```cp /etc/mkinitcpio.conf /etc/mkinitcpio.conf.bak
> pacman -Rscn linux # Probably not necessary, but I did it out of habit.
> rm /etc/mkinitcpio.d/linux.preset.pacsave
> pacman -Syu linux
> mv /etc/mkinitcpio.conf.bak /etc/mkinitcpio.conf
> mkinitcpio -p linux
```
source https://bbs.archlinux.org/viewtopic.php?pid=1925244#p1925244

6.Commadn to fix missing module
```
echo "md_mod" | sudo tee /etc/modules-load.d/md_mod.conf
```

7. mdamd started working and I could re-assemble raid and uncomment raid entry in /etc/fstab
8. ```systemctl daemon-reload``` to load module
9. sudo ```mount -a``` to mount 

--- formating edit

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.