Newly created RAID5 cannot be mounted

Hi,

So I have just created my very first raid using md plugin.

when I go to Storage > file system > Create and mount file system

System msg then creates the mount. I have 0 erros. but when I want to confirm configuration change I get this error

this is how it looks from CLI

cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdb[1] sda[0] sdd[3] sdc[2]
6000798720 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/4 pages [0KB], 65536KB chunk

lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINT,UUID
NAME SIZE FSTYPE MOUNTPOINT UUID
sda 1.9T linux_raid_member cc32ecc6-850d-8b27-83a0-f148f4dc0257
└─md0 5.6T ext4 /srv/md0 376f5756-5211-460f-9111-56ad9b6d2142
sdb 1.9T linux_raid_member cc32ecc6-850d-8b27-83a0-f148f4dc0257
└─md0 5.6T ext4 /srv/md0 376f5756-5211-460f-9111-56ad9b6d2142
sdc 1.9T linux_raid_member cc32ecc6-850d-8b27-83a0-f148f4dc0257
└─md0 5.6T ext4 /srv/md0 376f5756-5211-460f-9111-56ad9b6d2142
sdd 1.9T linux_raid_member cc32ecc6-850d-8b27-83a0-f148f4dc0257
└─md0 5.6T ext4 /srv/md0 376f5756-5211-460f-9111-56ad9b6d2142
nvme0n1 465.8G
├─nvme0n1p1 512M vfat /boot/firmware EC36-4DE1
└─nvme0n1p2 465.3G ext4 / d4cc7d63-da78-48ad-9bdd-64ffbba449a8

how it looks from the GUI

My NAS is built on SBC Rpi5 8GB.

I tried to unmount the raid, remove the filesystem and try once again, but got same result.

I would appreciate any hint.

thank you

Hi Votdev,

thanks for prompt reply.

I didn't know I could get the error exported. sorry bout that.

the result was a big AHA! moment

enabling me to see the bug was actually a sufficient support

So to be helpful also to other users.

So my NAS was originally composed of old ntb HDDs. now after an upgrade to SSDs I did not remove all former file systems

my plan was to use fifth unused SATA slot on the NAS to hook one hdd after another and copy the data like this.

and thus to be able to do it remotely I needed to keep former samba setup.

Apparently one of the disks was not EXT4 but NTFS which OVM didn't like to work with now and all I needed to do was to remove samba dlna shares with this disk and ofc this filesystem from OVM.

it worked like a breeze.

here is the relevant part of the error message

Quote

ID: mount_filesystem_mountpoint_a62ee1bc-c9a5-4c38-860e-671c3c4477ad

Function: mount.mounted

Name: /srv/dev-disk-by-uuid-5824BFD324BFB27C

Result: False

Comment: ntfs-3g: Failed to access volume '/dev/disk/by-uuid/5824BFD324BFB27C': No such file or directory

ntfs-3g 2022.10.3 integrated FUSE 28 - Third Generation NTFS Driver

Configuration type 7, XATTRS are on, POSIX ACLS are on

Copyright (C) 2005-2007 Yura Pakhuchiy

Copyright (C) 2006-2009 Szabolcs Szakacsits

Copyright (C) 2007-2022 Jean-Pierre Andre

Copyright (C) 2009-2020 Erik Larsson

Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

Options: ro (read-only mount), windows_names, uid=, gid=,

umask=, fmask=, dmask=, streams_interface=.

Please see the details in the manual (type: man ntfs-3g).

Example: ntfs-3g /dev/sda1 /mnt/windows

Plugin path: /usr/lib/aarch64-linux-gnu/ntfs-3g

News, support and information: https://github.com/tuxera/ntfs-3g/

Started: 23:28:21.186133

Duration: 11.921 ms

Changes:

Display More