The extensions do not appear in the corresponding tab of the Jellyfin configuration. I guess Jellyfin can't connect to repository ... or can't save to created folder ...
I installed docker again in the default path and it worked fine.
The extensions do not appear in the corresponding tab of the Jellyfin configuration. I guess Jellyfin can't connect to repository ... or can't save to created folder ...
I installed docker again in the default path and it worked fine.
This guide has a problem.
Doing this in a clean installation did not work for me the Jellyfin repository. If someone knows what is missing ... Otherwise this does not work.
Thank you. You are opening up study paths for me. I will still have to spend more time.
Every tool in OMV has too many options. You have to know how to use them well to avoid problems. It is complex.
It would be nice to enable a basic mode with only the basic options and an advanced mode with all the options. Sure there are options that are not necessary for the average user. If they could hide it would be easier. When you already know how to use the basics, you take one more step and activate the advanced options. In the style of kodi.
The wiki was, originally, for Linux experts and developers
Now I understand it all. There are still reminiscences of the origin of the text. You have done a great job.
Tell me, did the translation make sense?
Yes. It is perfectly understood. Illustrations in English are not a problem. I have next to my GUI in Spanish if there are doubts.
QuoteOff line means you can't access the ...
Thanks for the explanation, I will use it well. It was just an example of the problems that I find myself. The famous disk is already in synology running smoothly. I changed one for another.
This is life
so is
You and everyone else, to include me. I've been
I get the impression that the problem with this thread came after doing several rsync for a backup. Something changed permissions to many folders and files. I tried to solve it by modifying ACL permissions and I didn't get anything. Is it possible that this ends up affecting the access of a disk? I had files copied to various sites. I made copies with rsync from a synology, from windows, from OMV between two disks ... it was varied.
I had to reinstall the system for another problem. I can tell you that the disks with data can be reassembled without problems in the OMV GUI. You will not lose the data.
When you have mounted them you have to create the same shared folders that you had before and you will be able to access your data. As for the snapraid I don't know if it is possible to take advantage of the parity disk. But it is a lesser evil. You can reconfigure snapraid and resynchronize the parity disk.
Luck.
That guide is here https://openmediavault.readthe…rd-drive-health-and-smart
and google translates it for me on the screen without doing anything. This manual covers many topics but without going into depth and often in technical language. It is assumed that to manage / start in OMV you only have to be a windows user and have knowledge of networks, I have read this somewhere.
I have been looking at the explanation of SMART, for example. When he says that a long test is an "off line" test, it is as if they spoke to me in Chinese. Will I be able to use the data while the test is done? I cant? Will I have the server stopped for 18 hours? Do I have to do something before the disc so that it is "off line"? Do I have to disassemble it? To find the answer I have to start googling what that means ... and in the end it takes three hours to understand everything. Or ask here continuously and bother for nonsense. It is an example, similar things have happened to me with other OMV songs. Sometimes I do things that I don't know what I'm doing, like the "Flash memory" settings, that I have to get into editing fstab and write things that I don't know what they mean. Or the issue of file permissions, which drives me crazy. Finding the detailed explanation is the difficult thing. And the procedures.
Regarding synology, I know that it has its advantages and disadvantages. And I like the drawbacks less and less, that's why I'm here looking for alternatives. I hope to get to use OMV as a winchoff over time. You will not get rid of me and my questions.
Finally I decided to start over with a clean installation ... I have already lost count of how many I have done ... I hope this is the final one.
Thank you very much for the extensive explanation on SMART. Some things I already knew and others are new, you always learn.
I know it's not fair to compare OMV to synology, but I can't help it. I've been with synology for many years and I miss a place where all the information is organized and updated. Here it is very difficult sometimes to find the information. It is all very disaggregated and often in a tremendously technical language, very difficult to understand for a user not used to Linux. On the other hand, it is the only thing missing. Everything else I know I have here and you just have to learn how to use it.
Anyway my congratulations to all OMV developers. They are doing a great job. I'll keep trying, I guess it's a matter of patience and I have a lot.
I don't know how to do a long test. And every time I do something in linux / OMV I waste three hours reading and looking for information.
I have two other disks like that in a Synology server in RAID 1. I will replace the disk with one of those two. And I'll put that in synology, which is easier to test.
Then I will retrieve the data with SnapRaid and we will see the result.
This system is giving me a lot of problems and work ... I am learning a lot but at a very high price.
fstab is correct.
The sda disk does not have RO.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=f06c7755-2672-4a44-832e-af41d0443640 / ext4 noatime,nodiratime,errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
# UUID=1a5337de-7712-4b87-a324-9b6b0dc63ef8 none swap sw 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/ff0c80a3-94f6-4d00-986b-69902cb2c5c4 /srv/dev-disk-by-uuid-ff0c80a3-94f6-4d00-986b-69902cb2c5c4 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/61035a56-6a5f-4a32-9877-7f97232ca51e /srv/dev-disk-by-uuid-61035a56-6a5f-4a32-9877-7f97232ca51e ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/336149ff-95b4-4cfc-ad09-ab37c7a469a2 /srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab37c7a469a2 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/681875d7-7946-431c-b0cb-40c9379741ed /srv/dev-disk-by-uuid-681875d7-7946-431c-b0cb-40c9379741ed ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/27d00169-5e94-493d-aa6c-629d183b9e4b /srv/dev-disk-by-uuid-27d00169-5e94-493d-aa6c-629d183b9e4b ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/3b76061a-9bb2-423f-9f26-d03e03c9554a /srv/dev-disk-by-uuid-3b76061a-9bb2-423f-9f26-d03e03c9554a ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/fdd43d81-369d-4a14-8187-62da3fed6c63 /srv/dev-disk-by-uuid-fdd43d81-369d-4a14-8187-62da3fed6c63 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/srv/dev-disk-by-uuid-681875d7-7946-431c-b0cb-40c9379741ed:/srv/dev-disk-by-uuid-61035a56-6a5f-4a32-9877-7f97232ca51e:/srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab37c7a469a2 /srv/d245d9f1-19a0-4051-8e4c-9c2052784fcd fuse.mergerfs defaults,allow_other,cache.files=off,use_ino,category.create=mfs,minfreespace=750G,fsname=Datos:d245d9f1-19a0-4051-8e4c-9c2052784fcd,x-systemd.requires=/srv/dev-disk-by-uuid-681875d7-7946-431c-b0cb-40c9379741ed,x-systemd.requires=/srv/dev-disk-by-uuid-61035a56-6a5f-4a32-9877-7f97232ca51e,x-systemd.requires=/srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab37c7a469a2 0 0
//192.168.1.77/comun /srv/a28ecba5-885b-4bea-a61d-fbb34ae878a6 cifs _netdev,iocharset=utf8,vers=2.0,nofail,credentials=/root/.cifscredentials-530132f8-0516-4d9f-8998-6b19d0d28940 0 0
# <<< [openmediavault]
root@sotano:~#
Display More
It occurs to me to remove that disk, format it, and recover the information with SnapRaid. Would it fix the problem?
The system startup log shows various errors.
Jan 24 11:43:07 sotano systemd[1]: Mounted /srv/dev-disk-by-uuid-fdd43d81-369d-4a14-8187-62da3fed6c63.
Jan 24 11:43:07 sotano systemd[1]: Mounted /srv/dev-disk-by-uuid-3b76061a-9bb2-423f-9f26-d03e03c9554a.
Jan 24 11:43:07 sotano systemd-fsck[570]: D3: clean, 21618/244195328 files, 742565302/976754385 blocks
Jan 24 11:43:07 sotano systemd[1]: Started File System Check on /dev/disk/by-uuid/336149ff-95b4-4cfc-ad09-ab37c7a469a2.
Jan 24 11:43:07 sotano systemd[1]: srv-dev\x2ddisk\x2dby\x2duuid\x2d336149ff\x2d95b4\x2d4cfc\x2dad09\x2dab37c7a469a2.mount: Directory /srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab37c7a469a2 to mount over is not empty, mounting anyway.
Jan 24 11:43:07 sotano kernel: [ 0.092175] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Jan 24 11:43:07 sotano systemd[1]: Mounting /srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab37c7a469a2...
Jan 24 11:43:07 sotano kernel: [ 0.092175] #3
Jan 24 11:43:07 sotano kernel: [ 0.094153] smp: Brought up 1 node, 4 CPUs
Jan 24 11:43:07 sotano kernel: [ 0.094153] smpboot: Max logical packages: 1
Jan 24 11:43:07 sotano kernel: [ 0.094153] smpboot: Total of 4 processors activated (26398.33 BogoMIPS)
Jan 24 11:43:07 sotano systemd[1]: Mounted /srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab37c7a469a2.
Jan 24 11:43:07 sotano kernel: [ 0.095127] node 0 deferred pages initialised in 0ms
Jan 24 11:43:07 sotano kernel: [ 0.095127] devtmpfs: initialized
Jan 24 11:43:07 sotano systemd[1]: Starting File System Quota Check...
Jan 24 11:43:07 sotano kernel: [ 0.095127] x86/mm: Memory block size: 128MB
Jan 24 11:43:07 sotano kernel: [ 0.095127] PM: Registering ACPI NVS region [mem 0xd9524000-0xd95c1fff] (647168 bytes)
Jan 24 11:43:07 sotano systemd[1]: Mounting /srv/d245d9f1-19a0-4051-8e4c-9c2052784fcd...
......
Jan 24 11:52:57 sotano kernel: [ 657.657978] EXT4-fs warning (device sda1): ext4_end_bio:349: I/O error 10 writing to inode 118489917 starting block 792619264)
Jan 24 11:52:57 sotano kernel: [ 657.657985] ata4: EH complete
Jan 24 11:52:57 sotano kernel: [ 657.657999] Buffer I/O error on device sda1, logical block 792526848
Jan 24 11:52:57 sotano kernel: [ 657.658010] Aborting journal on device sda1-8.
Jan 24 11:52:57 sotano kernel: [ 657.658012] Buffer I/O error on device sda1, logical block 792526849
..
Jan 24 11:52:57 sotano kernel: [ 657.658052] Buffer I/O error on device sda1, logical block 792526856
Jan 24 11:52:57 sotano kernel: [ 657.658057] Buffer I/O error on device sda1, logical block 792526857
Jan 24 11:52:57 sotano kernel: [ 657.658101] EXT4-fs (sda1): Delayed block allocation failed for inode 118489917 at logical offset 385024 with max blocks 2048 with error 30
Jan 24 11:52:57 sotano kernel: [ 657.658110] EXT4-fs (sda1): This should not happen!! Data will be lost
Jan 24 11:52:57 sotano kernel: [ 657.658110]
Jan 24 11:52:57 sotano kernel: [ 657.658119] EXT4-fs error (device sda1) in ext4_writepages:2797: Journal has aborted
Jan 24 11:52:57 sotano kernel: [ 657.686988] ata4.00: limiting speed to UDMA/33:PIO4
Jan 24 11:52:57 sotano kernel: [ 657.686993] ata4.00: exception Emask 0x10 SAct 0x104000 SErr 0x400101 action 0x6 frozen
Jan 24 11:52:57 sotano kernel: [ 657.687001] ata4.00: irq_stat 0x0c000000, interface fatal error
Jan 24 11:52:57 sotano kernel: [ 657.687005] ata4: SError: { RecovData UnrecovData Handshk }
Jan 24 11:52:57 sotano kernel: [ 657.687009] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 24 11:52:57 sotano kernel: [ 657.687016] ata4.00: cmd 61/08:70:00:08:c4/00:00:e8:00:00/40 tag 14 ncq dma 4096 out
Jan 24 11:52:57 sotano kernel: [ 657.687016] res 40/00:a0:00:08:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Jan 24 11:52:57 sotano kernel: [ 657.687022] ata4.00: status: { DRDY }
Jan 24 11:52:57 sotano kernel: [ 657.687026] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 24 11:52:57 sotano kernel: [ 657.687032] ata4.00: cmd 61/08:a0:00:08:00/00:00:00:00:00/40 tag 20 ncq dma 4096 out
Jan 24 11:52:57 sotano kernel: [ 657.687032] res 40/00:a0:00:08:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Jan 24 11:52:57 sotano kernel: [ 657.687037] ata4.00: status: { DRDY }
Jan 24 11:52:57 sotano kernel: [ 657.687043] ata4: hard resetting link
Jan 24 11:52:57 sotano kernel: [ 658.001719] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 24 11:52:57 sotano kernel: [ 658.002688] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
Jan 24 11:52:57 sotano kernel: [ 658.002702] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-531)
Jan 24 11:52:57 sotano kernel: [ 658.007310] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
Jan 24 11:52:57 sotano kernel: [ 658.007324] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-531)
Jan 24 11:52:57 sotano kernel: [ 658.014038] ata4.00: configured for UDMA/33
Jan 24 11:52:57 sotano kernel: [ 658.014050] ata4: EH complete
Jan 24 11:52:57 sotano kernel: [ 658.034974] ata4.00: exception Emask 0x10 SAct 0x900 SErr 0x400101 action 0x6 frozen
Jan 24 11:52:57 sotano kernel: [ 658.034981] ata4.00: irq_stat 0x0c000000, interface fatal error
Jan 24 11:52:57 sotano kernel: [ 658.034985] ata4: SError: { RecovData UnrecovData Handshk }
Jan 24 11:52:57 sotano kernel: [ 658.034989] ata4.00: failed command: WRITE FPDMA QUEUED
Jan 24 11:52:57 sotano kernel: [ 658.034996] ata4.00: cmd 61/08:40:00:08:00/00:00:00:00:00/40 tag 8 ncq dma 4096 out
Jan 24 11:52:57 sotano kernel: [ 658.034996] res 40/00:40:00:08:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Jan 24 11:52:57 sotano kernel: [ 658.035002] ata4.00: status: { DRDY }
Jan 24 11:52:57 sotano kernel: [ 658.035005] ata4.00: failed command: WRITE FPDMA QUEUED
.....
Jan 24 11:53:04 sotano kernel: [ 664.304658] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-531)
Jan 24 11:53:04 sotano kernel: [ 664.304960] ata4.00: configured for UDMA/33
Jan 24 11:53:04 sotano kernel: [ 664.304987] sd 3:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Jan 24 11:53:04 sotano kernel: [ 664.304991] sd 3:0:0:0: [sda] tag#14 Sense Key : Illegal Request [current]
Jan 24 11:53:04 sotano kernel: [ 664.304993] sd 3:0:0:0: [sda] tag#14 Add. Sense: Unaligned write command
Jan 24 11:53:04 sotano kernel: [ 664.304997] sd 3:0:0:0: [sda] tag#14 CDB: Write(16) 8a 00 00 00 00 00 00 00 08 00 00 00 00 08 00 00
Jan 24 11:53:04 sotano kernel: [ 664.305000] blk_update_request: I/O error, dev sda, sector 2048 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Jan 24 11:53:04 sotano kernel: [ 664.305008] Buffer I/O error on dev sda1, logical block 0, lost sync page write
Jan 24 11:53:04 sotano kernel: [ 664.305029] EXT4-fs (sda1): I/O error while writing superblock
Jan 24 11:53:04 sotano kernel: [ 664.305036] EXT4-fs (sda1): previous I/O error to superblock detected
Jan 24 11:53:04 sotano kernel: [ 664.305039] ata4: EH complete
Jan 24 11:53:04 sotano kernel: [ 664.305043] EXT4-fs error (device sda1): ext4_journal_check_start:83: Detected aborted journal
Jan 24 11:53:04 sotano kernel: [ 664.305050] EXT4-fs (sda1): Remounting filesystem read-only
Jan 24 11:53:04 sotano kernel: [ 664.305059] EXT4-fs (sda1): failed to convert unwritten extents to written extents -- potential data loss! (inode 118489917, error -30)
Jan 24 11:53:04 sotano kernel: [ 664.305067] buffer_io_error: 2038 callbacks suppressed
Jan 24 11:53:04 sotano kernel: [ 664.305069] Buffer I/O error on device sda1, logical block 792555520
Display More
The output of the lsblk command indicates that all disks are RO in mode 0. The affected disk is sda.
After trying to write a file I get this error.
And after the lsblk command again it seems to be RO in mode 0.
root@sotano:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 3,7T 0 disk
└─sda1 8:1 0 3,7T 0 part /srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab
sdb 8:16 0 3,7T 0 disk
└─sdb1 8:17 0 3,7T 0 part /srv/dev-disk-by-uuid-61035a56-6a5f-4a32-9877-7f
sdc 8:32 0 4,6T 0 disk
└─sdc1 8:33 0 4,6T 0 part /srv/dev-disk-by-uuid-27d00169-5e94-493d-aa6c-62
sdd 8:48 0 4,6T 0 disk
└─sdd1 8:49 0 4,6T 0 part /srv/dev-disk-by-uuid-681875d7-7946-431c-b0cb-40
sde 8:64 0 55,9G 0 disk
└─sde1 8:65 0 55,9G 0 part /srv/dev-disk-by-uuid-ff0c80a3-94f6-4d00-986b-69
sdf 8:80 0 1,8T 0 disk
└─sdf1 8:81 0 1,8T 0 part /srv/dev-disk-by-uuid-fdd43d81-369d-4a14-8187-62
sdg 8:96 0 10,9T 0 disk
└─sdg1 8:97 0 10,9T 0 part /srv/dev-disk-by-uuid-3b76061a-9bb2-423f-9f26-d0
sdh 8:112 1 28,7G 0 disk
├─sdh1 8:113 1 24,8G 0 part /
├─sdh2 8:114 1 1K 0 part
└─sdh5 8:117 1 3,9G 0 part
root@sotano:~# ^C
root@sotano:~#
Message from syslogd@sotano at Jan 24 11:53:04 ...
kernel:[ 664.305059] EXT4-fs (sda1): failed to convert unwritten extents to written extents -- potential data loss! (inode 118489917, error -30)
Message from syslogd@sotano at Jan 24 11:53:04 ...
kernel:[ 664.306533] EXT4-fs (sda1): failed to convert unwritten extents to written extents -- potential data loss! (inode 118489917, error -30)
Message from syslogd@sotano at Jan 24 11:53:04 ...
kernel:[ 664.307872] EXT4-fs (sda1): failed to convert unwritten extents to written extents -- potential data loss! (inode 118489917, error -30)
Display More
The fstab file shows the same disk settings for all disks. There is no RO option on the sda disk. (I don't know how to copy this file to display it).
Did you backup your USB boot drive?
I have a copy from a week ago. It won't do, I made a lot of changes this week.
I just made a new one.
The problem continues. When I restart the system everything is normal. I can write and delete files. I can sync Snapraid.
After a few minutes the disc goes into read mode. I can no longer write or delete files. I can't sync.
It is as if some process were started that changes the operation of the disk.
I'd do a clean restart
It is done. Everything seems to be in order. Thank you.
I don't understand Anything.
After dinner I sat at the computer and the system was restarting itself.
After that I have tried rsync in sanpraid and it is syncing normally. And I can copy and delete files.
?????
Do I have goblins on the computer?
?????
I mark the thread as solved ..... mysteriously....
I have restarted it several times. When I restart it, it lets me write for a few minutes. Then you can't.
I was copying and deleting files that are in a synology through a windows computer using samba. In case it helps. I have rebooted all 3 machines and it remains the same.
Thank you for responding quickly.
Apparently one of my disks is in read-only mode?. I don't know how this happened or how to fix it.
I was just deleting some files from a shared folder and copying others. Some files won't let me copy them and other files won't let me delete them.
Snapraid has sent me an error email. This is the message.
Self test...
Loading state from /srv/dev-disk-by-uuid-681875d7-7946-431c-b0cb-40c9379741ed/snapraid.content...
Scanning disk D1...
Scanning disk D2...
Scanning disk D3...
Using 741 MiB of memory for the file-system.
Initializing...
Resizing...
Saving state to /srv/dev-disk-by-uuid-681875d7-7946-431c-b0cb-40c9379741ed/snapraid.content...
Saving state to /srv/dev-disk-by-uuid-61035a56-6a5f-4a32-9877-7f97232ca51e/snapraid.content...
Saving state to /srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab37c7a469a2/snapraid.content...
Error removing the stale content file '/srv/dev-disk-by-uuid-336149ff-95b4-4cfc-ad09-ab37c7a469a2/snapraid.content.tmp'. Read-only file system.
Display More
For what it's worth, the last thing I've done is a backup with rsync. I also activated the recycle bins on all shared folders yesterday. I only have one working docker package, Jellyfin.
SMART says the disks are fine.
If I restart the system it lets me write and delete files for a few minutes, then the disk won't write.
I'm lost, I can't find information about this. Any suggestion? Thanks...
....I wouldn't use one.
why?
Thank you very much for your correction. I will follow your advice and adapt it to the script and guidelines to publish it in guides with the Spanish translation. I edit it and add the ACL permissions warning.
That's the benefit of Existing Path, most free space. Once the path is set on one drive, as in a new shared folder, all files go to that folder. If dropping the mount point, there's nothing to consolidate or sort out. Files are under their intended sub-directory. The problem with this policy is "Video" storage. When a "video" shared folder is set, using EP,MFS that folder is the only place where video is stored. This is what we see on the forum and it's the reason why the associated drive fills up.
One way to solve it would be for OMV to automatically create the folder on the second disk when the first one is full. It would be a transparent process for the user maintaining the Existing Path, most free space policy.