Degraded mirror raid is not shown in gui

7ore · 5. Oktober 2022

I shut down my OMV and replaced a disc in one of my mirror raids. The one left there (sda) is a WD red 3TB.

When I restarted that raid (md125) is not shown in the "Software RAID" tab, so I can't add the new disc to the raid.

Code

~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md125 : inactive sda[2](S)
      2930135512 blocks super 1.2

md126 : active raid1 sdc[0] sdb[1]
      2930135360 blocks super 1.2 [2/2] [UU]

md127 : active raid1 sde[2] sdd[3]
      3906887512 blocks super 1.2 [2/2] [UU]

Code

~# blkid
/dev/sda: UUID="0c98e989-12de-39be-be11-9640e4f548e0" UUID_SUB="e2afcfe1-5ec0-1fa9-deaf-18c3ce64b5b4" LABEL="nasse:kangu" TYPE="linux_raid_member"
/dev/sdb: UUID="c38f46f3-382c-20e5-02a9-3b53837294a3" UUID_SUB="02a1daae-2f89-e566-ddae-a4f5180e58da" LABEL="nasse:puh" TYPE="linux_raid_member"
/dev/sdh1: UUID="123bb5a1-1840-4c01-8b7f-0e70c4429816" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2dcc77d4-01"
/dev/sdh5: UUID="1fb4ca6e-b72e-6a1b-a274-4c256505e16f" TYPE="swap" PARTUUID="2dcc77d4-05"
/dev/sdc: UUID="c38f46f3-382c-20e5-02a9-3b53837294a3" UUID_SUB="f1c17f07-a65c-6723-ec83-172221a2f81b" LABEL="nasse:puh" TYPE="linux_raid_member"
/dev/sdf1: UUID="ecd69112-7a50-4b01-b135-5e58697b857e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="bc636c9b-01"
/dev/sdf5: UUID="43f56fdc-7054-4c6c-b8d0-c3896e244977" TYPE="swap" PARTUUID="bc636c9b-05"
/dev/sde: UUID="edb0fb6c-b865-e482-9100-54591f536e48" UUID_SUB="35354ed1-0240-b4e3-3672-4331c1d92f36" LABEL="nasse:ior" TYPE="linux_raid_member"
/dev/sdd: UUID="edb0fb6c-b865-e482-9100-54591f536e48" UUID_SUB="492cfb70-58a5-c3b2-ebb4-ca9723d16ea2" LABEL="nasse:ior" TYPE="linux_raid_member"
/dev/md127: LABEL="ior" UUID="3b3cf06f-6ce6-4ac4-8d3f-a1568af6beec" BLOCK_SIZE="4096" TYPE="ext4"
/dev/md126: LABEL="puh" UUID="b984e9b0-911b-42d4-816b-03a0713696ba" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdg1: PARTLABEL="Microsoft reserved partition" PARTUUID="af413473-f79a-4be6-b5a8-becdc217f5d6"

Alles anzeigen

Code

~# fdisk -l | grep "Disk "
Partition 1 does not start on physical sector boundary.
Disk /dev/sda: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Disk /dev/sdb: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Disk /dev/sdh: 298.09 GiB, 320072933376 bytes, 625142448 sectors
Disk model: HITACHI HTS72503
Disk identifier: 0x2dcc77d4
Disk /dev/sdc: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EZRX-00D
Disk /dev/sdf: 74.53 GiB, 80026361856 bytes, 156301488 sectors
Disk model: INTEL SSDSA2M080
Disk identifier: 0xbc636c9b
Disk /dev/sde: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000NE001-2MA1
Disk /dev/sdg: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000VN0033-2EE
Disk identifier: E0670AC1-2154-4BA0-8C5E-E8AAB3487428
Disk /dev/sdd: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000NE001-2MA1
Disk /dev/md127: 3.64 TiB, 4000652812288 bytes, 7813775024 sectors
Disk /dev/md126: 2.73 TiB, 3000458608640 bytes, 5860270720 sectors

Alles anzeigen

Code

~# 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>

Alles anzeigen

Code

~# mdadm --detail --scan --verbose
ARRAY /dev/md/ior level=raid1 num-devices=2 metadata=1.2 name=nasse:ior UUID=edb0fb6c:b865e482:91005459:1f536e48
   devices=/dev/sdd,/dev/sde
ARRAY /dev/md/puh level=raid1 num-devices=2 metadata=1.2 name=nasse:puh UUID=c38f46f3:382c20e5:02a93b53:837294a3
   devices=/dev/sdb,/dev/sdc
INACTIVE-ARRAY /dev/md125 num-devices=1 metadata=1.2 name=nasse:kangu UUID=0c98e989:12de39be:be119640:e4f548e0
   devices=/dev/sda

geaves · 5. Oktober 2022

Zitat von 7ore

I shut down my OMV and replaced a disc in one of my mirror raids

mdadm is not hot swap the drive has to be failed then removed from the mdadm array before a new/replacement drive can be added, hence the array is currently inactive.

Zitat von 7ore

cat /etc/mdadm/mdadm.conf

the output of the above is odd, these arrays appear not to have been created using omv's gui, what hardware are you using

7ore · 5. Oktober 2022

OK, thanks, So I will readd the old one again, mark it as failed and then redo it.

It was created in the gui, but with OMV version 2 or possible version 4.

geaves · 5. Oktober 2022

Zitat von 7ore

It was created in the gui, but with OMV version 2 or possible version 4

either way omv writes the array to the mdadm configuration file, yours is blank contains no information on the arrays

7ore · 5. Oktober 2022

I created the raids in older versions and did a clean install with omv 6 and I do not remember if I just connected the drives or if I had to add them in the GUI.

Can I make omv create the mdadm config correctly?

geaves · 5. Oktober 2022

Once you have that array fully synced with the new drive you could try;

omv-salt deploy run mdadm then

update-initramfs -u

Degraded mirror raid is not shown in gui

7ore 6. Oktober 2022

Jetzt mitmachen!