PeterDB

It's correct the fan speed can be controlled through the bios, and certain bios' even allow for granular speed control based on certain temp sensors, mainly those on the boards themselves or if they have an external sensor which can be connected (the latter has become extremely rare for consumer motherboards). The advantage with the Dynamix fan control is that if will allow that granular speed control against all temperature sensors in your system, including those on the hard drives, something almost no bios controls allow for. Consider the scenario your motherboard has 4 sensors: CPU, chipset, memory, board. They all read within tolerance and therefore fan dont speed up. However your 4 20tb drives have been spinning and their temps are hitting 58C, but because you choose to rely on bios fan controls, the fans are not spinning up to cool the drives. As per the maintainer (I contacted him) of the NCT6775 driver, and when I asked if it was possible to do it without acpi_enforce_resources=lax, I got this response: No, because it is a board problem and not a driver problem. The BIOS reserves the memory space used to access the chip for itself. Overriding it has some risk, thus the boot option is required. There are always risks and sometimes the benefits outweigh them. In my case I'm not investing in a new board just because of this. I monitored for weeks for issues and my server runs 24/7 with heavy loads,and i had no issues. I still run the same system, without issue.

I don't think this workaround would work, I think you need to try the one you found github

Sounds like a different issue, but weird behaviour if you are using NCT6775. If indeed you are using a NCT6775, I would do the workaround, just to test to see if it helps. Still odd.

No idea, sorry! But if stuff reverts, it's usually because whoever edited didn't have the rights, so the file didn't get correctly updated. Maybe log in with the Unfair root user and edit?

Sorry I missed this post. Simple Google search shows it's a Nuvoton NCT6683D. I doubt this workaround would work. If you want to test you can, but it's your own risk. I would take a new USB stick, load up Unraid on and test on that system to see if it works.

The short answer: no Why? lmsensor is a tool to mainly readout temp and fan data. However, if there is no data, then it cannot read anything? Why is there no data, because the driver is doesn't work anymore because of its code and hardware design. No matter you do, you still need a driver to read out and input temp data and make changes to pwm voltages. And in order to load the driver you need to lower the acpi enforcement settings. Way back when I put this together, I contact one of kernel maintainers for hwmon and got these responses: Email Extract: My name is PeterDB and proud user of the NCT6775 driver you wrote. Thanks so much for doing this! Unfortunately, as the Git repository is no longer available, and I was not able to raise an issue there, I am reaching out to you directly. I hope this is okay. The reason being is that with later kernels it only seems possible to get the NCT6775 driver working if you add acpi_enforce_resources=lax to either syslinux.cfg or the GRUB bootloader. Is there any way that you might be able to patch this? Response: No, because it is a board problem and not a driver problem. The BIOS reserves the memory space used to access the chip for itself. Overriding it has some risk, thus the boot option is required. Email: Do you have any objection to me sharing this information and screenshot of the email on the Unraid community specifically in this post:h ttps://forums.unraid.net/topic/127313-nct6775-dynamix-system-temperature-dynamix-auto-fan-control-support/ Response: Ok with me, though the information on that page seems pretty complete. It already states that that acpi_enforce_resources=lax is necesssary and risky. And, yes, it is a workaround/hack/kludge, not a fix

actually, none at all. I thought it would, but I've experience no adverse reactions... only the desire to purchase new hardware where I don't have to do the workaround.

my motherboard has the same options for fan control, but the motherboard options are tied to a temp sensor, at leas with mine it is. You can control it via the bios, but I had my fans constantly spinning then. I switched them all to pwm, and no temp sensors, then did the workaround I propose here. Now I have fans only spinning when the temp is high as based on disks also. For me this worked better, try or not, up to you, but I can recommend it

