Status failed Service mountpoint

BF0911 · 15. April 2020

Hi there, yesterday we had a power cut. Since then I always get the error message "Status failed Service mountpoint_srv_dev-disk-by-label-data" by email. Furthermore, the error message in the appendix comes when booting. Unfortunately I can not do much with it and hope that someone can help me here.

Sorry for the bad english.

BF0911 · 16. April 2020

Code: cat /proc/mdstat

mdadm: Unknown keyword /dev/md127
ARRAY /dev/md127 level=raid0 num-devices=2 metadata=1.2 name=openmediavault:Raid UUID=cfdd4fab:745a46e8:f4b8f199:3042e20a
   devices=/dev/sda,/dev/sdb
root@OMV:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sda[0] sdb[1]
      2441638400 blocks super 1.2

Code: blkid

 blkid
/dev/sda: UUID="cfdd4fab-745a-46e8-f4b8-f1993042e20a" UUID_SUB="5565b2f5-0bab-ed98-fe94-10aa5c08006c" LABEL="openmediavault:Raid" TYPE="linux_raid_member"
/dev/sdb: UUID="cfdd4fab-745a-46e8-f4b8-f1993042e20a" UUID_SUB="86a24492-a3c3-07dc-0743-634a99861a36" LABEL="openmediavault:Raid" TYPE="linux_raid_member"
/dev/sdc1: UUID="a0e549b7-7791-481e-b3af-8958e1e95af3" TYPE="ext4" PARTUUID="9ca61718-01"
/dev/sdc5: UUID="5748ab9b-3f02-44ed-8e84-f8d08d0fe1ee" TYPE="swap" PARTUUID="9ca61718-05"

Code: fdisk -l | grep "Disk "

The primary GPT table is corrupt, but the backup appears OK, so that will be used.
The primary GPT table is corrupt, but the backup appears OK, so that will be used.
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 380783D3-04A5-4CCF-903A-EEFDB740CF31
Disk /dev/sdb: 1,4 TiB, 1500301910016 bytes, 2930277168 sectors
Disk identifier: D7A416CF-8294-481D-A2B8-1C1751FA425A
Disk /dev/sdc: 55,9 GiB, 60022480896 bytes, 117231408 sectors
Disk identifier: 0x9ca61718

Code: cat /etc/mdadm/mdadm.conf

# 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
/dev/md127 metadata=1.2 name=openmediavault:Raid UUID=cfdd4fab:745a46e8:f4b8f199:3042e20a

# instruct the monitoring daemon where to send mail alerts
MAILADDR xxx
MAILFROM root

Alles anzeigen

Code: mdadm --detail --scan --verbose

ARRAY /dev/md127 level=raid0 num-devices=2 metadata=1.2 name=openmediavault:Raid UUID=cfdd4fab:745a46e8:f4b8f199:3042e20a
   devices=/dev/sda,/dev/sdb

geaves · 16. April 2020

It's inactive;

mdadm --stop /dev/md127

mdadm --assemble --force --verbose /dev/md127 /dev/sd[ab]

then I would run fsck /dev/md127 and you're using mismatched drives for this raid

Status failed Service mountpoint

BF0911 16. April 2020

Jetzt mitmachen!

Ähnliche Themen

Status failed Service mountpoint

OMV freezing at random

Repeating error in syslog

Filesystem devices are missing after upgrade to OMV 4

Invalid RPC response -Kein Filesystem über GUI wählbar