Hi,
Always grateful for your help here... I was doing so well...
We had a power cut the other night and my UPS didn't last long enough to catch things...
Now my RAID seems to be in trouble. By email I'm getting: (Zulu is the name of my RAID...)
Code
The system monitoring needs your attention.
Host: \openmediavault.local
Date: Wed, 07 Apr 2021 08:52:04
Service: filesystem_srv_dev-disk-by-label-zulu
Event: Does not exist
Description: unable to read filesystem '/srv/dev-disk-by-label-zulu' state
and
Code
The system monitoring needs your attention.
Host: \openmediavault.local
Date: Wed, 07 Apr 2021 08:52:35
Service: mountpoint_srv_dev-disk-by-label-zulu
Event: Status failed
Description: status failed (1) -- /srv/dev-disk-by-label-zulu is not a mountpoint
This triggered the monitoring system to: alert
Other info:
Code
root@openmediavault:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : inactive sda[4](S) sdc[2](S) sdb[1](S)
5860147464 blocks super 1.2
unused devices: <none>
Code
root@openmediavault:~# blkid
/dev/sdb: UUID="e722afd9-5803-5460-ce00-e63017883000" UUID_SUB="5667c0d5-4cec-a644-36a3-e641ec176a46" LABEL="openmediavault.local:zulu" TYPE="linux_raid_member"
/dev/sda: UUID="e722afd9-5803-5460-ce00-e63017883000" UUID_SUB="acaec5ef-d304-a129-3754-9605267dcbdf" LABEL="openmediavault.local:zulu" TYPE="linux_raid_member"
/dev/sde1: UUID="173d1141-65e9-4ee1-ae31-b73d34f7b2cf" TYPE="ext4" PARTUUID="9d8e1096-01"
/dev/sde5: UUID="6947d5ca-f259-4fe7-be54-5b945620213c" TYPE="swap" PARTUUID="9d8e1096-05"
/dev/sdc: UUID="e722afd9-5803-5460-ce00-e63017883000" UUID_SUB="d49ed9a5-6400-f405-ea4d-0601f2e60642" LABEL="openmediavault.local:zulu" TYPE="linux_raid_member"
/dev/sdf1: LABEL="Backup" UUID="83ed8d9d-e2f7-4e64-bfc8-8fe26f404112" TYPE="ext4" PARTUUID="4f80a638-fd4a-44e9-851a-3c9575507f12"
Code
root@openmediavault:~# fdisk -l | grep "Disk "
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HDS72302
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: TOSHIBA HDWD120
Disk /dev/sde: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: CT120BX500SSD1
Disk identifier: 0x9d8e1096
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EARS-00M
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: SAMSUNG HD204UI
Disk /dev/sdf: 5.5 TiB, 6001175125504 bytes, 11721045167 sectors
Disk model: Expansion Desk
Disk identifier: B27D326A-00A1-47B0-B2D5-732A08CA3BEA
Alles anzeigen
Code
root@openmediavault:~# cat /etc/mdadm/mdadm.conf
# 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>
# instruct the monitoring daemon where to send mail alerts
MAILADDR omv@xx.co.uk
MAILFROM root
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 spares=0 name=openmediavault.local:zulu UUID=e722afd9:58035460:ce00e630:17883000
Alles anzeigen
Code
root@openmediavault:~# mdadm --detail --scan --verbose
INACTIVE-ARRAY /dev/md0 num-devices=3 metadata=1.2 name=openmediavault.local:zulu UUID=e722afd9:58035460:ce00e630:17883000
devices=/dev/sda,/dev/sdb,/dev/sdc
Code
root@openmediavault:~# mdadm --stop /dev/md0
mdadm: stopped /dev/md0
root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[bcd]
mdadm: looking for devices for /dev/md0
mdadm: Cannot read superblock on /dev/sdd
mdadm: no RAID superblock on /dev/sdd
mdadm: /dev/sdd has no superblock - assembly aborted
The section above was how I rebuilt things last time but it's not responding in this case. One disk seems to be struggling as it has a red marker next to it in the SMART section of OMV but surely the RAID should still function, albeit in a degraded state? Do I have several issues at once, not just the failing HD?
How can I get things back on a solid footing?
S