Jump to content

Tufinger

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by Tufinger

  1. On 12/13/2022 at 6:10 AM, Brandon_K said:


    I'm still having some issues that I've yet to be able to solve.

    What I want is pretty simple; when the cache is >70% full, move everything (all "cache: yes" shares) to the array.  I've been playing with options and I can get it to move, but it only moves data that is above 70% and leaves everything else on cache. I'm mostly just trying to avoid spinning up disks every day if I don't have to.  It usually takes 3-5 days to get my cache disk to ~70% utilization.

    My settings are below;

     

    
    No
     *Note that setting this to yes effectively disables this plugin
    
    Priority for mover process: Normal
    Priority for disk I/O: Normal
    Only move at this threshold of used cache space: 70 %
    Move files off cache based on age? No
    Move files that are greater than this many days old: 1
    Use CTIME: No
    Move files based on minimum size? No
    Move files that are larger than this size (In M). 1
    Move files off cache based on sparsenes? No
    Move files that are greather than this sparseness: .1
    Ignore files listed inside of a text file: No
    File list path:
    Ignore file types: No
    comma seperated list of file types:
    Let scheduled mover run during a parity check / rebuild: No
    Force turbo write on during mover: No
    Log when not moving due to rules: Yes
    Force move of all files on a schedule: No
    Cron Schedule to force move all of files:
    Allow force mover schedule to run during a parity check/rebuild: No
    Ignore All hiden files and directories: No
    Script to run before mover (No checks, always runs):
    Script to run after mover (No checks, always runs):
    Move All from Cache-Yes shares when disk is above a certain percentage: Yes
    Move All from Cache-yes shares pool percentage: 75 %
    Move Now button follows plug-in filters: Yes
    Test Mode: No

     

    What am I missing or doing wrong?

    same problem here

  2. Hallo,

    kann mir einer sagen, was das zu bedeuten hat?

    Diese Meldung ist mir seit dem letzten Update aufgefallen und taucht immer sporadisch auf.

    Das System ist seither auch zwei mal komplett hängen geblieben. Vielleicht besteht ja ein zusammenhang damit.

     

    Viele Grüße

    1626149090_Screenshot(135).thumb.png.05231be6d0bbf65b7372b90d76c1a7d0.png

     

    Quote

    Nov  7 19:01:17 Server kernel: ------------[ cut here ]------------
    Nov  7 19:01:17 Server kernel: WARNING: CPU: 5 PID: 21869 at net/netfilter/nf_conntrack_core.c:1205 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
    Nov  7 19:01:17 Server kernel: Modules linked in: tcp_diag udp_diag inet_diag xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth macvlan xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype br_netfilter xfs dm_crypt dm_mod dax md_mod nct6775 nct6775_core hwmon_vid jc42 efivarfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables 8021q garp mrp bridge stp llc ipv6 e1000e ixgbe xfrm_algo mdio i915 iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm intel_wmi_thunderbolt wmi_bmof mxm_wmi drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm aesni_intel crypto_simd cryptd ahci rapl intel_gtt
    Nov  7 19:01:17 Server kernel: intel_cstate agpgart corsair_psu libahci i2c_core intel_uncore syscopyarea sysfillrect sysimgblt fb_sys_fops video wmi backlight acpi_pad button unix [last unloaded: e1000e]
    Nov  7 19:01:17 Server kernel: CPU: 5 PID: 21869 Comm: kworker/5:3 Not tainted 5.19.14-Unraid #1
    Nov  7 19:01:17 Server kernel: Hardware name: System manufacturer System Product Name/MAXIMUS VIII HERO, BIOS 3802 03/15/2018
    Nov  7 19:01:17 Server kernel: Workqueue: events macvlan_process_broadcast [macvlan]
    Nov  7 19:01:17 Server kernel: RIP: 0010:__nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
    Nov  7 19:01:17 Server kernel: Code: c6 48 89 44 24 10 e8 ff e2 ff ff 8b 7c 24 04 89 da 89 c6 89 04 24 e8 78 e6 ff ff 84 c0 75 a2 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 38 de ff ff e8 4e e3 ff ff e9 7e 01
    Nov  7 19:01:17 Server kernel: RSP: 0018:ffffc900001fcda0 EFLAGS: 00010202
    Nov  7 19:01:17 Server kernel: RAX: 0000000000000188 RBX: 0000000000000000 RCX: 4385cd10564f24a8
    Nov  7 19:01:17 Server kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffa080db24
    Nov  7 19:01:17 Server kernel: RBP: ffff8881ebc07800 R08: 321c26b8117c6d44 R09: 8ab42f732c546932
    Nov  7 19:01:17 Server kernel: R10: 3499455a17b9962a R11: df75e9cf7fbce80f R12: ffffffff826e7480
    Nov  7 19:01:17 Server kernel: R13: 000000000001ee39 R14: ffff88821e06c600 R15: 0000000000000000
    Nov  7 19:01:17 Server kernel: FS:  0000000000000000(0000) GS:ffff88845ed40000(0000) knlGS:0000000000000000
    Nov  7 19:01:17 Server kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Nov  7 19:01:17 Server kernel: CR2: 0000145d4c1b4000 CR3: 000000000400a001 CR4: 00000000003706e0
    Nov  7 19:01:17 Server kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Nov  7 19:01:17 Server kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Nov  7 19:01:17 Server kernel: Call Trace:
    Nov  7 19:01:17 Server kernel: <IRQ>
    Nov  7 19:01:17 Server kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack]
    Nov  7 19:01:17 Server kernel: nf_hook_slow+0x3a/0x96
    Nov  7 19:01:17 Server kernel: ? ip_protocol_deliver_rcu+0x164/0x164
    Nov  7 19:01:17 Server kernel: NF_HOOK.constprop.0+0x79/0xd9
    Nov  7 19:01:17 Server kernel: ? ip_protocol_deliver_rcu+0x164/0x164
    Nov  7 19:01:17 Server kernel: __netif_receive_skb_one_core+0x68/0x8d
    Nov  7 19:01:17 Server kernel: process_backlog+0x8c/0x116
    Nov  7 19:01:17 Server kernel: __napi_poll.constprop.0+0x28/0x124
    Nov  7 19:01:17 Server kernel: net_rx_action+0x159/0x24f
    Nov  7 19:01:17 Server kernel: __do_softirq+0x126/0x288
    Nov  7 19:01:17 Server kernel: do_softirq+0x7f/0xab
    Nov  7 19:01:17 Server kernel: </IRQ>
    Nov  7 19:01:17 Server kernel: <TASK>
    Nov  7 19:01:17 Server kernel: __local_bh_enable_ip+0x4c/0x6b
    Nov  7 19:01:17 Server kernel: netif_rx+0x52/0x5a
    Nov  7 19:01:17 Server kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
    Nov  7 19:01:17 Server kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
    Nov  7 19:01:17 Server kernel: process_one_work+0x1a8/0x295
    Nov  7 19:01:17 Server kernel: worker_thread+0x18b/0x244
    Nov  7 19:01:17 Server kernel: ? rescuer_thread+0x281/0x281
    Nov  7 19:01:17 Server kernel: kthread+0xe4/0xef
    Nov  7 19:01:17 Server kernel: ? kthread_complete_and_exit+0x1b/0x1b
    Nov  7 19:01:17 Server kernel: ret_from_fork+0x1f/0x30
    Nov  7 19:01:17 Server kernel: </TASK>
    Nov  7 19:01:17 Server kernel: ---[ end trace 0000000000000000 ]---

     

  3. Mit dieser Anleitung hat es nach langem rumprobieren geklappt.

    https://kmwoley.com/blog/controlling-case-fans-based-on-hard-drive-temperature/

    https://forums.unraid.net/topic/87947-control-fan-speed-based-on-drive-temp/

     

    Wobei der Teil ab "Figure out which controls what" nicht nötig ist, wenn man die entsprechenden Einstellungen in der UI von dem Fan Speed Plugin macht.

    Die ganzen Start Befehle in der GO Datei kann man auch weg lassen, wenn man einfach folgenden Befehl in GO schreibt:

     

    # Start Autofan
    /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'restart'

     

    So sieht es bei mir komplett aus:

    Quote

    #Temps
    modprobe coretemp
    modprobe nct6775

     

    # Start Autofan
    /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'restart'

     

    Und so hab ich es in der syslinux.cfg:

    Quote

    kernel /bzimage
    append pcie_acs_override=downstream,multifunction modprobe.blacklist=i2c_i801,i2c_smbus acpi_enforce_resources=lax initrd=/bzroot

     

    • Thanks 1
  4. Das Problem habe ich jedes mal, wenn ich eine Windows VM installiere.

    Meine Lösung (wie vielleicht schon beschrieben) :

    1. Treiber deinstallieren und löschen.

    2. den Geräte Manager aktualisieren.

    3. Treiber installieren und die virtio cd auswählen ( OHNE das System neuzustarten)

     

    So funktioniert es bei mir immer.

    • Like 1
    • Thanks 1
×
×
  • Create New...