MD array monitor failed to start

astrothug · 27. Oktober 2020

getting this error from cockpit

Code

mdmonitor.service: Failed with result 'exit-code'.systemd
8:57 PM
mdmonitor.service: Main process exited, code=exited, status=1/FAILUREsystemd
8:57 PM
mdadm: No mail address or alert command - not monitoring.

I also cant access omv from my local network, it sees it but will not access.

astrothug · 27. Oktober 2020

Code

cat /proc/mdstat

Zitat

Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md127 : active raid5 sdb[2] sdc[0] sdd[1]
7813772288 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
bitmap: 6/30 pages [24KB], 65536KB chunk
unused devices: <none>

blkid

Zitat

/dev/sdb: UUID="fa533ddb-d7de-8a36-0b45-5088ebd9e296" UUID_SUB="ae4b11c6-4f6d-b494-9261-fb4cded3482c" LABEL="openmediavault.local:media" TYPE="linux_raid_member"
/dev/sda1: UUID="7bc0c265-c68c-44e6-86b6-127dbd6fbbb1" TYPE="ext4" PARTUUID="1c1fd8a9-01"
/dev/sda5: UUID="9138cf45-a0a0-4279-bef8-ac2906acebcc" TYPE="swap" PARTUUID="1c1fd8a9-05"
/dev/sde1: LABEL="VM" UUID="0ce2132a-9e40-47c8-b00b-ff8701d80716" TYPE="ext4" PARTUUID="d76e7f62-45d7-49a4-be89-991294c86cb3"
/dev/sdc: UUID="fa533ddb-d7de-8a36-0b45-5088ebd9e296" UUID_SUB="6f90d2e2-ea4b-1405-7c9d-062e9a93261c" LABEL="openmediavault.local:media" TYPE="linux_raid_member"
/dev/md127: LABEL="media" UUID="d6ffe5d0-f2d3-4d29-ae35-8ced398e467c" TYPE="ext4"
/dev/sdd: UUID="fa533ddb-d7de-8a36-0b45-5088ebd9e296" UUID_SUB="0334dede-95e3-5461-f64d-e032a46f116a" LABEL="openmediavault.local:media" TYPE="linux_raid_member"

Alles anzeigen

fdisk -l | grep "Disk "clear

Code

Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EZRZ-19G
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: ADATA SU655
Disk identifier: 0x1c1fd8a9
Disk /dev/sde: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC WD2500AAKS-0
Disk identifier: C7577FA2-ECFF-495E-B840-C610276A20BF
Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EZRZ-19G
Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EZRZ-19G
Disk /dev/md127: 7.3 TiB, 8001302822912 bytes, 15627544576 sectors
root@openmediavault:~#

Alles anzeigen

cat /etc/mdadm/mdadm.conf

Code

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.


# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# definitions of existing MD arrays
ARRAY /dev/md/media metadata=1.2 name=openmediavault.local:media UUID=fa533ddb:d7de8a36:0b455088:ebd9e296

Alles anzeigen

mdadm --detail --scan --verbose

Code

ARRAY /dev/md/media level=raid5 num-devices=3 metadata=1.2 name=openmediavault.local:media UUID=fa533ddb:d7de8a36:0b455088:ebd9e296
devices=/dev/sdb,/dev/sdc,/dev/sdd

ryecoaaron · 27. Oktober 2020

Your array is fine. What is the output of: sudo journalctl -u mdmonitor.service

astrothug · 27. Oktober 2020

Code

-- Logs begin at Mon 2020-10-26 19:58:32 PDT, end at Tue 2020-10-27 06:56:17 PDT

Oct 26 19:58:32 openmediavault.local systemd[1]: Started MD array monitor.

Oct 26 19:58:32 openmediavault.local mdadm[405]: mdadm: No mail address or alert

Oct 26 19:58:32 openmediavault.local systemd[1]: mdmonitor.service: Main process

Oct 26 19:58:32 openmediavault.local systemd[1]: mdmonitor.service: Failed with

Oct 26 20:57:53 openmediavault.local systemd[1]: Started MD array monitor.

Oct 26 20:57:53 openmediavault.local mdadm[7350]: mdadm: No mail address or aler

