Nirin

I'm having an odd issue with the backup of the Plex appdata folder : [05.02.2026 10:16:18][ℹ️][plex] tar creation failed! Tar said: tar: /mnt/user/appdata/plex/Plex Media Server/Plug-in support/Databases/com.plexapp.plugins.library.blobs.db-wal: file changed as we read it I already have all the recommended items and paths excluded, the issue seems to be that one of the database files is always altered during the backup. I tried making it so that plex is shutdown for backup, but this plugin refuses to allow that (shows an error message saying it's recommended not to shut down plex and keeps it running). I considered adding that blob to the exclusions, but it's a database file so I assume it's going to be a pain if I don't have a backup of it if I ever want to recover the plex install later! I've also tried setting the backup time to a time of day when noone is using plex, but that seems to make no difference the database backup still fails.

(Hoping this is the right subforum for this, as it's currently run as a userscript) StudioNirin/PlexCache-R Some of you may recognise this, as there has been an old version of this from a few years back by Brimur and Bexem. That ended up getting archived, and Brimur was happy to let me try and fix some bugs and expand the functionality a bit. After I released V1, I then got some amazing help from someone called Brandon and we have managed to pump out a whole slew of upgrades. Some of you may also recognise this because v1 and v2 were already released on the unraid subreddit... I just kept forgetting to actually make a post here lol. Intro/Recap: Automate Plex media management: Efficiently transfer media from the On Deck/Watchlist to the cache, and seamlessly move watched media back to their respective locations. An updated version of the "PlexCache-Refactored" script with various bugfixes and improvements. Hopefully fixed and improved anyway, time will tell! PlexCache efficiently transfers media from the On Deck/Watchlist to the cache and moves watched media back to their respective locations. This Python script reduces energy consumption by minimizing the need to spin up the array/hard drive(s) when watching recurrent media like TV series. It achieves this by moving the media from the OnDeck and watchlist for the main user and/or other users. For TV shows/anime, it also fetches the next specified number of episodes. V2.1.1 Update Notes: I'll write a bit of a shortlist version of the additions here, though we made a LOT of changes in this edition so even the changelog is probably missing a few things. Check the releases page notes for more details on each of these. But here goes: .plexcached Backup System When files are moved to cache, the original array file is renamed to filename.plexcached instead of being deleted. This reduces unnecessary file writes, and data loss if the cache drive fails. 2. OAuth PIN-Based Authentication Replaces manual token entry with Plex's official PIN-based OAuth. 3. Cache Retention Period 4. Watchlist Retention Period 5. Cache Size Limit New cache_limit setting to cap total cache usage. 6. Updated Setup Wizard Auto-detects missing settings and prompts to add them 7. Unraid Mover Exclusion File (manual custom entries) There is now a new generated file (unraid_mover_exclusions.txt) which allows for manually-entered custom exclusion links. 8. Multi-Path Mapping Support 9. Smart Cache Eviction System Cached files are now rated using a priority system, so that if the cache size limit is reached files will be removed based on age/priority of the individual files. Plus a bunch of debug and logging improvements. And as I say, probably a few other things we forgot to document. Migration should be pretty straightforward. However there are some of the usual recommendations: Make a backup of your old Plexcache-R folder. This is mostly so you can revert back if you have any issues. Just zip the folder or copy it somewhere else temporarily. Download the new files, and overwrite the old versions Run the setup script. This will look for and find missing settings and add them to your existing settings.json file. When it's finished, run the Plexcache-R script. And ... that's it, should just work at this point. As always, at your own risk, no responsibility etc. But if you have any issues please do post them on the github and we will do our best to help you out. We have been running this new version for a couple weeks now and haven't run into any issues as of yet, but there's always going to be something! StudioNirin/PlexCache-R There's already a lot of plans for v3 which will be a big update, but we don't have a release timeline yet and it's very much experimental. V2 however seems to be working well for the people that have reported back on reddit and on the github. Good luck!

I had a warning from unraid saying one of my disks was getting full, which was weird cos I should have had several TB of empty space on that disk. Turns out it was because the appdata backups were taking up huge amounts of space. I have it set to delete all backups older than 7 days, but I instead have several months worth of backups in the folder lol. I'm manually deleting them now, but is this a known issue and is there a fix?

Great plugin, really handy. I had the 'file activity' one installed before and it never worked correctly. Just a bit of feedback - when I select to order the log "by date", it doesn't actually sort the list of entries by date. It still sorts them by either share or disk first, and just sorts those by date/time. Which is fine, it does make sense, but there's no way to quickly scan between shares and disks as it's just a list of like 50 pages and the different shares/disks are in a random place. I assume the intended method (only one I've found anyway) is by turning on and off individual 'group' filters, but that seems like a bit of a workaround rather than a UX method. Not sure on a better solution, maybe have a 'front page' which shows the most recent 20 entries from each share/disk, so that info is all on one page, and then have the existing sort/filters database logs as the next page or a separate tab... I dunno, was just a thought, as I mostly use this to check for things causing my disks to spin up unecessarily etc so I only need to see recent files for each, rather than all the files for each sequentially. Regardless, the plugin works great as it is, thanks for putting the work in!

