Mdadm: CREATE group disk not found

I noticed that after the last software update (a few days ago) that my RAID device produces an error that read:

mdadm: CREATE group disk not found

I tried to manually start the array mdadm --assemble --force /dev/md0 /dev/sdb /dev/sdc and got the same message.

Eventually, I was able to mount the device mount -t btrfs /dev/md0 /mnt/raid/.

I just tried rebooting the router to see if I could get the problem to reoccur, but it didn’t. It seems to be related to a software update. I built a similar configuration for a friend, and he has the same issue.

What might be the cause of this issue? Is there a way to prevent it?

** edit **

Testing this AM (with a mounted RAID device).

I get the error with the device mounted:

# mdadm --detail --scan
mdadm: CREATE group disk not found
ARRAY /dev/md0 metadata=1.2 name=turris:0 UUID=69c415bb:716b8e0b:b03d7218:88a9cb05

Examine /etc/mdadm/mdadm.conf reveals the issue (I think):

# cat /etc/mdadm/mdadm.conf 
# /etc/mdadm/mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes   <----- HERE

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR XXXXX@XXXX.com

# definitions of existing MD arrays (# mdadm --examine --scan)
ARRAY /dev/md/0  metadata=1.2 UUID=69c415bb:716b8e0b:b03d7218:88a9cb05 name=turris:0

It appears that I don’t have a group with the name disk. How do I create this group?

** edit 1 **

The list of groups on the Omnia:

# cat /etc/group
root:x:0:
daemon:x:1:
adm:x:4:
tty:x:5:
mail:x:8:
audio:x:29:
www-data:x:33:
ftp:x:55:
users:x:100:
network:x:101:
nogroup:x:65534:
kresd:x:3536:kresd
dnsmasq:x:453:dnsmasq
sshd:x:22:sshd
mosquitto:x:200:mosquitto
rpc:x:65533:rpc
minidlna:x:65536:minidlna
cron:x:16:cron
nfs:x:65537:nfs
dialout:x:20:
gerbera:x:65538:gerbera
transmission:x:224:transmission

Is fixing this just a matter of adding root to a group named disk?

I created a group named disk:

# groupadd disk

I added root to the group:

# usermod -G disk -a root

The problem was solved:

# mdadm --detail --scan
ARRAY /dev/md0 metadata=1.2 name=turris:0 UUID=69c415bb:716b8e0b:b03d7218:88a9cb05