I recently ran into a problem where if there's no support for some mounted file system in OMV (for example, Paragon's UFSD, which I use for MAC and NTFS drives), OMV not only refuses to create shares but even open the share list without showing the dreaded "Invalid RPC response" error.
I am myself a PHP developer and did some rough digging into OMV code and found that this is caused by the lack of file system support in OMV itself (Exception raised due to no filesystem implementation). But reading foreign OOP code takes a lot of time. Perhaps a developer could explain me how can I integrate additional file systems into OMV (it does not have to be easy, I like a challenge) ? In exchange, I could contribute some code back to OMV.
Is there good reason you do not refer to drives by their UUID (blkid) identifiers instead of volume labels ? Labels aren't really meant to be unique and in my opinion aren't the best way to identify a drive. Also, doesn't OMV already use UUID to mount drives with no label ?
Thank you in advance.