Bug 1888730 - Booting with a RAID attached results in mdmonitor failing to start
Summary: Booting with a RAID attached results in mdmonitor failing to start
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lorax
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1888728
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-15 15:38 UTC by Brian Lane
Modified: 2021-03-01 19:33 UTC (History)
5 users (show)

Fixed In Version: lorax-34.4-1
Clone Of: 1888728
Environment:
Last Closed: 2021-03-01 19:33:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Brian Lane 2020-10-15 15:38:02 UTC 
+++ This bug was initially created as a clone of Bug #1888728 +++

The mdmonitor service is disabled on the installer iso, but if there is a RAID attached systemd tries to start it anyway. This results in an error in the logs and on the console.

The system continues to boot, and installation works fine, this is purely cosmetic.

It does not appear with a normally partitioned drive, only with RAID.

We do not want to actually run mdmonitor during installation because it requires an email address to function properly. So it either needs to be removed or masked from being started under any conditions.
Comment 1 Brian Lane 2020-10-30 19:22:17 UTC 
https://github.com/weldr/lorax/pull/1092
Note You need to log in before you can comment on or make changes to this bug.