BUG or misconfiguration: i have to wait a while until /dev/md0 is mounted to be able to ssh on omv

ssh from windows box

PS C:\Users\xxxxxx> ssh root@192.168.xxx.xx

root@192.168.xxx.xxx's password:

"System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8)."

users is on a shared folder created on /dev/md0 raid6 array

i have to wait a while until the raid6 array is mounted to ssh on omv

*** SOLVED ***

The array is formated as F2FS

omv tries to mount it using parameters that are not compatible with F2FS

i mounted using fstab and the problem disappeared

it is a potential misconfiguration of openmediavault because f2fs is not very popular. when i created another raid5 array again through openmediavault two years ago it worked flawlessly up until i deleted it a few weeks ago

openmediavault automatically mounts filesystems. there is no way the user can change mount parameters

f2fs is much different than ext4 or xfs

i mount f2fs using defaults -- openmediavault mounts with extra parameters like quotas if i am not mistaken, etc.

i have a linux software raid6 array 8 data ssd / 2 parity ssd. the array was created initialized through omv and then formated as f2fs. when i mount it through omv and restart the system i get a huge timeout until md0 filesystem becomes available. mounting through fstab using defaults solves the problem

i manually edited fstab adding the /dev/md0 raid6 array

#################################################

UUID= /mnt f2fs defaults 0 0

#################################################

after root fs and before openmediavault entries