• Posts

  • Joined

  • Last visited

Everything posted by 188pilas

  1. I just tried with 6.9.0-rc2 and still same error. unable to pass through Mellanox card.
  2. Thanks you are correct!! Let me test out changing the config on one of the 10gb cards.
  3. I updated to beta35 but seems only the mstflint tool is included...or did I miss something?
  4. does the kernel include the mlxconfig tool as well? or just the mstflint to burn firmware?
  5. k cool that makes perfect sense. I installed 0.8.5 and my zfs pools are theere. I also had an issue with ZnapZend not working but it just needed perl-5.32.0-x86_64-1.txz from nerdpack.
  6. are you able to install zfs 0.8.4 with beta30? I ran the build twice and seems that it excludes the zfs install.
  7. I am also having this issue passing the Mellanox card to a VM. Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0)
  8. I am going to build one with Unraid 6.8.3 with ZFS 0.8.4...I also have Mellanox Technologies MT26448 ConnectX EN 10GigE and will try to build with Melanox Firmware Tools. Going to backup my pool and boot drive...I do not have a cache drive and I read that the builds are /mnt/cache/appdata/kernel/output-VERSION by default...can we manually change that? or do I need to put a cache drive temporarily?
  9. @ich777 thanks for this helpful tool...have you tried using ZFS ZVOL and attaching that to iSCSI target? I would like to test out the performance compared to an SMB for gaming library.
  10. Just in case...I was able to accomplish this using https://github.com/Red5d/docker-autocompose.
  11. @juan11perez I saw the stacks option in portainer, but it appears to create dockers from an already existing docker-compose file. I would like to do the reverse...create a docker compose file from all my dockers running on unraid with their respective values. Thanks for the suggestion though.
  12. Thanks!!! Let me give this a try.
  13. Hey all - does anyone have any suggestions on auto generating a docker compose file from an existing unraid setup? I have several dockers running with custom port mapping along with volume mapping and would like to have a docker-compose file of that setup. Thanks!!!
  14. Weird part is the it works on the previous beta release of unraid. Sent from my SM-G955U using Tapatalk
  15. It was created in Unraid with the plugin a while back. Sent from my SM-G955U using Tapatalk
  16. anyone having an issue with ZFS on latest beta 6.9.0-beta25 ? I tried to import and have the below error due to unsupported feature. root@Omega:/# zpool import omega This pool uses the following feature(s) not supported by this system: com.delphix:log_spacemap (Log metaslab changes on a single spacemap and flush them periodically.) All unsupported features are only required for writing to the pool. The pool can be imported using '-o readonly=on'. cannot import 'omega': unsupported version or feature
  17. Awesome! Thanks Sent from my SM-G955U using Tapatalk
  18. k still running into some issues...-bash: /usr/local/bin/znapzend: /usr/bin/perl: bad interpreter: No such file or directory when I run znapzend --logto=/var/log/znapzend.log --daemonize. below are some logs. root@Omega:~# cat /var/log/syslog | head Mar 9 20:41:30 Omega kernel: microcode: microcode updated early to revision 0x1d, date = 2018-05-11 Mar 9 20:41:30 Omega kernel: Linux version 4.19.107-Unraid (root@Develop) (gcc version 9.2.0 (GCC)) #1 SMP Thu Mar 5 13:55:57 PST 2020 Mar 9 20:41:30 Omega kernel: Command line: BOOT_IMAGE=/bzimage vfio-pci.ids=8086:2934,8086:2935,8086:293a, vfio_iommu_type1.allow_unsafe_interrupts=1 isolcpus=6-7,14-15 pcie_acs_override=downstream initrd=/bzroot Mar 9 20:41:30 Omega kernel: x86/fpu: x87 FPU will use FXSAVE Mar 9 20:41:30 Omega kernel: BIOS-provided physical RAM map: Mar 9 20:41:30 Omega kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable Mar 9 20:41:30 Omega kernel: BIOS-e820: [mem 0x0000000000100000-0x000000009f378fff] usable Mar 9 20:41:30 Omega kernel: BIOS-e820: [mem 0x000000009f379000-0x000000009f38efff] reserved Mar 9 20:41:30 Omega kernel: BIOS-e820: [mem 0x000000009f38f000-0x000000009f3cdfff] ACPI data Mar 9 20:41:30 Omega kernel: BIOS-e820: [mem 0x000000009f3ce000-0x000000009fffffff] reserved root@Omega:~# cat /var/log/znapzend.log | head cat: /var/log/znapzend.log: No such file or directory root@Omega:~# ls -la /boot/config/plugins/unRAID6-ZnapZend/auto_boot_on -rw------- 1 root root 0 Mar 9 20:58 /boot/config/plugins/unRAID6-ZnapZend/auto_boot_on root@Omega:~# ps aux | grep -i znapzend root 18502 0.0 0.0 3912 2152 pts/1 S+ 21:06 0:00 grep -i znapzend
  19. @steini84 I was able to get it working by deleting the old /boot/config/plugins/unRAID6-ZnapZend folder and downloading a new one.
  20. @steini84 I received the below error when updating to stable 6.8.3 ...any suggestions? going back to 6.7.2 for now.
  21. I was able to resolve my issue. It had to do with an error in znapzend not having a matching dataset between source and one of the destinations. I ran znapzendztatz and then deleted the snapshot on destination along with the dataset and then ran delete on znapzend schedule on source dataset and then recreated everything from scratch and its working fine now. thanks! https://github.com/oetiker/znapzend/issues/303
  22. hello steini84 - I have this plugin installed and a couple of jobs for some datasets however I have noticed that the jobs are not running running automatically. I usually have to run the job using the "znapzend --debug --runonce=zpool/dataset" command and it will run successfully. Below is an example of one of the schedules that I have setup: znapzendzetup create --recursive SRC '1week=>12hour' zpool/dataset DST:a '1week=>24hour' root@192.168.XX.XX:zpool/dataset DST:b '1week=>24hour' root@192.168.XX.XX:zpool/dataset I can schedule a user script to run at a schedule to run the znapzend --debug --runonce command; however just wondering if there were any other steps. I setup the touch auto_boot_on file. Thanks!
  23. Cool thanks. Let me give that a try.