Mirror RAID clean, degraded

chuvihi · 24. August 2021

Hi,

I have an issue with my Mirror RAID in my OMV. Yesterday I've turned off my NAS for cleaning (unmount components and mount same components) and after switch on again my Raid showed "clean, degraded"

Here you have the diagnostics information.

Can anybody help me to make it working again without loosing data? Many thanks.

Regards

Code

root@HomeServer:/# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sde[1]
      3906886464 blocks super 1.2 [2/1] [_U]
      bitmap: 4/30 pages [16KB], 65536KB chunk

md0 : active raid1 sdb[0] sdc[1]
      976630464 blocks super 1.2 [2/2] [UU]
      bitmap: 0/8 pages [0KB], 65536KB chunk

unused devices: <none>

Alles anzeigen

Code

root@HomeServer:/# blkid
/dev/sda1: UUID="cf057b4b-196a-4511-a1ae-45915e651744" TYPE="ext4" PARTUUID="e7fde74e-01"
/dev/sda3: UUID="2becb76c-39af-43a5-b063-cc748f2d8c74" TYPE="ext4" PARTUUID="e7fde74e-03"
/dev/sda5: UUID="4ec3d4e7-2f6e-4b9a-af46-a5375533a86f" TYPE="swap" PARTUUID="e7fde74e-05"
/dev/sdc: UUID="55ac50b0-8102-38a7-a271-0cd53a47d01a" UUID_SUB="393688b4-4bc9-3a04-a08d-a8a08cc5dc69" LABEL="Disc1" TYPE="linux_raid_member"
/dev/sdb: UUID="55ac50b0-8102-38a7-a271-0cd53a47d01a" UUID_SUB="c84c50dc-15df-e8b8-2674-663a4ad3a417" LABEL="Disc1" TYPE="linux_raid_member"
/dev/md0: UUID="fd18ffbc-1f40-4140-b3be-c1ce934b45b6" TYPE="ext4"
/dev/sde: UUID="bceb274f-3cd4-e33b-dbed-b70b859b4f3d" UUID_SUB="4ac6a8ff-9032-89f2-ed3f-b79765ffffe0" LABEL="Raid4TB1" TYPE="linux_raid_member"
/dev/md1: UUID="225ca463-d0e3-4ec6-9f6d-b0479d1ed760" TYPE="ext4"
/dev/sdf: UUID="bceb274f-3cd4-e33b-dbed-b70b859b4f3d" UUID_SUB="819e5033-ee4c-a3b8-ed1e-c2352e6feec2" LABEL="Raid4TB1" TYPE="linux_raid_member"

Code

root@HomeServer:/# fdisk -l | grep "Disk "
Partition 2 does not start on physical sector boundary.Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500LM000-1EJ16
Disk identifier: 0xe7fde74e

Disk /dev/sdc: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00B
Disk /dev/sdb: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EFRX-68J
Disk /dev/sde: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EFAX-68J
Disk /dev/md0: 931,4 GiB, 1000069595136 bytes, 1953260928 sectors
Disk /dev/md1: 3,7 TiB, 4000651739136 bytes, 7813772928 sectors
Disk /dev/sdf: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EFAX-68J

Alles anzeigen

Code

root@HomeServer:/# 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>

# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=Disc1 UUID=55ac50b0:810238a7:a2710cd5:3a47d01a
ARRAY /dev/md1 metadata=1.2 name=Raid4TB1 UUID=bceb274f:3cd4e33b:dbedb70b:859b4f3d
root@HomeServer:/# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=1.2 name=Disc1 UUID=55ac50b0:810238a7:a2710cd5:3a47d01a
   devices=/dev/sdb,/dev/sdc
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=1.2 name=Raid4TB1 UUID=bceb274f:3cd4e33b:dbedb70b:859b4f3d
   devices=/dev/sde

Alles anzeigen

Code

root@HomeServer:/# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=1.2 name=Disc1 UUID=55ac50b0:810238a7:a2710cd5:3a47d01a
   devices=/dev/sdb,/dev/sdc
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=1.2 name=Raid4TB1 UUID=bceb274f:3cd4e33b:dbedb70b:859b4f3d
   devices=/dev/sde

ananas · 24. August 2021

mdadm --add /dev/md1 /dev/sdf

Should add the missing drive to the array md1

chuvihi · 24. August 2021

Solved!!!

Thank you ananas!!!

Many thank for your help!!!

chuvihi · 25. September 2021

Hi all,

