[HOWTO] Instal ZFS-Plugin & use ZFS on OMV

    • OMV 1.0

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

    • Sin10 wrote:

      is that still up to date? Can i import ZFS pools from XigmaNAS in OMV?
      In general, that comment is pretty outdated but it depends on when the filesystem was created on XigmaNAS and what features were enabled.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • ryecoaaron wrote:

      Sin10 wrote:

      is that still up to date? Can i import ZFS pools from XigmaNAS in OMV?
      In general, that comment is pretty outdated but it depends on when the filesystem was created on XigmaNAS and what features were enabled.
      i have created a raidz1 in xigmanas with 5 HDD's (aka raid 5) - i think reading this software raid is enough, for copy this data to another disk and make a software raid via mdadm
    • Sin10 wrote:

      raulfg3 wrote:

      DISCLAIMER: Actual ZFS version on linux DO not import latest FreeNAS pool because FreeNAS use some featured Flags NOT supported by actual ZFS version of ZFSonLinux.
      is that still up to date? Can i import ZFS pools from XigmaNAS in OMV?
      actually, the actual linux version is newer than others so the problem is the reverse that when I post.

      actually 23/04/2019 a pool created on current ZFSonLinux version have some features not suported by BSD 12.

      I try to import my Data pool on BSD12 and this is the error show:
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ; ctop
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife

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

    • So basically, if I import a freenas pool into openmediavault, can I then later re-import it into freenas or will it automatically update to newer flags?

      Btw. here is my pool info, does this look like I can import it into OMV?

      Source Code

      1. root@freenas:~ # zpool get all sixer | more
      2. NAME PROPERTY VALUE SOURCE
      3. sixer size 16.2T -
      4. sixer capacity 71% -
      5. sixer altroot /mnt local
      6. sixer health ONLINE -
      7. sixer guid 6518915853434090800 default
      8. sixer version - default
      9. sixer bootfs - default
      10. sixer delegation on default
      11. sixer autoreplace off default
      12. sixer cachefile /data/zfs/zpool.cache local
      13. sixer failmode continue local
      14. sixer listsnapshots off default
      15. sixer autoexpand on local
      16. sixer dedupditto 0 default
      17. sixer dedupratio 1.00x -
      18. sixer free 4.60T -
      19. sixer allocated 11.7T -
      20. sixer readonly off -
      21. sixer comment - default
      22. sixer expandsize - -
      23. sixer freeing 0 default
      24. sixer fragmentation 17% -
      25. sixer leaked 0 default
      26. sixer feature@async_destroy enabled local
      27. sixer feature@empty_bpobj active local
      28. sixer feature@lz4_compress active local
      29. sixer feature@multi_vdev_crash_dump enabled local
      30. sixer feature@spacemap_histogram active local
      31. sixer feature@enabled_txg active local
      32. sixer feature@hole_birth active local
      33. sixer feature@extensible_dataset enabled local
      34. sixer feature@embedded_data active local
      35. sixer feature@bookmarks enabled local
      36. sixer feature@filesystem_limits enabled local
      37. sixer feature@large_blocks enabled local
      38. sixer feature@sha512 enabled local
      39. sixer feature@skein enabled local
      Display All
    • ovizii wrote:

      can I then later re-import it into freenas or will it automatically update to newer flags
      What do you mean by "newer flags"? If you're talking pool property's and the values set to those properties above, the answer is no. Other than the default values set when a pool is created which are automatic, changes to the pool's properties must be done on the command line or in the GUI. This includes upgrading the pool.

      ovizii wrote:

      if I import a freenas pool into openmediavault, can I then later re-import it into freenas
      I believe this may be dependent on how old the freenas pool is. Until recently the version of ZFS used in freenas was different from that used by Linux. The version of ZFS, in OMV, have been ZOL (ZFS On Linux) throughout. Given a potential difference, an import may not work. On the other hand, the differences may be minor where it may work. To be honest, I don't know. Since freeNAS users will be going through the conversion, perhaps the subject has been discussed in their forum.

      EDIT: According to the freeNAS ZOL post, pools "should" be interoperable between Linux and freeNAS "if" properties are not changed that exist on ZOL only. (There are no guarantees.)

      The post was edited 2 times, last by crashtest: edit ().

    • yes you can import a FreeNAS Pool and it's not updated automatically, you need to update from CLI (not recomended) if you plan to return back to BSD (FreeNAS or XigmaNAS).
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ; ctop
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife
    • @raulfg3 sorry I didn't quite understand. Did I get this right: I can import the pool and it is not automatically updated so I should just be able to return to BSD?

      One more question, before I go an try it out: Does this zfs plugin also handle encrypted pools? Of course I could decrypt the pool before switching but I would really, really like to continue with my encrypted pool. If its not possible, any alternatives to keep my data "safe" against physical theft? Some other kind of encryption although I am not quite sure where and how to implement it?
    • ovizii wrote:

      @raulfg3 sorry I didn't quite understand. Did I get this right: I can import the pool and it is not automatically updated so I should just be able to return to BSD?
      yes you can import a FreeNAS Pool and it's not updated automatically


      PD: Copy&paste from my previous post, what you don't understand
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ; ctop
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife
    • @raulfg3 sure I can explain but maybe my confusion is simply related to English being my 3rd language...
      the way I understand it, information in parenthesis () in a sentence is optional information and does not change the meaning of a sentence so if I remove your parenthesis this is what is left over and it sounds like this, hence my confusion:

      you need to update from CLI if you plan to return back to BSD.

      @pro_lamer @raulfg3 - I am coming from freenas so I am using GELI full disk encryption => ixsystems.com/documentation/fr…1/storage.html#encryption

      I can decrypt the pool before moving to OMV but I would really, really like some sort of encryption. Is there a solution or some planned solution or an alternative?

      Also, I'm curious what the problem is with supporting encryption, I read that native encryption is present in ZOl since 0.8-RC1 or is that a different type of encryption? Or is it simply that the ZFS plugin (GUI) doesn't yet support encryption?

      Thanks for any pointers and info guys!
    • ovizii wrote:

      I read that native encryption is present in ZOl since 0.8-RC1 or is that a different type of encryption?
      Native means it is part of zfs. Any other encryption is on top of or underneath zfs. freebsd and linux offer different types of encryption that I am fairly certain are not compatible (LUKS on linux vs whatever freebsd offers). Once freebsd and linux are using zol 0.8, I would think encrypted zfs would compatible on either.

      ovizii wrote:

      s there a solution or some planned solution or an alternative?
      OMV has a LUKS plugin now. You could use zfs on top of it.

      ovizii wrote:

      I'm curious what the problem is with supporting encryption,
      No problem. OMV uses the version of zfs in the Debian repos and 0.8 is not even released yet.

      ovizii wrote:

      Or is it simply that the ZFS plugin (GUI) doesn't yet support encryption?
      It doesn't need to once zfs 0.8 is available. You should be able to enable it.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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 plugin doesn’t support encryption in zfs. Bear in mind that encryption in zol I atm in a rc version, not the current one. If you need encryption only solution I see is to use zvols formatted as luks, then you can use ext4 or xfs on top.
      Other option destroy the pool, format each disk with luks, then create pool with the devices.

      If I were you I would wait.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Hello,
      I have a problem with zfs. Could anybody help?

      Source Code

      1. Linux smallnas 4.19.0-0.bpo.4-amd64 #1 SMP Debian 4.19.28-2~bpo9+1 (2019-03-27) x86_64 GNU/Linux
      2. openmediavault 4.1.22-1 (Arrakis)
      I`ve intalled omv setup and it works without any problem.
      Yesterday I tried open dir and system stuck.
      I`ve checked zpool and sow scrub running.
      In several min system hung.
      I`ve done hardreset. And system hung with" job import zfs pools from cache". I`ve reload to old kernal and disable zfs-import-cache.service. And reload to default kernal.
      But if I try manualy import zpool system hungs with message


      If I try reboot I`ve got


      I`ve uninstalled/installed zfs plugin, its not help.

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

    • First, I'll state up front, I have no experience with this kind of error.
      With that said, did you see the first line of the first screen shot? Kernel Bug at /build/-----/linux-4.19.28/drivers/ata/sat..... ?

      Do you have OS backup from a time when all functioned? If the answer is "yes", I'd restore the backup. If the answer is "no", I'd consider setting your current boot drive aside and rebuilding. It's a guess, but I'm of the belief that this might not be fixable. Further, I'd be reluctant to work on the pool with an OS that may be corrupt.


    • [HOWTO] Instal ZFS-Plugin & use ZFS on OMV

      Did you try to boot another kernel than 4.19.28?

      As an alternative you can try the Proxmox kernel. Have a look at „System -> OMV-Extras -> Kernel -> Install Proxmox kernel“.

      Regards Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - tvos | android tv | libreelec | win10 | kodi krypton
      frontend hardware - appletv 4k | nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2
      -------------------------------------------
      backend software - debian | openmediavault | latest backport kernel | zfs raid-z2 | docker | emby | unifi | vdr | tvheadend | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------
    • No one advice works :(
      Install new system with kernel 4.14 but can`t install headers for it.
      When upgrade kernel to 4.19 have same error.
      Now try compile kernel 4.14 from sources.

      I have one more storage on openmediavault with old kernel. Can I take it and install to new storage? In /var/cache/apt/archives deb is missing.

      I found 4.14.0-0.bpo.3 deb files in old backup but the same error when I try import zpool.

      Display Spoiler

      Brainfuck Source Code

      1. May 16 14:59:01 smallnas kernel: [ 89.324086] ------------[ cut here ]------------
      2. May 16 14:59:01 smallnas kernel: [ 89.324344] invalid opcode: 0000 [#1] SMP PTI
      3. May 16 14:59:01 smallnas kernel: [ 89.324472] Modules linked in: softdog cpufreq_userspace cpufreq_conservative cpufreq_powersave iTCO_wdt snd_hda_codec_hdmi iTCO_vendor_support ppdev amdkfd nouveau snd_hda_intel coretemp mxm_wmi radeon wmi video snd_hda_codec lpc_ich mfd_core evdev snd_hda_core ttm snd_hwdep kvm drm_kms_helper irqbypass pcspkr serio_raw snd_pcm snd_timer drm snd soundcore i2c_algo_bit sg i5000_edac rng_core i5k_amb shpchp parport_pc parport button zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) sunrpc ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb crypto_simd cryptd glue_helper aes_x86_64 btrfs zstd_decompress zstd_compress xxhash raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod
      4. May 16 14:59:01 smallnas kernel: [ 89.326492] ata_generic sd_mod ahci ata_piix sata_mv libahci uhci_hcd ehci_pci i2c_i801 ehci_hcd usbcore libata e1000e usb_common ptp pps_core scsi_mod
      5. May 16 14:59:01 smallnas kernel: [ 89.326900] CPU: 2 PID: 154 Comm: scsi_eh_7 Tainted: P O 4.14.0-0.bpo.3-amd64 #1 Debian 4.14.13-1~bpo9+1
      6. May 16 14:59:01 smallnas kernel: [ 89.327201] Hardware name: Supermicro X7DB8/X7DB8, BIOS 2.1a 12/20/2008
      7. May 16 14:59:01 smallnas kernel: [ 89.327398] task: ffff9945442de080 task.stack: ffffad2d439b0000
      8. May 16 14:59:01 smallnas kernel: [ 89.327581] RIP: 0010:mv_qc_prep+0x1e7/0x200 [sata_mv]
      9. May 16 14:59:01 smallnas kernel: [ 89.327733] RSP: 0018:ffffad2d439b3a40 EFLAGS: 00010006
      10. May 16 14:59:01 smallnas kernel: [ 89.327892] RAX: ffff994544baa400 RBX: ffff994544270000 RCX: 0000000000000047
      11. May 16 14:59:01 smallnas kernel: [ 89.328096] RDX: ffff994544baa40a RSI: ffff994544baa400 RDI: ffff994544271d50
      12. May 16 14:59:01 smallnas kernel: [ 89.328300] RBP: 0000000000000001 R08: 0000000000000008 R09: 0000000000000000
      13. May 16 14:59:01 smallnas kernel: [ 89.328504] R10: ffffad2d439b3b50 R11: ffff99454fc21280 R12: ffff994544271e80
      14. May 16 14:59:01 smallnas kernel: [ 89.328708] R13: ffff99454b4c50a0 R14: ffff994544271d50 R15: 0000000000000001
      15. May 16 14:59:01 smallnas kernel: [ 89.328913] FS: 0000000000000000(0000) GS:ffff99454fc80000(0000) knlGS:0000000000000000
      16. May 16 14:59:01 smallnas kernel: [ 89.329154] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      17. May 16 14:59:01 smallnas kernel: [ 89.329320] CR2: 00007f5585898160 CR3: 0000000819d9a000 CR4: 00000000000006e0
      18. May 16 14:59:01 smallnas kernel: [ 89.329524] Call Trace:
      19. May 16 14:59:01 smallnas kernel: [ 89.329625] ata_qc_issue+0x122/0x2a0 [libata]
      20. May 16 14:59:01 smallnas kernel: [ 89.329767] ata_exec_internal_sg+0x338/0x640 [libata]
      21. May 16 14:59:01 smallnas kernel: [ 89.329926] ata_exec_internal+0x5f/0x90 [libata]
      22. May 16 14:59:01 smallnas kernel: [ 89.330069] ata_read_log_page.part.36+0x19b/0x1d0 [libata]
      23. May 16 14:59:01 smallnas kernel: [ 89.330244] ata_eh_analyze_ncq_error+0xe0/0x300 [libata]
      24. May 16 14:59:01 smallnas kernel: [ 89.330409] ata_eh_link_autopsy+0x97/0xab0 [libata]
      25. May 16 14:59:01 smallnas kernel: [ 89.330567] ? check_preempt_curr+0x54/0x90
      26. May 16 14:59:01 smallnas kernel: [ 89.330697] ? ttwu_do_wakeup+0x19/0x140
      27. May 16 14:59:01 smallnas kernel: [ 89.330829] ata_eh_autopsy+0x26/0xd0 [libata]
      28. May 16 14:59:01 smallnas kernel: [ 89.330968] sata_pmp_error_handler+0x38/0x9b0 [libata]
      29. May 16 14:59:01 smallnas kernel: [ 89.331129] ? update_curr+0x10c/0x1a0
      30. May 16 14:59:01 smallnas kernel: [ 89.331245] ? lock_timer_base+0x74/0x90
      31. May 16 14:59:01 smallnas kernel: [ 89.331377] ata_scsi_port_error_handler+0x428/0x730 [libata]
      32. May 16 14:59:01 smallnas kernel: [ 89.331557] ? scsi_try_target_reset+0x80/0x80 [scsi_mod]
      33. May 16 14:59:01 smallnas kernel: [ 89.331720] ata_scsi_error+0x91/0xc0 [libata]
      34. May 16 14:59:01 smallnas kernel: [ 89.331859] scsi_error_handler+0xd8/0x5d0 [scsi_mod]
      35. May 16 14:59:01 smallnas kernel: [ 89.332009] kthread+0xfc/0x130
      36. May 16 14:59:01 smallnas kernel: [ 89.332115] ? scsi_eh_get_sense+0x260/0x260 [scsi_mod]
      37. May 16 14:59:01 smallnas kernel: [ 89.332274] ? kthread_create_on_node+0x70/0x70
      38. May 16 14:59:01 smallnas kernel: [ 89.332414] ret_from_fork+0x1f/0x30
      39. May 16 14:59:01 smallnas kernel: [ 89.332531] Code: 80 f9 ca 0f 85 55 ff ff ff 0f b6 4f 2b 48 8d 50 0c 80 cd 12 66 89 48 0a e9 4d ff ff ff f3 c3 c6 47 35 30 c3 0f ff e9 a6 fe ff ff <0f> 0b 48 83 e2 df 48 89 57 20 e9 6d fe ff ff 66 2e 0f 1f 84 00
      40. May 16 14:59:01 smallnas kernel: [ 89.333298] ---[ end trace fe452eba46f69d03 ]---
      Display All


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

    • du_ku wrote:

      No one advice works
      Try the proxmox kernel from the omv-extras kernel tab. No compiling needed.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!