Does this container actually get fixes/updates regularly? I've noticed the icon for it has been broken for months now, and it still seems to have the same issue as a long time ago where it installs with incorrect permissions and so doesn't actually run without editing those... Otherwise I'll try the other container that seems to have been released.

Another bug to add to the pile - If "normal governer" is set to balanced power, then the "power save governer" can only be set to balanced power too. If I try and change it to power save, and hit apply, it just changes back to balanced power. However if I change the normal governer to something else like balanced-performance, then the power saving governer will change to power save. And can't be changed to balanced-power at all. Very weird behaviour. Something is conflicting somewhere.

I recently asked the exact same question. The only answer I got here was "test it for yourself". Which was less than helpful. However as the dev puts the 'balanced power' one in the 'power saving' menu, and not the balanced performance one, the assumption is that the descriptions are the wrong way around. Doubt it'll ever get fixed, dev doesn't seem active on here.

I mean I'd have to run like a week of 24/7 tests to figure out the difference, as the differences are going to be pretty minor either way except in long-term averages. Or I could just ask the dev which AMD profile is lined up with which power state, because AMD already did all that testing so there's no need for me to repeat the work unnecessarily. Considering the dev has 'balanced power' in the "power save cpu profile" dropdown, I assume that the titles are correct, and that its the descriptions that are backwards.

