Shared folder error after add union filesystems

  • Hi,


    I have created an union filesytem with 2 EXT4 filesystems.
    But i have an error when i want to add a new shared folder with this new union filesystem.


    Precisely this error occured when i want to list available device :

    Code
    Error #0:OMV\Rpc\Exception: Invalid RPC response. Please check the syslog for more information. in /usr/share/php/openmediavault/rpc/rpc.inc:187Stack trace:#0 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('ShareMgmt', 'getCandidates', Array, Array, 3)#1 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()#2 {main}


    In syslog :


    Code
    Jan 30 17:52:16 omv omv-engined[7372]: PHP Fatal error: Uncaught Error: Call to a member function getImpl() on null in /usr/share/php/openmediavault/system/filesystem/filesystem.inc:898
    Jan 30 17:52:16 omv omv-engined[7372]: Stack trace:
    Jan 30 17:52:16 omv omv-engined[7372]: #0 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(88): OMV\System\Filesystem\Filesystem::getImplByMountPoint('/srv/f13d6a78-b...')
    Jan 30 17:52:16 omv omv-engined[7372]: #1 [internal function]: Engined\Rpc\ShareMgmt->getCandidates(Array, Array)
    Jan 30 17:52:16 omv omv-engined[7372]: #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    Jan 30 17:52:16 omv omv-engined[7372]: #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getCandidates', Array, Array)
    Jan 30 17:52:16 omv omv-engined[7372]: #4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('ShareMgmt', 'getCandidates', Array, Array, 1)
    Jan 30 17:52:16 omv omv-engined[7372]: #5 {main}
    Jan 30 17:52:16 omv omv-engined[7372]: thrown in /usr/share/php/openmediavault/system/filesystem/filesystem.inc on line 898

    Thank you for your help !!

  • In my /etc/fstab, i have this for the unionfs :

    Code
    /srv/dev-disk-by-label-Storage:/srv/dev-disk-by-label-Storage2 /srv/f13d6a78-ba62-41e4-845c-f3e53565f721 fuse.mergerfs defaults,allow_other,cache.files=off,use_ino,category.create=epmfs,minfreespace=4G,x-systemd.requires=/srv/dev-disk-by-label-Storage,x-systemd.requires=/srv/dev-disk-by-label-Storage2 0 0
  • root@omv:~# dpkg -l | grep openm
    ii libopenmpt0:amd64 0.4.3-1 amd64 module music library based on OpenMPT -- shared library
    ii omvextras-unionbackend 5.0.2 all union filesystems backend plugin for openmediavault
    ii openmediavault 5.2.6-1 all openmediavault - The open network attached storage solution
    ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
    ii openmediavault-minidlna 5.0.3 all OpenMediaVault miniDLNA (DLNA server) plugin
    ii openmediavault-omvextrasorg 5.2.3 all OMV-Extras.org Package Repositories for OpenMediaVault
    ii openmediavault-snapraid 5.0.5 all snapraid plugin for OpenMediaVault.
    ii openmediavault-unionfilesystems 5.1 all Union filesystems plugin for OpenMediaVault.

  • I'm having this exact same issue. If I remove the unionfs device, I can add Shared Folders again but as soon as I add a unionfs device back in, I get that same error (with the new device id of course). In fact I get it right after I hit Add, before I even have the chance to pick anything in the drop down.

  • @votdev This change is breaking the mergerfs plugins because it is not returning the correct device file. Thoughts?


    root@omv5dev:~# grep 8d0d /proc/mounts
    p1:8d0d73a5-246e-4cf9-91d0-d4808eeeda41 /srv/8d0d73a5-246e-4cf9-91d0-d4808eeeda41 fuse.mergerfs rw,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0


    root@omv5dev:~# findmnt --first-only --noheadings --output=SOURCE --raw /srv/8d0d73a5-246e-4cf9-91d0-d4808eeeda41
    p1:8d0d73a5-246e-4cf9-91d0-d4808eeeda41

    omv 5.3.9 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • I have the same issue.
    I changed from EPMFS to MFS policy, the sharedfolders are no longer displaying in OMV menu.
    The fstab showing the correct policy though.




    Code
    Error #0:
    OMV\Rpc\Exception: Invalid RPC response. Please check the syslog for more information. in /usr/share/php/openmediavault/rpc/rpc.inc:187
    Stack trace:
    #0 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('ShareMgmt', 'enumerateShared...', Array, Array, 3)
    #1 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
    #2 {main}
  • Looks like I am having the same issue.
    So omv5 is still unreliable yet?

    OMV5 is perfectly reliable (although not technically stable yet)... it appears an update made broke the plugin. It could have just as easily happened on OMV 4, and it's been stable forever. It happens. Just be patient, it will get worked out.

  • @votdev This change is breaking the mergerfs plugins because it is not returning the correct device file. Thoughts?


    root@omv5dev:~# grep 8d0d /proc/mounts
    p1:8d0d73a5-246e-4cf9-91d0-d4808eeeda41 /srv/8d0d73a5-246e-4cf9-91d0-d4808eeeda41 fuse.mergerfs rw,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0


    root@omv5dev:~# findmnt --first-only --noheadings --output=SOURCE --raw /srv/8d0d73a5-246e-4cf9-91d0-d4808eeeda41
    p1:8d0d73a5-246e-4cf9-91d0-d4808eeeda41

    The problem is that /proc/mount sometimes contains invalid entries, e.g. some ARM devices return /dev/root for the root filesystem. /dev/root is incorrect, it is deprecated since Debian Lenny and there is no UDEV rule in Debian anymore which resolves this path correctly.


    @ryecoaaron Please correct me, but to me the returned device file looks the same as in the /etc/fstab.

  • It appears to have worked for me as well. Thank you for the quick fix! I'm definitely loving the install so far. I moved from a failing WHS 2011 system so it is very different but has been very easy to setup and run so far.


    I am pretty sure I know the answer to this but just in case:


    Is there an easy or clean way to move data from an existing shared folder to a new unionfs shared folder? My old WHS system was so flaky that I needed to get all the data off it so I just moved it to shared folders mapped to specific disks. I have plenty of space to move things around right now but all my dockers and kodi/mobile clients are already mapped to the existing shares (full server paths). I assume there's no easy way to adjust dockers but I'm hoping I'm wrong :) Worst case it's probably a matter of a few hours to get it all setup and working again but I wanted to make sure there wasn't an easier way before I headed down that path.


    Thanks again!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!