reccurent RAID issue after reboot

tifab77 · Dec 16th 2020

Hi all,

I had to shutdown my OMV before an power intervention at my place.

I made a clean shutdown of course

After a reboot I was not able to see my RAID 5 on the OMV interface

After a :

$ mdadm --stop /dev/md0

then a :

$mdadm --assemble --force --verbose /dev/md0

I was able to get my RAID back. At first the sde disk was not mounting on the Raid group

To be sure I made a reboot then I got back to the same issue (no RAID displayed)

after the same 2 command that is now ths sda disk that is not mountig in the raid

Here are the required commands and thir output :

Code

$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdb[0] sde[3] sdf[2] sdc[1]
      3906523136 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4] [UUUU_]
      bitmap: 1/8 pages [4KB], 65536KB chunk

$ blkid
/dev/sda: UUID="5bfd32bb-4679-7bac-81fc-d9a85297c17c" UUID_SUB="727fea00-8759-f8c2-1c33-1e123ef5fe81" LABEL="fb-nas-03:RAID01" TYPE="linux_raid_member"
/dev/sdb: UUID="5bfd32bb-4679-7bac-81fc-d9a85297c17c" UUID_SUB="b939ce3e-73d1-a700-2e44-b06039f07810" LABEL="fb-nas-03:RAID01" TYPE="linux_raid_member"
/dev/sde: UUID="5bfd32bb-4679-7bac-81fc-d9a85297c17c" UUID_SUB="774ecad5-1c13-e0ff-0afc-b603e1401996" LABEL="fb-nas-03:RAID01" TYPE="linux_raid_member"
/dev/sdd1: UUID="59bd3370-261c-4d13-8f69-05805bc5d0c7" TYPE="ext4" PARTUUID="88250d03-01"
/dev/sdd5: UUID="22134512-0414-4b90-b204-86e816be664a" TYPE="swap" PARTUUID="88250d03-05"
/dev/sdc: UUID="5bfd32bb-4679-7bac-81fc-d9a85297c17c" UUID_SUB="f3c0d88f-3958-a227-834d-448c8decc07b" LABEL="fb-nas-03:RAID01" TYPE="linux_raid_member"
/dev/sdf: UUID="5bfd32bb-4679-7bac-81fc-d9a85297c17c" UUID_SUB="63201f8e-7ccd-1424-987e-ed6f88050766" LABEL="fb-nas-03:RAID01" TYPE="linux_raid_member"



fdisk -l | grep "Disk "
Disk /dev/sdc: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HGST HTS721010A9
Disk /dev/sdf: 931,5 GiB, 1000203804160 bytes, 1953523055 sectors
Disk model: WDC WD10EZEX-00B
Disk /dev/sdd: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HGST HTS721010A9
Disk /dev/sde: 931,5 GiB, 1000203804160 bytes, 1953523055 sectors
Disk model: HGST HTS721010A9
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HGST HTS721010A9
Disk /dev/sdb: 223,6 GiB, 240056327680 bytes, 468860015 sectors
Disk model: KINGSTON SV300S3
Disk identifier: 0x88250d03
Disk /dev/md0: 3,7 TiB, 4000279691264 bytes, 7813046272 sectors

$ 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 fbouvart@orange.fr
MAILFROM root

# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=fb-nas-03:RAID01 UUID=5bfd32bb:46797bac:81fcd9a8:5297c17c

mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid5 num-devices=5 metadata=1.2 name=fb-nas-03:RAID01 UUID=5bfd32bb:46797bac:81fcd9a8:5297c17c
   devices=/dev/sda,/dev/sdc,/dev/sdd,/dev/sdf

$ mdadm --stop /dev/md0
$ mdadm --assemble --force --verbose /dev/md0
mdadm: looking for devices for /dev/md0
mdadm: No super block found on /dev/sdd5 (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdd5
mdadm: /dev/sdd2 is too small for md: size is 2 sectors.
mdadm: no RAID superblock on /dev/sdd2
mdadm: No super block found on /dev/sdd1 (Expected magic a92b4efc, got 0000041c)
mdadm: no RAID superblock on /dev/sdd1
mdadm: No super block found on /dev/sdd (Expected magic a92b4efc, got cd8e1c7b)
mdadm: no RAID superblock on /dev/sdd
mdadm: /dev/sdf is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdc is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sde is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sdb is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sda is identified as a member of /dev/md0, slot 4.
mdadm: added /dev/sdc to /dev/md0 as 1
mdadm: added /dev/sdf to /dev/md0 as 2
mdadm: added /dev/sde to /dev/md0 as 3
mdadm: failed to add /dev/sda to /dev/md0: Invalid argument
mdadm: added /dev/sdb to /dev/md0 as 0
mdadm: /dev/md0 has been started with 4 drives (out of 5).
root@fb-nas-03:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdb[0] sde[3] sdf[2] sdc[1]
      3906523136 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4] [UUUU_]
      bitmap: 1/8 pages [4KB], 65536KB chunk

unused devices: <none>

Display More

OMV : 5.5.18-1

kernel : 5.5.9.0-0.bpo.2-amd64

Let me know if more detail is needed

Thanks in advance

Fabrice

geaves · Dec 16th 2020

When specifying assemble using this -> mdadm --assemble --force --verbose /dev/md0 add /dev/sd[drive letters in the array]

This -> mdadm: failed to add /dev/sda to /dev/md0: Invalid argument but it doesn't state what that is

Storage -> Disks select sda on the menu click wipe and then short, when complete; Raid Management -> select the raid, on the menu click recover a dialog should display sda select it and it will be added to the array, the raid should rebuild. Come back if there any errors, but it should be OK.

tifab77 · Dec 16th 2020

Thanks,

It helps. I erased sda then readd it to the raid

It is rebuilding

however I hope it won't reappear at next reboot

tifab77 · Dec 17th 2020

after the rebuild I rebooted my OMV and I had no failure

thanks, you brought me the solution

geaves · Dec 17th 2020

Quote from tifab77

I rebooted my OMV and I had no failure

reccurent RAID issue after reboot

tifab77 Dec 16th 2020

Participate now!

Tags