ZFS device(s) not listed in devices dropdown

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

    • ZFS device(s) not listed in devices dropdown

      Hi!

      I created an issue for omv yesterday, because I can't create new shares on my ZFS device anymore. The issue got closed because it seems to be caused by the ZFS plugin (see last post of the issue).

      When I set up my NAS a few month I used OMV v4.0.X with the ZFS plugin v4.0 to create the ZFS pool and all shares. After setting up the NAS I updated all system packages on a regular basis (but not the kernel).

      Yesterday I tried to create a new shared folder but the device dropdown menu in the "Add shared folder" popup is empty. The device name for all previous created shares is set to "n/a" in the shared folder overview, but all shared folders are mounted and accessible.

      When I try to edit an existing shared folder, I get the following error message:

      Source Code

      1. "Failed to execute XPath query '//system/fstab/mntent[uuid='3f8ede54-1dc4-47be-ab28-eedd97a3ab6d']'."
      2. Error #0:
      3. OMV\Config\DatabaseException: Failed to execute XPath query '//system/fstab/mntent[uuid='3f8ede54-1dc4-47be-ab28-eedd97a3ab6d']'. in /usr/share/php/openmediavault/config/database.inc:78
      4. Stack trace:
      5. #0 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(231): OMV\Config\Database->get('conf.system.fil...', '3f8ede54-1dc4-4...')
      6. #1 [internal function]: OMVRpcServiceShareMgmt->get(Array, Array)
      7. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      8. #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('get', Array, Array)
      9. #4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('ShareMgmt', 'get', Array, Array, 1)
      10. #5 {main}
      Display All



      Some basic infos about my system:

      Source Code

      1. root@omv:~# uname -a
      2. Linux omv 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux
      3. root@omv:~# dpkg -l | grep openmediavault
      4. ii openmediavault 4.1.4-1 all openmediavault - The open network attached storage solution
      5. ii openmediavault-domoticz 3.0 all Domoticz plugin for OpenMediaVault
      6. ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
      7. ii openmediavault-omvextrasorg 4.1.0 all OMV-Extras.org Package Repositories for OpenMediaVault
      8. ii openmediavault-zfs 4.0.2-1 amd64 OpenMediaVault plugin for ZFS
      9. root@omv:~# dpkg -l | grep zfs
      10. ii libzfs2linux 0.7.6-1~bpo9+1 amd64 OpenZFS filesystem library for Linux
      11. ii openmediavault-zfs 4.0.2-1 amd64 OpenMediaVault plugin for ZFS
      12. ii zfs-dkms 0.7.6-1~bpo9+1 all OpenZFS filesystem kernel modules for Linux
      13. ii zfs-zed 0.7.6-1~bpo9+1 amd64 OpenZFS Event Daemon
      14. ii zfsutils-linux 0.7.6-1~bpo9+1 amd64 command-line tools to manage OpenZFS filesystems
      15. root@omv:~# omv-confdbadm read conf.system.filesystem.mountpoint
      16. []
      Display All

      Kind regards
      Teeminus
    • Same for me
      Disk usage tab for my ZFS pool has vanished from GUI !

      and here too
      Finding the correct mntent UUID for a filesystem not in config.xml

      There is definitively a problem with ZFS plugin or something related too, and that's not the version of the kernel...

      Check if you still have the <mntent> section of your ZFS pool in config.xml. You can copy the section back, but it will be deleted at some point... don't know by what at the moment.

      Source Code

      1. root@home-server:/# diff /etc/openmediavault/config.sav /etc/openmediavault/config.xml
      2. 882,891d881
      3. < <mntent>
      4. < <uuid>864e8b70-edf9-48fb-a2fc-7fe7dbab1c2f</uuid>
      5. < <fsname>StoragePool</fsname>
      6. < <dir>/StoragePool</dir>
      7. < <type>zfs</type>
      8. < <opts>rw,relatime,xattr,noacl</opts>
      9. < <freq>0</freq>
      10. < <passno>0</passno>
      11. < <hidden>1</hidden>
      12. < </mntent>
      13. root@home-server:/# uname -a
      14. Linux home-server 4.14.0-0.bpo.3-amd64 #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14) x86_64 GNU/Linux
      15. root@home-server:/# dpkg -l | grep openmediavault
      16. ii openmediavault 4.1.4-1 all openmediavault - The open network attached storage solution
      17. ii openmediavault-backup 3.10 all backup plugin for OpenMediaVault.
      18. ii openmediavault-diskstats 4.0.2-1 all OpenMediaVault disk monitoring plugin
      19. ii openmediavault-dnsmasq 3.1.5 all OpenMediaVault dnsmasq (local DNS and DHCP server) plugin
      20. ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
      21. ii openmediavault-letsencrypt 3.4.5 all Generate free and valid SSL certificates for OMV
      22. ii openmediavault-minidlna 3.3.11 all OpenMediaVault miniDLNA (DLNA server) plugin
      23. ii openmediavault-omvextrasorg 4.1.3 all OMV-Extras.org Package Repositories for OpenMediaVault
      24. rc openmediavault-sensors 3.0 all Provides a cpu temperature monitor
      25. ii openmediavault-transmissionbt 3.0.9 all OpenMediaVault Transmission (BitTorrent client) plugin.
      26. ii openmediavault-urbackup-server 3.1 all OpenMediaVault urbackup-server plugin
      27. ii openmediavault-zfs 4.0.2-1 amd64 OpenMediaVault plugin for ZFS
      28. root@home-server:/# dpkg -l | grep zfs
      29. ii libzfs2linux 0.7.6-1~bpo9+1 amd64 OpenZFS filesystem library for Linux
      30. ii openmediavault-zfs 4.0.2-1 amd64 OpenMediaVault plugin for ZFS
      31. ii zfs-dkms 0.7.6-1~bpo9+1 all OpenZFS filesystem kernel modules for Linux
      32. ii zfs-zed 0.7.6-1~bpo9+1 amd64 OpenZFS Event Daemon
      33. ii zfsutils-linux 0.7.6-1~bpo9+1 amd64 command-line tools to manage OpenZFS filesystems
      Display All
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9

      The post was edited 1 time, last by sbocquet ().

    • Did you export / import the pool by the WebUI for any reason? With OMV 3.x there where issues after exporting / importing the pool.

      The implementation of the ZFS features in OMV is provided by the ZFS plugin. Unfortunately the ZFS functionality is not part of the basic OMV system maintaind by votdev. Therefore almost all reported issues are immediately closed because of this reason. @ryecoaaron and other mods here in the forum do their very best to solve some of the issues.

      IMHO ZFS should not be used with OMV because one have always to calculate that something will go wrong after the next update. Far to unstable for such an important thing like a file system. And to check every update in a virtual machine before installing it on the productive system is not an real option for me. And I didn´t have the time for this.

      Personally I have a running OMV 3 system with ZFS. I do not touch it. I know some of the drawbacks of the ZFS plugin and how to bypass them. But in the end I always feel uncomfortable while using ZFS with OMV.
      OMV 3.0.90 (Gray style)
      ASRock Rack C2550D4I - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1)- Fractal Design Node 304
    • The ZFS pool was created 2/3 weeks ago with the plugin.
      It runs nicely since without a problem since, and continue to... but something is removing the <mntent> section of the pool in config.xml. If I re-add the section in the OMV config file, all the problems are solved.
      In that case, I doubt that ZFS himself is in fault. That's something with the pluging itself or in OMV.
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • There are two problems with zfs:

      1 - zfs pools not being found at boot. This is not an omv issue but I'm not sure if the plugin could something to help.

      2 - fixOMVMntEnt is called whenever getObjectTree and that is called whenever the plugin's main panel is loaded or when you view details. If the pool/filesystem isn't found at boot time, this will remove the zfs mntent entries for those pools/filesystems. This is bad but not sure how to fix since zfs doesn't do things normal.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.10
      omv-extras.org 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!
    • But there maybe a thing to check like if this mntent is used by a sharedfolder to avoid to delete it if it is used?
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9

      The post was edited 1 time, last by sbocquet ().

    • sbocquet wrote:

      But there maybe a thing to check like is this mntent is used by a sharedfolder to avoid to delete it if it is used?
      That would probably help. I still think this function is dangerous. The mntent entries should be relatively static. This functions makes them very dynamic.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.10
      omv-extras.org 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!
    • The fact is that this entry is remove even after boot time... I gonna test to re-add it and go to the plugin panel to see what happens...

      EDIT : Bingo ! That's it !
      On a current working conf, no reboot...
      - I copy back the ZFS pool mount section in config.xml.
      - In the GUI, move to several place, tab, etc... except ZFS panel tab. No change in config.xml.
      - In the GUI, move to ZFS panel. config.xml is modified and the ZFS pool mount section is remove...

      Done several times
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9

      The post was edited 1 time, last by sbocquet ().

    • sbocquet wrote:

      Done several times
      I figured that was causing the problem. Thank you for confirming it. @subzero79 and I trying to come up with a good solution.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.10
      omv-extras.org 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!
    • Teeminus wrote:

      Why does the ZFS pool has to be present at boot time?
      It doesn't have to be for the plugin but it they are never found at all, that is a problem. Someone shouldn't have to manually import pools after a reboot.

      Teeminus wrote:

      Wouldn't it be sufficient to poll the pools/check for the available pools every time the device list is requested?
      Yuck. The filesystems tab updates every few seconds. If you have a lot of pools/filesystems/snapshots, it would take forever. Personally, I don't like when the filesystem is not mounted right at boot and stays that way. I wish zfs did things the Linux way.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.10
      omv-extras.org 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!
    • I think that 99% of the ZFS users mount their data pool at boot time. ZoL and the plugin does it that way, and that's the way to do things.
      That's not a USB disk thing... to play with ;) Will you play with a mdadm RAID array at each reboot ???
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • As it happens I have pools I unmount and mount while running to back up my main storage (which is mounted at boot time through OMV). Fortunately I handle all that outside of the OMV interface.

      What's still a mystery to me is (a) how my root storage zpool (mounted at boot) lost its mntent (b) why I can't for the life of me get OMV to re-recognise it. As a practical problem this is a non-issue for me, as I only ever use filesystems off the root pool so I don't need to access it from the OMV interface, but it concerns me that I may in future "lose" e.g. the owncloud filesystem, which I absolutely cannot delete and recreate or manage without.

      I should note also that while it's possible that an export/import/reboot as above might fix the issues, I'd have to remove and later recreate significant amounts of service settings in order to get to the point where I could export my NAS storage pool, so that's a far from ideal solution.
    • OK, OMV just lost track of the re-created ZFS filesystem that I made to get around this problem. This filesystem is mounted at boot time, so I cannot understand why this is happening. This is now a serious problem for me, as my owncloud installation is dependent on that partition existing. Again, it looks as though this is as a result of OMV deleting the appropriate mntent entry from config.xml. Why this filesystem and not the others? No idea. The only difference is that the other filesystems have been around for several years, but this one was created within the last month.
    • I may be going for some kind of replying to my own posts record here. Working on the basis of ellnic's suggestion, I stopped nginx and all of the services using my ZFS filesystems, ran a "zpool export" manually and then rebooted the machine. This seems to have fixed the problem for now, although I still don't have a mntent for the root of the pool.

      (Speculation: I wonder if the current tmpfile bug is causing mntents to generate spurious error conditions and then OMV is aggressively removing these filesystems as "non-existent".)
    • ZFS device(s) not listed in devices dropdown

      I haven't been able to get it to resolve this time round. It has only happened to me once or twice before and it was an age ago, OMV 3 I think. I managed to resolve by exporting/importing in one instance, and in another I do seem to remember that I typoed the ZFS mount point and it had a trailing '/', this also caused (eg. /mnt/Tank/ instead of /mnt/Tank). Changing the mount point to omit the trailing '/' fixed it. When setting up new pools, I would do this via CLI then visit OMVs ZFS tab and have it save the changes, moving forward. However, that is probably a separate issue.

      For now, I have edited the AFP config manually as I am lucky that this server doesn't reference the ZFS pools via OMV for anything else. It's only AFP via OMV (and mainly some convenience, reporting/monitoring etc) and Emby and a few other things [that are separately installed via CLI] which have their own configs and are unaffected. My pools mount at boot, it's just the mntent problem. This does seem to have happened since Kernel 4.15, but then that doesn't explain why others have experienced the issue on 4.14 etc.

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

    • OK... just my 2 cts on the problem.

      If I don't touch/click the ZFS panel, my ZFS mntent in config.xml isn't deleted and everything works fine with OMV & ZFS (stats, drop down shared folder, etc...).
      So as long as there's no patch available, just don't touch the ZFS panel in OMV and do your ZFS things with SSH.

      At the moment, that's just a GUI bug and nothing gets hurt on the ZFS background.
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9