Containers Wont Access Shared Volumes After RAID Rebuild

I started getting bad sectors on my 5TB Raid1 array this week, so I ordered a replacement drive 6TB, and set about replacing my failing drive.

I shut down my system, removed the failing drive, replaced it with the new drive, and restarted my system. The array was not visible on booting up, so I powered down the new drive, and how swapped the failing drive back in, at which point it detected the array, so I powered down the failing drive and how swapped the new one back in. From here I successfully rebuilt the RAID array and tested to make sure things were working properly. All of my mapped smb shares popped up and all my files appeared to be there.

The issue began when I launched my Airsonic and Jellyfin Docker containers. All of the folders in the shared volume that was on the rebuilt raid array were not accessible to these docker containers. I used the Docker GUI to try to reselect the target folders in case something had gone wrong, but they were missing from the GUI. So I did a full OMV restart, and then these folders were visible in the dockerGUI, but the containers are still behaving like they don't have access to these folders.

I'm not aware that I changed any configuration for anything. What has gone wrong here? Feel free to move this to the appropriate forum section, if I've chosen incorrectly.

I am still on OMV4, and I plan on updating in ~5 months when I'm in a place where I'll have the time/space/resources to do it. So I just need to limp along until then.

# lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda       8:0    0 298.1G  0 disk
├─sda1    8:1    0   199M  0 part
├─sda2    8:2    0   281G  0 part
├─sda3    8:3    0  16.8G  0 part
└─sda4    8:4    0 103.3M  0 part
sdb       8:16   0  29.8G  0 disk
├─sdb1    8:17   0    22G  0 part  /
├─sdb2    8:18   0     1K  0 part
└─sdb5    8:21   0   7.8G  0 part  [SWAP]
sdc       8:32   0   4.6T  0 disk
└─md127   9:127  0   4.6T  0 raid1 /srv/dev-disk-by-label-Volume3
sdd       8:48   0   5.5T  0 disk
└─md127   9:127  0   4.6T  0 raid1 /srv/dev-disk-by-label-Volume3
sde       8:64   0   1.8T  0 disk
└─md126   9:126  0   1.8T  0 raid1 /srv/dev-disk-by-label-Volume2
sdf       8:80   0   1.8T  0 disk
└─md126   9:126  0   1.8T  0 raid1 /srv/dev-disk-by-label-Volume2
sdg       8:96   0   2.7T  0 disk
└─md125   9:125  0   2.7T  0 raid1 /srv/dev-disk-by-label-Volume1
sdh       8:112  0   2.7T  0 disk
└─md125   9:125  0   2.7T  0 raid1 /srv/dev-disk-by-label-Volume1

And my docker inspect: https://pastebin.com/6LEz2aR7

Thank you!

The folders are still there: "all my files appeared to be there."

As far as permissions, I didn't change any permissions configuration. Could it have been reset by any of the actions I had taken? What's the most effective way to check permissions?

Watching some tutorials on youtube, and people appear to use /srv/dev-disk-by-label-Volume3 instead of /sharedfolders/Volume3/

What is the difference in functionality there?

Looks like users can access:

drwxrwsr-x+ 12 root users     4096 Feb  7 15:15 Volume1
drwxrwsr-x+ 14 root users     4096 Feb  4 20:26 Volume2
drwxrwsr-x+  6 root users     4096 Feb  8 09:20 Volume3