BasWeg

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

7 Neutral

About BasWeg

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For me it does not work. All of my unassigned SSDs are configured within /boot/config/Smart-one.cfg But the notification is related to the default temp for HDDs
  2. No, you need to execute the command for every dataset inside the pool. https://forums.unraid.net/topic/41333-zfs-plugin-for-unraid/?do=findComment&comment=917605 I'm using following script in UserScripts to be executed at "First Start Array only" #!/bin/bash #from testdasi (https://forums.unraid.net/topic/41333-zfs-plugin-for-unraid/?do=findComment&comment=875342) #echo "[pool]/[filesystem] /mnt/[pool]/[filesystem] zfs rw,default 0 0" >> /etc/mtab #just dump everything in for n in $(zfs list -H -o name) do echo "$n /mnt/$n zfs rw,default 0 0" >&
  3. Which version of ZFS do you have working with VM and Dockers now?
  4. The original smb reference is pretty old. And one topic later testdasi had a solution
  5. to be honest, no. I've nothing to do with linux internal stuff
  6. Hi, please check this post This is the workaround, I'm using. best regards Bastian
  7. So, what's about the other .img files, used for VMs and so on? Are there any issues? I'm still at RC1 with zfs-2.0.0-1
  8. All this samba staff is pretty well explained in this referenced topic https://forum.level1techs.com/t/zfs-on-unraid-lets-do-it-bonus-shadowcopy-setup-guide-project/148764
  9. So, at the moment it is better not to update? I'm still on RC1 with ZFS 2.0.0
  10. yep, that is correct. The dashboard is fine... the notification is the trouble
  11. In my "smart-one.cfg", I can see my configuration for the unassigned disks I use with ZFS [Samsung_SSD_860_EVO_250GB_xxx] hotTemp="55" maxTemp="65" [Samsung_SSD_860_EVO_250GB_xxx] hotTemp="55" maxTemp="65" [Samsung_SSD_860_EVO_500GB_xxx] hotTemp="55" maxTemp="65" [Samsung_SSD_860_EVO_250GB_xxx] hotTemp="55" maxTemp="65" [Samsung_SSD_970_EVO_Plus_1TB_xxx] hotTemp="55" maxTemp="65" but the unraid system doesn't care and complains all the time using the default settings.
  12. So, use_unstable_build is not needed any more to get version 2.0.0?
  13. Thanks for the hint! I've made a user script with following content in order to run after first array start: #!/bin/bash #from testdasi (https://forums.unraid.net/topic/41333-zfs-plugin-for-unraid/?do=findComment&comment=875342) #echo "[pool]/[filesystem] /mnt/[pool]/[filesystem] zfs rw,default 0 0" >> /etc/mtab #just dump everything in for n in $(zfs list -H -o name) do echo "$n /mnt/$n zfs rw,default 0 0" >> /etc/mtab done
  14. Is it possible to get rid of / waiver this error/warning? I know that I'm using an unstable version, and everytime after a reboot this shows up and shocks me. 🙃