Many thanks for your help. This is solving me the issue every time I have it. I don't know why, every time I switch off the OMV, the RAID is degraded and I need to add again the missing drive to the array.

Does'nt matter if I switch off the system from the OMV GUI, when I start it back, is showing me RAID clean, degraded.

Anyone has happened the same?

I have two raids in my OMV system, but this is only happening to the same RAID. The other one is working ok.

chuvihi · 29. September 2021

Hi All again,

just happened yesterday what I was saying and now I cannot re-add the missing disk to the raid.

Please see below the messages:

Code

root@HomeServer:/# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [ra                                                id10]
md1 : active raid1 sde[1] sdd[0](F)
      3906886464 blocks super 1.2 [2/1] [_U]
      bitmap: 6/30 pages [24KB], 65536KB chunk

md0 : active raid1 sdc[1] sdb[0]
      976630464 blocks super 1.2 [2/2] [UU]
      bitmap: 0/8 pages [0KB], 65536KB chunk

unused devices: <none>

Alles anzeigen

Code

root@HomeServer:/# blkid
/dev/sda1: UUID="cf057b4b-196a-4511-a1ae-45915e651744" TYPE="ext4" PARTUUID="e7f                                                de74e-01"
/dev/sda3: UUID="2becb76c-39af-43a5-b063-cc748f2d8c74" TYPE="ext4" PARTUUID="e7f                                                de74e-03"
/dev/sda5: UUID="4ec3d4e7-2f6e-4b9a-af46-a5375533a86f" TYPE="swap" PARTUUID="e7f                                                de74e-05"
/dev/sdc: UUID="55ac50b0-8102-38a7-a271-0cd53a47d01a" UUID_SUB="393688b4-4bc9-3a                                                04-a08d-a8a08cc5dc69" LABEL="Disc1" TYPE="linux_raid_member"
/dev/sdb: UUID="55ac50b0-8102-38a7-a271-0cd53a47d01a" UUID_SUB="c84c50dc-15df-e8                                                b8-2674-663a4ad3a417" LABEL="Disc1" TYPE="linux_raid_member"
/dev/sde: UUID="bceb274f-3cd4-e33b-dbed-b70b859b4f3d" UUID_SUB="4ac6a8ff-9032-89                                                f2-ed3f-b79765ffffe0" LABEL="Raid4TB1" TYPE="linux_raid_member"
/dev/md0: UUID="fd18ffbc-1f40-4140-b3be-c1ce934b45b6" TYPE="ext4"
/dev/sdd: UUID="bceb274f-3cd4-e33b-dbed-b70b859b4f3d" UUID_SUB="819e5033-ee4c-a3                                                b8-ed1e-c2352e6feec2" LABEL="Raid4TB1" TYPE="linux_raid_member"
/dev/md1: UUID="225ca463-d0e3-4ec6-9f6d-b0479d1ed760" TYPE="ext4"

Code

root@HomeServer:/# fdisk -l | grep "Disk "
Partition 2 does not start on physical sector boundary.Disk /dev/sda: 465,8 GiB,                                                 500107862016 bytes, 976773168 sectors
Disk model: ST500LM000-1EJ16
Disk identifier: 0xe7fde74e

Disk /dev/sdc: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00B
Disk /dev/sdb: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EFRX-68J
Disk /dev/sde: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EFAX-68J
Disk /dev/sdd: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EFAX-68J
Disk /dev/md0: 931,4 GiB, 1000069595136 bytes, 1953260928 sectors
Disk /dev/md1: 3,7 TiB, 4000651739136 bytes, 7813772928 sectors

Alles anzeigen

Code

root@HomeServer:/# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=1.2 name=Disc1 UUID=55ac50b0:810238a7:a2710cd5:3a47d01a
   devices=/dev/sdb,/dev/sdc
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=1.2 name=Raid4TB1 UUID=bceb274f:3cd4e33b:dbedb70b:859b4f3d
   devices=/dev/sdd,/dev/sde

And when I try to re-add the disk /dev/sdd

Code

root@HomeServer:/# mdadm --add /dev/md1 /dev/sdd
mdadm: Cannot open /dev/sdd: Device or resource busy

Can anyone help me and avoid this happen again? Everytime I turn off /restart the OMV this happen to me.

Many thanks.

Regards,

Mirror RAID clean, degraded

Jetzt mitmachen!

Ähnliche Themen

Missing Data on Raid1 RPi

RAID showing clean, degraded