I doubt your issue has anything with the NCT6775 driver. If you have a multiple PWM controllers, you need to test each own to find out which one is the main PWM controller. Although most of the times its the one ending in pwm1. Unless you connect the NORCO s500 fans to the motherboard PWM/Fan headers, you won't get able to get any readouts from them. From what I read the NORCO s500 fan is internal in the unit and you only connect power and sata to the units, so unless you open it and connect the cable to the motherboard it's not going to be readout in Unraid. That means that it's the internal temp sensor in the NORCO s500 which controls the fan. As for why the CPU fan isn't found, it's most likely the ict8718 controllers, if not, you'd need to use the sensors-detect to find which driver is missing. However, i'll be honest the GA-G33-DS3R is quite old and you might not be able to find a lot of information out there.

It seems that it cannot load correctly due to the drivers for the Kraken not being part of the OS. Looking at others online, Kraken AIOs seems to be very sporadically supported on Linux and many opting for Windows VMs to control it. It seems there is a driver, but I cannot find any details on really how to install it. It might be an idea to reach out to the dev Jonas Malaco (https://jonasmalaco.com/) who created it and actually who wrote LiquidCTL. Some posts: https://www.kernel.org/doc/html/latest/hwmon/nzxt-kraken2.html https://github.com/liquidctl/liquidctl

Here's the thing; in the comment here it's eluded to the fact, that in the future there will be no array, but just pools, which could imply XFS is going away. As for scalability, with the btrfs pools I have each time I added a drive it required me to reformat, would that also be the case in the future if XFS goes away?

This is quite interesting! So for the future would a pool still be able to use XFS or will you be limiting it to btrfs and zfs? What about the ability to scale pools one drive at a time (major reason for many who use Unraid) and will there be a pool disk size limit?

In a single array, yes, it should be 32. Why? Good reason, if you have a HBA controllers which supports 16 drives and you have two in your system, such as I and many others do, then the maximum drive count is 32 drives. With Unraid only supporting 30 drives, you're left with two drives you cannot add to the array. As for the multiple array's, I'm actually fine with a 32 drive limit, but it would be nice to have more arrays, not more cache pools.

Awesome! But, it would be great to have array sizes beyond the 30 drive limit or have multiple arrays

@ich777Considering this is an issue for several people here, and considering your wealth of knowledge, do you have another suggestion?

Sadly, I read it already, but it's what is being advised for the nct6775 driver when there are detection issues, and sadly it seems no one is doing anymore development on it. I'll correct the screenshots and add a disclaimer.

I had issues too! Check this post I made

I'm writing this not only for myself, as I had a to spend a couple of hours to get this to work, but also because I find others who still experience issues with getting temperature and fan readings out when they are using Dynamix System Temperature or Dynamix Auto Fan Control Support together with the NCT6775 driver for Nuvoton NCT5572D/NCT6771F/NCT6772F/NCT6775F/W83677HG-I and other chips. The issue that most will experience is that only CPU temps are showing up, but none of the fan or other temperature sensors are showing up. There are a lot of instructions of solving the various issues, such as sensor detection, adding acpi_enforce_resources=lax to syslinux.cfg or just getting the driver to load, but there is no end-to-end guide! Newer Asus motherboards, who are notorious for using Nuvoton sensors, will in the future have a different driver, read more here https://www.phoronix.com/forums/forum/hardware/motherboards-chipsets/1304134-new-asus-sensor-driver-for-linux-aims-for-greater-flexibility-faster-sensor-reading. However, for older boards such as my Asus Sabertooth X99 with the Nuvoton thermal sensors, enabling acpi_enforce_resources=lax has been advised in for several years. This guide assumes you have a bit of experience with Unraid, but if you don't just post here and I'll try to help! DISCLAIMER: Adding acpi_enforce_resources=lax to syslinux.cfg could/can cause adverse effects, read more here: https://bugzilla.kernel.org/show_bug.cgi?id=204807#c37 It would be strongly advise that should you need to do any firmware updates to boot into regular Unraid OS for the boot menu and not choose the default Unraid OS NCT6775 Workaround option. Steps for workaround Open the Unraid terminal Type sensors-detect and accept everything At the end of sensors-detect it will show you a list of the found drivers, write these down: in the below case it's "nct6775" and "coretemp" On the Unraid flash drive edit the Go-file found in /boot/config (make sure to make a backup!) and add the lines referring to the drivers, and save the file modprobe nct6775 modprobe coretemp /usr/bin/sensors -s Now go to the Unraid dashboards Main page and click on your flash drive Scroll down to the section Syslinux Configuration and on the right side click on "Menu View" Add the label Unraid OS NCT6775 WORKAROUND under the label Unraid OS. The text you need to add is shown below. label Unraid OS NCT6775 WORKAROUND kernel /bzimage append initrd=/bzroot acpi_enforce_resources=lax Once you've added the label click on the "Raw View" option on the right side and select the new Unraid OS NCT6775 WORKAROUND as default but clicking the little round radiobutton and then click "Apply" Now reboot All done and it should work, and you'll be able to configure the Dynamix System Temperature and Dynamix Auto Fan Control Support plugins Proof that it does:

Interesting! Why honestly, why not just use the Add2PSU and a molex connector between the cases?

yeah, I spent a couple of hours to see how to get this done correctly, and even custom ordering the cables, so they are made properly... cost is more than an second PSU. Easier to get an Add2PSU and use a second PSU. Thanks again for the help! Last question: You mention you run a 3U and 2U as a diskshelf, how are you ensure the power on between the two?

I managed to find some, even higher rated 12V to 5V 10A converters, and coincidentally also some chia miners that use the same method to split the power off EPS and PCI-E.

Ah, I get it. In essence I could make an EPS or PCI-E 8pin to a step-down 12V>5V and 12V>3.3V and then to SATA, or just 5V and Molex. However, I seem to be unable to one in Europe.

Could you clarify what you mean by the DC-DC module and that there's already one inside?

I'm starting to run out of space and room in my rack for drives. I currently have an Inter-Tech 4U 4129L with an array of 14 drives (incl. one for parity), plus an nvme, ssd cache and a hdd cache all working quite well with an Zalman ZM750-ARX PSU. The drives are a mix of shucked 8TB WDCs, 16TB Seagate DC and WDC DC drives totally 152TB, and yes, I'm running out of space. I bought the Inter-Tech 4F28 (imgur), as it can hold 28 3.5" plus 6 2.5" drives (two on either side of the drive cages and two side mounted in the rear compartment) without thinking of PSU, but just needing more drive space. I plan to populate it with WDC 16tb or 18tb DC drives, which usually pull operationally 5V/0.5A and 12V/0.57A, but would like to port over my existing drives which based on the drive spec pull 9.2A on 5V and 9.8A on 12V. Yes, I have been reading a lot here, reddit, and many other communities, reached out via DM to a lot of OPs to figure out their set up's, and found that most just only look at the PSU wattage not amps or just plainly ignore amps, staggered spin-ups, max connections on sata cables, and far too many seem to underpower their systems. Personally, I don't need a high-spec'd CPU or motherboard, I currently use a Gigabyte H97-D3H-CF and an Intel i7-4770 with 32gb, which is more than enough for storage and running a few dockers. The controller is a Adaptec 71605 in HBA mode, and I don't see any options in the controller BIOS for staggered spin-up. The short question(s): - How many drives do you have and what's your cabling/PSU? - My Zalman ZM750-ARX delivers 5V rail 22A 120W and 12V rail 62A 744W (80% load would be 5V/17.6A/96W and 12V/49.6A/595W) is it enough? - Should I get a 2nd PSU, just to be safe? - What's the best mounting options for a 2nd PSU considering the case/any regular 1 PSU ATX/4U case? Am I overthinking this? Did my Googling just make the simple decision a lot more complicated?

Here are some pictures of the 4F28. Very promising! Will try to post more pictures in a different thread.