Change SSD in RAID, now cannot mount

Hello,

I have an NVMe NAS (Gtek with Intel(R) N150) and 4 SSD NVMe (2 Samsung SSD 980 PRO 2TB and 2 KINGSTON SNV3S2000G)

I change one of the SSD and then my partition cannot be mounted. I try in repairing the RAID, theoretically was rebuild but I cannot see the partition anymore .

Here are some details :

root@Ender-G:~# cat /proc/mdstat

Quote

Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10]

md0 : active raid5 nvme1n1[1] nvme3n1[2] nvme0n1[0] nvme2n1[4]

5860147200 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

bitmap: 0/15 pages [0KB], 65536KB chunk

unused devices: <none>

root@Ender-G:~# blkid

Quote

/dev/nvme0n1: UUID="64399d72-c502-e1e1-720f-404de3ac1bb4" UUID_SUB="c68929b3-8ead-7e82-1888-16f7f9ce6233" LABEL="Ender-G:0" TYPE="linux_raid_member"

/dev/nvme3n1: UUID="64399d72-c502-e1e1-720f-404de3ac1bb4" UUID_SUB="8696f94a-96db-6c21-fa5d-d2052a83c080" LABEL="Ender-G:0" TYPE="linux_raid_member"

/dev/mmcblk0p3: UUID="8062f5bc-579d-4e95-9e01-254a0ded2ea2" TYPE="swap" PARTUUID="39457a81-ce3f-4630-a56a-23d100c3ccbb"

/dev/mmcblk0p1: UUID="7E5A-3D8E" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f2914223-dba5-4295-98ff-7147af77fa8d"

/dev/mmcblk0p2: UUID="16f6d4ca-8f68-450b-94de-115108860505" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="288bdec5-bae0-487c-a68a-07638a01a5ef"

/dev/md0: UUID="c2b9ead3-3823-446f-8bec-5e4a588c12b1" BLOCK_SIZE="4096" TYPE="ext4"

/dev/nvme2n1: UUID="64399d72-c502-e1e1-720f-404de3ac1bb4" UUID_SUB="66a3b200-ec20-672b-b1ca-4dff2aab1bc0" LABEL="Ender-G:0" TYPE="linux_raid_member"

/dev/nvme1n1: UUID="64399d72-c502-e1e1-720f-404de3ac1bb4" UUID_SUB="1e860a33-74c2-ce56-89e7-85831c161ac9" LABEL="Ender-G:0" TYPE="linux_raid_member"

root@Ender-G:~# fdisk -l | grep "Disk "

Disk /dev/nvme1n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors

Disk model: Samsung SSD 980 PRO 2TB

Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors

Disk model: Samsung SSD 980 PRO 2TB

Disk /dev/nvme3n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors

Disk model: KINGSTON SNV3S2000G

Disk /dev/nvme2n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors

Disk model: KINGSTON SNV3S2000G

Disk /dev/mmcblk0: 58.23 GiB, 62528684032 bytes, 122126336 sectors

Disk identifier: 6D9B3DE4-07F5-473C-9A4D-F5E8E594AED9

Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors

Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors

Disk /dev/md0: 5.46 TiB, 6000790732800 bytes, 11720294400 sectors

Display More

root@Ender-G:~# cat /etc/mdadm/mdadm.conf

Quote

# 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

# definitions of existing MD arrays

ARRAY /dev/md0 metadata=1.2 name=Ender-G:0 UUID=64399d72:c502e1e1:720f404d:e3ac1bb4

Display More

root@Ender-G:~# mdadm --detail --scan --verbose

Quote

ARRAY /dev/md0 level=raid5 num-devices=4 metadata=1.2 name=Ender-G:0 UUID=64399d72:c502e1e1:720f404d:e3ac1bb4

devices=/dev/nvme0n1,/dev/nvme1n1,/dev/nvme2n1,/dev/nvme3n1