Mdmonitor.service not found

Issues & Assistance
1 
System:
Kernel: 6.16.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=19954613-1c31-4aaa-b314-772fe0e94e44 rw rootflags=subvol=@
quiet loglevel=3
Desktop: KDE Plasma v: 6.4.5 tk: Qt v: N/A info: frameworks v: 6.18.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASRock product: Z790 LiveMixer v: N/A
serial: <superuser required>
Mobo: ASRock model: Z790 LiveMixer serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: 22.02
date: 05/05/2025
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M275/M280
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Device-2: sony_controller_battery_00:32:00:de:73:a1 model: N/A serial: N/A
charge: N/A status: full
CPU:
Info: model: Intel Core i9-14900KF bits: 64 type: MST AMCP arch: Raptor Lake
gen: core 14 level: v3 note: check built: 2022+ process: Intel 7 (10nm)
family: 6 model-id: 0xB7 (183) stepping: 1 microcode: 0x12F
Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2
st: 16 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32
KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
Speed (MHz): avg: 800 min/max: 800/6100:4400 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800
17: 800 18: 800 19: 800 20: 800 21: 800 22: 800 23: 800 24: 800 25: 800
26: 800 27: 800 28: 800 29: 800 30: 800 31: 800 32: 800 bogomips: 203980
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD103 [GeForce RTX 4080] vendor: Gigabyte driver: nvidia
v: 580.82.09 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-08) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1
empty: DP-1,DP-2,DP-3 bus-ID: 01:00.0 chip-ID: 10de:2704 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
display-ID: 0
Monitor-1: HDMI-A-1 model: MSI G321CU built: 2022 res: mode: 3840x2160
hz: 120 scale: 100% (1) dpi: 140 gamma: 1.2 size: 697x392mm (27.44x15.43")
diag: 800mm (31.5") ratio: 16:9 modes: max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.82.09
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4080/PCIe/SSE2
memory: 15.62 GiB display-ID: :1.0
API: Vulkan v: 1.4.321 layers: 11 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 4080 driver: nvidia v: 580.82.09
device-ID: 10de:2704 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.2.2-arch1.2 (LLVM
20.1.8) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: ASRock
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:22bb class-ID: 0403
API: ALSA v: k6.16.7-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 5000 bus-ID: 04:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter
vendor: Lenovo driver: rtl8821ae v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 4000 bus-ID: 05:00.0 chip-ID: 10ec:8821 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek RTL8821A Bluetooth driver: btusb v: 0.8 type: USB rev: 2.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:15 chip-ID: 0bda:0821
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
RAID:
Supported mdraid levels: raid1
Device-1: md0 maj-min: 9:0 type: mdraid level: mirror status: active
size: 2.73 TiB
Info: report: 2/2 UU blocks: 2930134464 chunk-size: N/A super-blocks: 1.2
Components: Online:
0: sdc maj-min: 8:32 size: 2.73 TiB
1: sdd maj-min: 8:48 size: 2.73 TiB
Drives:
Local Storage: total: 22.85 TiB used: 11.48 TiB (50.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Fanxiang model: S880 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: SN17171 temp: 44.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:6 vendor: Crucial model: CT500P3PSSD8
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR40D temp: 40.9 C
scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:5 vendor: TeamGroup
model: T-FORCE TM8FPZ004T size: 3.64 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: EIFM51.3 temp: 38.9 C scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3500418AS
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: CC38 scheme: GPT
ID-5: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST12000NM0127
size: 10.91 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: G006 scheme: GPT
ID-6: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST3000NM0025
size: 2.73 TiB block-size: physical: 512 B logical: 512 B tech: N/A
serial: N/A fw-rev: N003
ID-7: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST3000NM0025
size: 2.73 TiB block-size: physical: 512 B logical: 512 B tech: N/A
serial: N/A fw-rev: N003
ID-8: /dev/sde maj-min: 8:64 vendor: SanDisk model: SanDisk 3.2 Gen1
size: 116.57 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: DL17 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 159.18 GiB size: 159.18 GiB (100.00%)
used: 14.7 GiB (9.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 2.3 MiB (0.4%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 159.18 GiB size: 159.18 GiB (100.00%)
used: 14.7 GiB (9.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-4: /var/log raw-size: 159.18 GiB size: 159.18 GiB (100.00%)
used: 14.7 GiB (9.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-5: /var/tmp raw-size: 159.18 GiB size: 159.18 GiB (100.00%)
used: 14.7 GiB (9.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 46.86 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 35.5 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 48 GiB available: 46.86 GiB used: 3.03 GiB (6.5%)
Processes: 590 Power: uptime: 2m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 18.68 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1934 libs: 546
tools: gnome-software,octopi,paru Compilers: clang: 20.1.8 gcc: 15.2.1
Shell: Bash v: 5.3.3 default: fish v: 4.0.2 running-in: konsole
inxi: 3.3.39
Garuda (2.8.3-2):
System install date:     2025-09-17
Garuda release:          250916
Last full system update: 2025-09-17
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:            mdmonitor.service
--- System Health Check Report ---
23/24 checks run in 1.08 seconds āŒ›
Powered by garuda-health šŸ¦…

--- LOW ---
- Failed systemd services found: mdmonitor.service

i used the latest garuda gaming iso to do a fresh install and had no issues whatsoever apart of the mdmonitor.service not found. Not sure what this means for everything seems to be working.

Excellent job guys!

2

Maybe its better for new help request than ask here in anouncement? @TNE
So we can mark a solution.

5 Likes
3

I think you can start by enabling this service from systemctl.
Check status by typing (do run with sudo!)

sudo systemctl status mdmonitor.service

And if you get anything then you can start with enabling it

sudo systemctl enable mdmonitor.service

Or you can use ā€˜startā€™ in place of ā€˜enableā€™ (if enable doesnā€™t work)

Thatā€™s the only solution I can think of

4

Announcement?

Indication error!

1 Like
5

For status there is no need for sudo, right?

6

Yeah sorry my bad!, but I think for enabling we need it.

7

No luck iā€™m afraid

This is the out put of sudo systemctl status mdmonitor.service

mdmonitor.service - MD array monitorLoaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static)Active: failed (Result: exit-code) since Fri 2025-09-19 01:34:15 AWST; 18s agoDuration: 17msInvocation: 6ae95dc204844838970b62116b3ba670Docs: man:mdadm(8)Main PID: 29432 (code=exited, status=1/FAILURE)Mem peak: 1.7MCPU: 2ms

Sep 19 01:34:15 gerry-runs-wild systemd[1]: Started MD array monitor.Sep 19 01:34:15 gerry-runs-wild mdadm[29432]: mdadm: No mail address or alert command - not monitoring.Sep 19 01:34:15 gerry-runs-wild systemd[1]: mdmonitor.service: Main process exited, code=exited, status=1/FAIL>Sep 19 01:34:15 gerry-runs-wild systemd[1]: mdmonitor.service: Failed with result 'exit-code'. lines 1-14/14 (END)


This is the out come of sudo systemctl enable mdmonitor.service

The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.

Possible reasons for having these kinds of units are:
ā€¢ A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
ā€¢ A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
ā€¢ A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
ā€¢ In case of template units, the unit is meant to be enabled with some
instance name specified.

And this is what i get typing sudo systemctl enable mdmonitor.service

The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.

Possible reasons for having these kinds of units are:
ā€¢ A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
ā€¢ A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
ā€¢ A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
ā€¢ In case of template units, the unit is meant to be enabled with some
instance name specified.
8

maybe you try to reinstall it and reboot .

paru -S mdadm
1 Like
9

[sudo] password for gerry: Ɨ mdmonitor.service - MD array monitor Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static) Active: failed (Result: exit-code) since Fri 2025-09-19 07:06:29 AWST; 26s ago Duration: 22ms Invocation: d9c18ea179404a599bbda0fd6e36b864 Docs: man:mdadm(8) Process: 3973 ExecStart=/sbin/mdadm --monitor --scan (code=exited, status=1/FAILURE) Main PID: 3973 (code=exited, status=1/FAILURE) Mem peak: 2M CPU: 3ms Sep 19 07:06:29 gerry-runs-wild systemd[1]: Started MD array monitor. Sep 19 07:06:29 gerry-runs-wild mdadm[3973]: mdadm: No mail address or alert command - not monitoring. Sep 19 07:06:29 gerry-runs-wild systemd[1]: mdmonitor.service: Main process exited, code=exited, status=1/FAIL> Sep 19 07:06:29 gerry-runs-wild systemd[1]: mdmonitor.service: Failed with result ā€˜exit-codeā€™. lines 1-15/15 (END)

It did not make any difference. Almost as if it is trying to run something that is not there but the 2 drives i got in raid appear to be working fine.

10

Please, change to markdown and it use the correct format for the terminal output. :hugs:

Upper left [M-A]

3 Likes
11

Perhaps the file /etc/mdadm.conf isnā€™t correct.

Wrong uuid or array or no entries
With mdadm --detail /dev/md/0 you see the raid geometry.
Compare it with mdadm.conf and also insert a valid email but not a must and only if example ā€œmailutilsā€ is installed.
If you make a manual intervention there, you must rebuild over dracut the initramfs.

4 Likes
12

Thanks @gampel that solved the issue nicely

1 Like
13

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.