Arch Linux

H2R

Member

Registered: 2021-11-13

Posts: 13

Software RAID Setup Failing on Boot

So I have a software RAID 1 setup with 2 nvme drives. Usually the machine boots fine, but suddenly I've run into issues where /boot isn't mounting. The workaround is adding `MAILADDR root` to mdadm.conf,  but I wan't to understand why mdadm is failing.

The first error I see in the journal is the `mdmonitor` service failing. `boot.mount` and `mdmonitor.service` are the failed units. The error I get is the following, seeming related to this issue:

Executable /usr/lib/mdadm/mdadm_env.sh missing, skipping: No such file or directory

I don't know why this error suddenly happens, because from my understanding `mdadm_env.sh` is not strictly necessary.

EDIT: changed raid-z2 to RAID 1

Last edited by H2R (2023-06-29 08:25:55)

-thc

Member

Registered: 2017-03-15

Posts: 734

Re: Software RAID Setup Failing on Boot

AKAIK the level "RAID-Z2" is equivalent to "RAID6" and protects against the failure of two drives at the same time - which makes no sense with only two NVMe drives.

H2R

Member

Registered: 2021-11-13

Posts: 13

Re: Software RAID Setup Failing on Boot

Not sure why I said raid-z2, it's just a plain RAID mirror. I think the error is irrespective of the RAID type, however, and rather a package configuration issue.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,031

Re: Software RAID Setup Failing on Boot

It could be a timing issue, but mdadm_env.sh doesn't appear to exist in the archlinux mdadm package .
A search finds archlinux forum threads that mention it but none of them are recent.

Output of

$ pacman -Qo /usr/lib/mdadm/mdadm_env.sh
$ pacman -Qikk mdadm

?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky