1 of 4 HHD´s missed

harwey01 · 4. Mai 2023

Hi community,

in my RAID configuration I see only 3 out of 4 disks.

But there are 4 disks installed and listed in the file system too.

Actually the drives sdb; sdc; sdd; sde should be part of the raid group. Listed here are only sdb; sdc; sdd. Is this normal or what did I do wrong.

I should mention that I had previously installed OMV 4.x and now have reinstalled OMV 6.x on sda.

I am not sure if this is normal or not.I can not expand the raid because this option is grayed out.

In Picture RAID-IV I can´t select any Drive cause it is no drive displayed.

Translated with http://www.DeepL.com/Translator (free version)

forum.openmediavault.org/wsc/index.php?attachment/29826/

geaves · 4. Mai 2023

Zitat von harwey01

But there are 4 disks installed and listed in the file system too

There might be 4 drives installed but they should not be listed in filesystem, storage -> disks yes

What appears to be an image of mdadm --detail one of the drives has been removed, suggesting it's been removed by mdadm

Follow this sticky ssh into omv as root and copt and paste each output into a code box -> symbol </> on the thread bar, also include information regarding your system and the version of omv

harwey01 · 4. Mai 2023

Hi geaves,

thanks for your quick replay.

These are all results and I have no idea what they mean

My system:

6.3.10-2 (Shaitan)

Prozessor Intel(R) Pentium(R) CPU G4400 @ 3.30GHz

Kernel Linux 5.16.0-0.bpo.4-amd64

Code

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] 
md127 : active raid5 sdc[5] sdd[6] sdb[4]
      8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [_UUU]
      
unused devices: <none>

Code

 blkid
/dev/sdd: UUID="622d9f42-c849-c2dd-ac25-b97e6f32b4bf" UUID_SUB="5abbd615-1eb9-91bf-c544-ab46e757a467" LABEL="Harry-sein-NAS:OMV" TYPE="linux_raid_member"
/dev/sdc: UUID="622d9f42-c849-c2dd-ac25-b97e6f32b4bf" UUID_SUB="0f2e257c-d44b-908f-324d-8e5590bb7c43" LABEL="Harry-sein-NAS:OMV" TYPE="linux_raid_member"
/dev/sde: UUID="622d9f42-c849-c2dd-ac25-b97e6f32b4bf" UUID_SUB="31e5ea6b-8531-8ce4-428f-e9bafd14b44d" LABEL="Harry-sein-NAS:OMV" TYPE="linux_raid_member"
/dev/sdb: UUID="622d9f42-c849-c2dd-ac25-b97e6f32b4bf" UUID_SUB="ee03690c-e2c9-62d6-bd13-0b46162272ea" LABEL="Harry-sein-NAS:OMV" TYPE="linux_raid_member"
/dev/sda1: UUID="a724e2c6-f3e3-401c-be32-e7208966ad57" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="86125f95-01"
/dev/sda5: UUID="3903e171-7c0c-4245-bcfd-87d2457baef6" TYPE="swap" PARTUUID="86125f95-05"
/dev/md127: LABEL="OMV" UUID="02574a47-539a-4078-a8f5-01232e9efbfe" BLOCK_SIZE="4096" TYPE="ext4"

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>
# instruct the monitoring daemon where to send mail alerts
MAILADDR mail@xxxxxx
MAILFROM root

# definitions of existing MD arrays
ARRAY /dev/md/OMV metadata=1.2 name=Harry-sein-NAS:OMV UUID=622d9f42:c849c2dd:ac25b97e:6f32b4bf
root@harry-sein-omv:~# mdadm --detail --scan --verbose
ARRAY /dev/md/OMV level=raid5 num-devices=4 metadata=1.2 name=Harry-sein-NAS:OMV UUID=622d9f42:c849c2dd:ac25b97e:6f32b4bf
   devices=/dev/sdb,/dev/sdc,/dev/sdd

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>
# instruct the monitoring daemon where to send mail alerts
MAILADDR mail@xxxxxxx
MAILFROM root

# definitions of existing MD arrays
ARRAY /dev/md/OMV metadata=1.2 name=Harry-sein-NAS:OMV UUID=622d9f42:c849c2dd:ac25b97e:6f32b4bf
root@harry-sein-omv:~# mdadm --detail --scan --verbose
ARRAY /dev/md/OMV level=raid5 num-devices=4 metadata=1.2 name=Harry-sein-NAS:OMV UUID=622d9f42:c849c2dd:ac25b97e:6f32b4bf
   devices=/dev/sdb,/dev/sdc,/dev/sdd

Alles anzeigen

geaves · 4. Mai 2023

Zitat von harwey01

My system:

motherboard?

the drive that's been removed is /dev/sde, do not reboot or shutdown as this can change the drive references

How/when did you notice the missing drive

harwey01 · 4. Mai 2023

That a drive is missing I noticed after installing OMV 6

What I don't understand is that OMV sees all 5 drives but I can't expand or rebuild the RAID.

geaves · 4. Mai 2023

/dev/sda is your boot drive you cannot add that to the array

If you look at the second image you posted, the details of the array, it shows you one drive has been removed, that drive was removed by mdadm (software raid), why, it detected a fault or an error on the drive, so to protect the array mdadm removed it

The way to deal with this is from the GUI, it's easier to use than the cli, so;

storage -> disks select /dev/sde, on the menu click on wipe, then click secure, this totally erases that drive of the filesystem and any raid signatures

when finished;

Raid Management -> select the array and on the menu click recover, on the next screen from the drop down device select /dev/sde, it should be only drive available then click save, the array should rebuild.

If the drive (/dev/sde) does not show as being selectable then come back as this has happened recently with no reason why

Try not to access/use the server and refrain from adding any data to the existing 3 working drives

harwey01 · 4. Mai 2023

Thanks for your help, I have now deleted the dev/sde drive and was able to add it back to the raid.

The raid group is currently being enlarged, let's see what happens. Fortunately I have a second server here which serves as a backup.

I will give an info when everything is done.

harwey01 · 4. Mai 2023

recovering is by 92%

Now I´m on 100% everything works fine

Thanks for your helpful effort.

Harry from Duisburg

geaves · 4. Mai 2023

Zitat von harwey01

recovering is by 92%

Excellent

1 of 4 HHD´s missed

geaves 4. Mai 2023

geaves 4. Mai 2023

Jetzt mitmachen!