Oct 26 20:57:53 openmediavault.local systemd[1]: mdmonitor.service: Main process

Oct 26 20:57:53 openmediavault.local systemd[1]: mdmonitor.service: Failed with

Oct 26 21:17:03 openmediavault.local systemd[1]: Started MD array monitor.

Oct 26 21:17:03 openmediavault.local mdadm[23241]: mdadm: No mail address or ale

Oct 26 21:17:03 openmediavault.local systemd[1]: mdmonitor.service: Main process

Oct 26 21:17:03 openmediavault.local systemd[1]: mdmonitor.service: Failed with

lines 1-13/13 (END)

Alles anzeigen

ryecoaaron · 27. Oktober 2020

Your lines are truncated and I can't see the entire message.

astrothug · 27. Oktober 2020

Code

-- Logs begin at Mon 2020-10-26 19:58:32 PDT, end at Tue 2020-10-27 07:12:22 PDT. --
Oct 26 19:58:32 openmediavault.local systemd[1]: Started MD array monitor.
Oct 26 19:58:32 openmediavault.local mdadm[405]: mdadm: No mail address or alert command - not monitoring.
Oct 26 19:58:32 openmediavault.local systemd[1]: mdmonitor.service: Main process exited, code=exited, status=1/FAILURE
Oct 26 19:58:32 openmediavault.local systemd[1]: mdmonitor.service: Failed with result 'exit-code'.
Oct 26 20:57:53 openmediavault.local systemd[1]: Started MD array monitor.
Oct 26 20:57:53 openmediavault.local mdadm[7350]: mdadm: No mail address or alert command - not monitoring.
Oct 26 20:57:53 openmediavault.local systemd[1]: mdmonitor.service: Main process exited, code=exited, status=1/FAILURE
Oct 26 20:57:53 openmediavault.local systemd[1]: mdmonitor.service: Failed with result 'exit-code'.
Oct 26 21:17:03 openmediavault.local systemd[1]: Started MD array monitor.
Oct 26 21:17:03 openmediavault.local mdadm[23241]: mdadm: No mail address or alert command - not monitoring.
Oct 26 21:17:03 openmediavault.local systemd[1]: mdmonitor.service: Main process exited, code=exited, status=1/FAILURE
Oct 26 21:17:03 openmediavault.local systemd[1]: mdmonitor.service: Failed with result 'exit-code'.
root@openmediavault:~#

Alles anzeigen

ryecoaaron · 27. Oktober 2020

I still can't see the ends of the lines. You need to make your terminal wider before you cut&paste.

astrothug · 27. Oktober 2020

sorry about that.. fixed above

ryecoaaron · 27. Oktober 2020

nevermind. mdmonitor isn't running on my system with a raid array. Once I populated the Notifications section, it starts.

astrothug · 27. Oktober 2020

Zitat von ryecoaaron

nevermind. mdmonitor isn't running on my system with a raid array. Once I populated the Notifications section, it starts.

so for me this means? not understanding thanks

ryecoaaron · 27. Oktober 2020

Zitat von astrothug

so for me this means? not understanding thanks

mdmonitor isn't running because there is no email address set. In order to set the email address, you need to setup notifcations. In the System -> Notification tab, you can set this up. Then either reboot or sudo systemctl start mdmonitor

astrothug · 27. Oktober 2020

ok, no worrie, so i also can see OMV on my network, windows 7 machine can access it, but windows 10 cant, Im glad I was able to figure it out and with your help understand a bit more. thanks for taking the time to help me out.

MD array monitor failed to start

Jetzt mitmachen!

Ähnliche Themen

Unable to use Network UPS Tools to monitor my UPS

Webpage Login issues "Failed to connect to socket: Connection refused:"

simple changes have to be reverted. Timeout change error..

nut plugin with Raspberry Pi Os

OMV 5.0 - finally out! :-)

Tags

Jetzt mitmachen!

Ähnliche Themen

Unable to use Network UPS Tools to monitor my UPS

Webpage Login issues "Failed to connect to socket: Connection refused​:"

simple changes have to be reverted. Timeout change error..

nut plugin with Raspberry Pi Os

OMV 5.0 - finally out! :-)

Tags

Webpage Login issues "Failed to connect to socket: Connection refused:"