Hi sorry, just to confirm... are you just saying that because of the description (which doesn't match the title), or are you saying that because you know that's the right one, and the description is correct, but the title is wrong? Cos the titles don't match the descriptions, so one or the other is definitely incorrect lol. Going from 'max power saving' to 'max performance' should be: Power Save Balance_Power Balance_Performance Performance But you seem to be saying that balance_performance is more power saving than balance_power? Edit: Looking at other sources of the amd pstate drive, it does seem that 'balance_power' should be the more power efficient version compared to 'balance_performance', however I don't know if tips n tweaks has gotten it backwards or has a typo or something.

According to the help tooltip, it says if you set one to 'not used' it should hide that on the toolbar. However as you can see, it still displays it, just with a "--" so is there some way to remove that?

"Balanced Performance" - Set all CPUs frequency scaling to balanced_performance. Balances performance and power usage, with a slight bias toward efficiency. "Balanced Power" - Set all CPUs frequency scaling to balanced_power. Balances power and performance, but with a slight performance bias. This confused me a little, as the description has the 'Performance' one being biased towards efficiency, and the "power" one is biased to performance lol. Are these descriptions accidentally reversed? I am looking for the setting which is on the 'power saving' side of balanced.

I seem to be having the "Docker volume mount not detected" issue on my NVME drives (image attached). I have already checked here, and the 'solution' says to add a path to the docker (also image attached). However while that does trigger a rescan of the drives when booting up diskspeed, the error doesn't change. All four of the NVME drives are still erroring.

Only learned this was a thing today, really surprised that Unraid restricts the ability to use a useful drive health tool. It should 100% just automatically not spin down a drive if there's a smart test running. How was this not a day1 setting?

Came here with the same issue. I'm on 7.1.2, updated yesterday from v6.something, and today I don't seem to have the server in windows network anymore. I also can't find it by looking for \\server-name anymore. I can find it by using \\server-ip so that's fine at least, but it's a bit of a pain. I'll try turning off the docker option of host access and see if that fixes it but that may not be a long term solution if it breaks other functionality with my containers (I have no memory over whether it was needed for any of my containers or custom networks).

I'm trying to get the global exclusions working, but I had some issues, copying the ones in the example didn't work. I eventually figured it out - while the example says to format it like this: logs, log, *.png, .cache (etc etc, using comma and space to break up each one) This doesn't actually work. It only works if you put each entry in a new line. I assume this is a new change, as the per-container exclusions seem to work that way (new lines) by default (if you manually select the folders with the file-browser) so I guess the example text didn't get updated (?) Edit: I'll also add that because of the way the text box works, it currently also means that when you load the settings page it only shows the first two entries and doesn't indicate that there are a whole bunch more (you have to manually enlarge the text box to see them). I don't know if this is an unraid limitation or not, but if there's a way to fix it then it would be better!

It was just those same errors over and over again.

Sep 5 18:47:39 Hex kernel: RIP: 0010:sbitmap_get+0xb/0xd1 Sep 5 18:47:39 Hex kernel: Code: f0 72 16 85 f6 89 f7 74 07 e8 e1 ff ff ff 89 c7 48 8b 43 18 65 89 38 89 f8 5b c3 cc cc cc cc 41 57 41 56 41 55 41 54 55 53 51 <48> 83 7f 18 00 75 0a 0f 0b 83 cb ff e9 a3 00 00 00 8b 07 49 89 fd Sep 5 18:47:39 Hex kernel: RSP: 0018:ffffc9000becfbb8 EFLAGS: 00010286 Sep 5 18:47:39 Hex kernel: RAX: ffffffff815d65d2 RBX: ffff880103be7000 RCX: 0000000000000001 Sep 5 18:47:39 Hex kernel: RDX: ffff888103bdb408 RSI: ffff888101a16600 RDI: ffff880103be7030 Sep 5 18:47:39 Hex kernel: RBP: ffff888103bdb400 R08: ffff888101a16680 R09: ffff888101a16670 Sep 5 18:47:39 Hex kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff880103be7030 Sep 5 18:47:39 Hex kernel: R13: ffff8881325a0000 R14: 0000000001a16601 R15: ffff8881084a3c00 Sep 5 18:47:39 Hex kernel: FS: 000014baa11f1200(0000) GS:ffff88885f300000(0000) knlGS:0000000000000000 Sep 5 18:47:39 Hex kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 5 18:47:39 Hex kernel: CR2: ffff880103be7048 CR3: 00000002f5332003 CR4: 0000000000770ee0 Sep 5 18:47:39 Hex kernel: PKRU: 55555554 Sep 5 18:47:39 Hex kernel: note: smartctl[32750] exited with irqs disabled Sep 5 18:48:11 Hex kernel: BUG: unable to handle page fault for address: ffff880103be7048 Sep 5 18:48:11 Hex kernel: #PF: supervisor read access in kernel mode Sep 5 18:48:11 Hex kernel: #PF: error_code(0x0000) - not-present page Sep 5 18:48:11 Hex kernel: PGD 0 P4D 0 Sep 5 18:48:11 Hex kernel: Oops: 0000 [#1015] PREEMPT SMP NOPTI Sep 5 18:48:11 Hex kernel: CPU: 10 PID: 2067 Comm: smartctl Tainted: P D W O 6.1.99-Unraid #1 Sep 5 18:48:11 Hex kernel: Hardware name: ASUS System Product Name/ROG STRIX B760-I GAMING WIFI, BIOS 1662 08/07/2024 Sep 5 18:48:11 Hex kernel: RIP: 0010:sbitmap_get+0xb/0xd1 Sep 5 18:48:11 Hex kernel: Code: f0 72 16 85 f6 89 f7 74 07 e8 e1 ff ff ff 89 c7 48 8b 43 18 65 89 38 89 f8 5b c3 cc cc cc cc 41 57 41 56 41 55 41 54 55 53 51 <48> 83 7f 18 00 75 0a 0f 0b 83 cb ff e9 a3 00 00 00 8b 07 49 89 fd Sep 5 18:48:11 Hex kernel: RSP: 0018:ffffc90059d87b38 EFLAGS: 00010286 Sep 5 18:48:11 Hex kernel: RAX: ffffffff815d65d2 RBX: ffff880103be7000 RCX: 0000000000000001 Sep 5 18:48:11 Hex kernel: RDX: ffff888103bdb408 RSI: ffff888101a16600 RDI: ffff880103be7030 Sep 5 18:48:11 Hex kernel: RBP: ffff888103bdb400 R08: ffff888101a16680 R09: 0000000000000000 Sep 5 18:48:11 Hex kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff880103be7030 Sep 5 18:48:11 Hex kernel: R13: ffff8881325a0000 R14: 0000000001a16601 R15: ffff8881084a3c00 Sep 5 18:48:11 Hex kernel: FS: 0000150ff31fd200(0000) GS:ffff88885f480000(0000) knlGS:0000000000000000 Sep 5 18:48:11 Hex kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 5 18:48:11 Hex kernel: CR2: ffff880103be7048 CR3: 000000034d4a0003 CR4: 0000000000770ee0 Sep 5 18:48:11 Hex kernel: PKRU: 55555554 Sep 5 18:48:11 Hex kernel: Call Trace: Sep 5 18:48:11 Hex kernel: Sep 5 18:48:11 Hex kernel: ? __die_body+0x1a/0x5c Sep 5 18:48:11 Hex kernel: ? page_fault_oops+0x329/0x376 Sep 5 18:48:11 Hex kernel: ? search_bpf_extables+0x5d/0x68 Sep 5 18:48:11 Hex kernel: ? fixup_exception+0x22/0x24b Sep 5 18:48:11 Hex kernel: ? exc_page_fault+0xf4/0x11d Sep 5 18:48:11 Hex kernel: ? asm_exc_page_fault+0x22/0x30 Sep 5 18:48:11 Hex kernel: ? target_unblock+0x34/0x34 Sep 5 18:48:11 Hex kernel: ? sbitmap_get+0xb/0xd1 Sep 5 18:48:11 Hex kernel: ? slab_post_alloc_hook+0x4d/0x15e Sep 5 18:48:11 Hex kernel: scsi_mq_get_budget+0x19/0x90 Sep 5 18:48:11 Hex kernel: blk_mq_do_dispatch_sched+0xd3/0x31b Sep 5 18:48:11 Hex kernel: __blk_mq_sched_dispatch_requests+0xc9/0x11c Sep 5 18:48:11 Hex kernel: blk_mq_sched_dispatch_requests+0x2f/0x5a Sep 5 18:48:11 Hex kernel: __blk_mq_run_hw_queue+0x36/0x73 Sep 5 18:48:11 Hex kernel: blk_mq_get_tag+0xc1/0x1e9 Sep 5 18:48:11 Hex kernel: ? _raw_spin_rq_lock_irqsave+0x20/0x20 Sep 5 18:48:11 Hex kernel: __blk_mq_alloc_requests+0x1aa/0x227 Sep 5 18:48:11 Hex kernel: blk_mq_alloc_request+0x14c/0x19d Sep 5 18:48:11 Hex kernel: scsi_alloc_request+0xa/0x57 Sep 5 18:48:11 Hex kernel: sg_io+0x96/0x2a8 Sep 5 18:48:11 Hex kernel: scsi_ioctl+0x295/0x80a Sep 5 18:48:11 Hex kernel: blkdev_ioctl+0x213/0x23a Sep 5 18:48:11 Hex kernel: ? up_read+0x47/0x5d Sep 5 18:48:11 Hex kernel: vfs_ioctl+0x1b/0x2f Sep 5 18:48:11 Hex kernel: __do_sys_ioctl+0x52/0x78 Sep 5 18:48:11 Hex kernel: do_syscall_64+0x65/0x7b Sep 5 18:48:11 Hex kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Sep 5 18:48:11 Hex kernel: RIP: 0033:0x150ff33074e8 Sep 5 18:48:11 Hex kernel: Code: 00 00 48 8d 44 24 08 48 89 54 24 e0 48 89 44 24 c0 48 8d 44 24 d0 48 89 44 24 c8 b8 10 00 00 00 c7 44 24 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 07 89 d0 c3 0f 1f 40 00 48 8b 15 f9 e8 0d Sep 5 18:48:11 Hex kernel: RSP: 002b:00007ffc1972dd88 EFLAGS: 00000206 ORIG_RAX: 0000000000000010 Sep 5 18:48:11 Hex kernel: RAX: ffffffffffffffda RBX: 00007ffc1972df40 RCX: 0000150ff33074e8 Sep 5 18:48:11 Hex kernel: RDX: 00007ffc1972dd90 RSI: 0000000000002285 RDI: 0000000000000006 Sep 5 18:48:11 Hex kernel: RBP: 0000000000000003 R08: 0000000000000006 R09: 000000000000003c Sep 5 18:48:11 Hex kernel: R10: 0000150ff3211370 R11: 0000000000000206 R12: 0000000000000000 Sep 5 18:48:11 Hex kernel: R13: 0000000000000000 R14: 0000000000000012 R15: 00007ffc1972e1f0 Sep 5 18:48:11 Hex kernel: Sep 5 18:48:11 Hex kernel: Modules linked in: tun af_packet xt_nat xt_tcpudp veth macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag nct6775 nct6775_core hwmon_vid corefreqk(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iosf_mbi drm_buddy i2c_algo_bit btusb btrtl ttm btbcm drm_display_helper btintel kvm drm_kms_helper bluetooth drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 cdc_acm input_leds joydev led_class aesni_intel ecdh_generic ecc intel_gtt agpgart crypto_simd cryptd syscopyarea rapl mei_hdcp mei_pxp intel_cstate wmi_bmof intel_uncore i2c_i801 mei_me Sep 5 18:48:11 Hex kernel: sysfillrect i2c_smbus nvme sysimgblt ahci video igc mei nvme_core libahci vmd fb_sys_fops thermal fan i2c_core tpm_crb tpm_tis tpm_tis_core wmi tpm backlight intel_pmc_core acpi_pad acpi_tad button unix Sep 5 18:48:11 Hex kernel: CR2: ffff880103be7048 Sep 5 18:48:11 Hex kernel: ---[ end trace 0000000000000000 ]--- Cant tell if its cpu, memory, it even mentions macvlan (which I thought had been fixed in the current version). Though disk 3 seems to say its spun up, but it won't spin down when I tell it to and the temp seems to imply its already spun down.... so that seems problematic https://ibb.co/hCm9Mq0 hmm and it wont shut down the array cos it says Mover is running... I only knew this was a problem because my downstairs TV wouldn't run plex. Except it seems to work upstairs on my PC still. I have a monitor on the server box but it wont show the command line (remains a blank screen when I try and turn it on). But the webgui works fine. Except that one of my disks says its spun up when it isn't, and mover seems to have jammed everything up! Noone had any idea on the discord so I posted this here, before doing a hard reboot of the box (it wont shutdown the array because mover is running, even though it isn't... at least according to the logs!).

Dynamix Autofan - Is it known that this doesn't auto-start when the NAS/Array is booted up? I have to manually go into the plugin, and 'detect' and apply the fan again, for it to start working. Is there a way to automate this? A script or something maybe?>

Did anyone ever find the solution to this? I have the same issue, on the latest mover tuner plugin (correct version, in fact the only version on CA).

Might anyone know how to disable a specific PM in powertop? Automatically I mean, I know I can go into tunables and turn the individual ones on/off. The powertop documentation only refers to turned off sets of several (such as 'all PCI' or 'all ata'). I need to disable the one, as it is for the ethernet controller and -might- be the cause of my ethernet dying sporadically.

Does anyone have the SquishedMoo guides backed up or anything? Or other guide links? Their site seems to have gone down entirely since I couple days ago, and my Ghost setup isn't working correctly (worked for 24 hours and then died for no apparent reason)./

I'm curious about the reasoning for disabling turbo boost on the cpu? I understand that this will reduce the peak power draw, as the lower frequencies will draw less power. Fine. But it will also mean the cpu will need to run for longer periods of time to do the same tasks, so you're drawing less power but for longer. It would seem that you're not actually saving much power, and have the tradeoff of a much slower system. Just was curious, maybe having turbo turned on prevents sleep states or something? If it's just a matter of the voltage curve, then the best results would come from undervolting and then limiting the max boost a little bit, so you end up on the most efficient part of the voltage/boost curve (I would think).

Just to warn people - this link takes you to a site that uses one of those "your system has been infected with a virus, click here to fix" scam popups. Sure an ad blocker usually avoids them, but still. Not worth supporting scummy people with traffic.

Trying to add a parity fisk to a new build, but it keeps hanging on 0.0mb/s speeds after a while. Mar 4 15:02:21 Hex kernel: ------------[ cut here ]------------ Mar 4 15:02:21 Hex kernel: WARNING: CPU: 10 PID: 11284 at kernel/exit.c:814 do_exit+0x87/0x923 Mar 4 15:02:21 Hex kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper kvm drm_kms_helper drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd intel_gtt mei_hdcp mei_pxp agpgart i2c_i801 cryptd rapl input_leds joydev led_class intel_cstate wmi_bmof nvme syscopyarea Mar 4 15:02:21 Hex kernel: i2c_smbus intel_uncore mei_me ahci sysfillrect sysimgblt igc i2c_core nvme_core mei libahci vmd thermal fb_sys_fops fan video tpm_crb tpm_tis tpm_tis_core wmi tpm intel_pmc_core backlight acpi_tad acpi_pad button unix Mar 4 15:02:21 Hex kernel: CPU: 10 PID: 11284 Comm: unraidd0 Tainted: P D O 6.1.74-Unraid #1 Mar 4 15:02:21 Hex kernel: Hardware name: ASUS System Product Name/ROG STRIX B760-I GAMING WIFI, BIOS 1604 12/15/2023 Mar 4 15:02:21 Hex kernel: RIP: 0010:do_exit+0x87/0x923 Mar 4 15:02:21 Hex kernel: Code: 24 74 04 75 13 b8 01 00 00 00 41 89 6c 24 60 48 c1 e0 22 49 89 44 24 70 4c 89 ef e8 31 ed 80 00 48 83 bb b0 07 00 00 00 74 02 <0f> 0b 48 8b bb d8 06 00 00 e8 33 ec 80 00 48 8b 83 d0 06 00 00 83 Mar 4 15:02:21 Hex kernel: RSP: 0018:ffffc9000113fee0 EFLAGS: 00010286 Mar 4 15:02:21 Hex kernel: RAX: 0000000000000000 RBX: ffff888130e68000 RCX: 0000000000000000 Mar 4 15:02:21 Hex kernel: RDX: 0000000000000001 RSI: 0000000000002710 RDI: 00000000ffffffff Mar 4 15:02:21 Hex kernel: RBP: 0000000000000009 R08: 0000000000000000 R09: 0000000000aaaaaa Mar 4 15:02:21 Hex kernel: R10: 0000000000000001 R11: 0000000000000001 R12: ffff88812dbf3400 Mar 4 15:02:21 Hex kernel: R13: ffff888130599080 R14: 0000000000000000 R15: 0000000000000000 Mar 4 15:02:21 Hex kernel: FS: 0000000000000000(0000) GS:ffff88885f480000(0000) knlGS:0000000000000000 Mar 4 15:02:21 Hex kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 4 15:02:21 Hex kernel: CR2: 0000000000000157 CR3: 0000000151b86000 CR4: 0000000000750ee0 Mar 4 15:02:21 Hex kernel: PKRU: 55555554 Mar 4 15:02:21 Hex kernel: Call Trace: Mar 4 15:02:21 Hex kernel: <TASK> Mar 4 15:02:21 Hex kernel: ? __warn+0xab/0x122 Mar 4 15:02:21 Hex kernel: ? report_bug+0x109/0x17e Mar 4 15:02:21 Hex kernel: ? do_exit+0x87/0x923 Mar 4 15:02:21 Hex kernel: ? handle_bug+0x41/0x6f Mar 4 15:02:21 Hex kernel: ? exc_invalid_op+0x13/0x60 Mar 4 15:02:21 Hex kernel: ? asm_exc_invalid_op+0x16/0x20 Mar 4 15:02:21 Hex kernel: ? do_exit+0x87/0x923 Mar 4 15:02:21 Hex kernel: make_task_dead+0x11c/0x11c Mar 4 15:02:21 Hex kernel: rewind_stack_and_make_dead+0x17/0x17 Mar 4 15:02:21 Hex kernel: RIP: 0000:0x0 Mar 4 15:02:21 Hex kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Mar 4 15:02:21 Hex kernel: RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000 Mar 4 15:02:21 Hex kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Mar 4 15:02:21 Hex kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Mar 4 15:02:21 Hex kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Mar 4 15:02:21 Hex kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Mar 4 15:02:21 Hex kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Mar 4 15:02:21 Hex kernel: </TASK> Mar 4 15:02:21 Hex kernel: ---[ end trace 0000000000000000 ]---

Dynamix Fan Control Currently in the log it's showing that the 'hottest drive' is 48c, and it setting the speed of the fan appropriately. Fine. However the hottest drive is actually 65c (it's an NVME) which I was going to set to ignore anyway as the fan doesn't cool that drive, but it seems dynamix is ignoring it anyway (even though I haven't ticked the 'ignore' option in the settings for fan control). The hottest hard drive though... is only 40c. So it's not those that it's looking at either. The drive that is 48c is a sata ssd, which isn't in the array or mounted, and which isn't available in the 'ignore' list for control fan. So Dynamix seems to be registering and tracking the temps of drives not in the array, but only allows you to ignore drives that -are- in the array? Seems like a bug. Two bugs actually, as it's also ignoring the nvme for no reason. So it's ignoring one drive it shouldn't, and tracking one drive it shouldn't.