No filesystem backend exists for type 'cifs' errors - but all seems to work anyway

    • OMV 3.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • No filesystem backend exists for type 'cifs' errors - but all seems to work anyway

      I get the error below when I visit a couple of services.

      I guess there is some settings thats got lost during the last week, when I have had problems during the upgrade.

      This time it came when I opened the nginx service in the GUI. But I get this from other as well.

      Source Code

      1. No filesystem backend exists for type 'cifs'.
      2. Error #0:
      3. OMV\AssertException: No filesystem backend exists for type 'cifs'. in /usr/share/php/openmediavault/system/filesystem/backend/
      4. Stack trace:
      5. #0 /usr/share/openmediavault/engined/rpc/ OMV\System\Filesystem\Backend\Manager->assertBackendExistsByType('cifs')
      6. #1 [internal function]: OMVRpcServiceShareMgmt->enumerateSharedFolders(Array, Array)
      7. #2 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)
      8. #3 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('enumerateShared...', Array, Array)
      9. #4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('ShareMgmt', 'enumerateShared...', Array, Array, 1)
      10. #5 {main}
    • The system do work but I cant really change things as this exception prevents pages to load properly, Like "File Systems".

      I can see that there are items /etc/openmediavault/config.xml under fstab that is missing from /etc/fstab.

      But as I accidentaly removed OMV and succeeded to reinstate it, I had presumed it to be the other way around. That things would be gone from omv setting but in place for fstab...

      For instance this section is from config.xml but no UUID starts with "fd9" is fstab.

      Source Code

      1. <mntent>
      2. <uuid>fd900769-c5d8-447d-b1c1-d803216edaa0</uuid>
      3. <fsname>c95301c0-9790-48c6-ab1f-17da8e3c3538</fsname>
      4. <dir>/media/c95301c0-9790-48c6-ab1f-17da8e3c3538</dir>
      5. <type>cifs</type>
      6. <opts></opts>
      7. <freq>0</freq>
      8. <passno>0</passno>
      9. <hidden>1</hidden>
      10. </mntent>

      What steps should I do to realign my system so that everything works as expected again?
      Any specific config files I can add that would help the troubleshooting or logs?

      On the File system page I get this exception:
      Error #0:exception 'OMV\Exception' with message 'No filesystem backend exists for 'cifs'.' in /usr/share/openmediavault/engined/rpc/ trace:#0 [internal function]: OMVRpcServiceFileSystemMgmt->getList(Array, Array)#1 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)#2 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)#3 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'getList', Array, Array, 1)#4 {main}

      The post was edited 2 times, last by 7ore ().

    • Sounds like the remotemount plugin isn't installed or partially installed.
      omv 4.1.17 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13 plugins source code and issue tracker - github

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