MartinQ

Members
  • Posts

    109
  • Joined

  • Last visited

Everything posted by MartinQ

  1. I'm trying to get Auto Fan Control working but I receive the following "PWM Fan" response when when Detect is selected for any of the PWM controllers in the drop down list. <br /><b>Warning</b>: file_put_contents(): Only 0 of 1 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b> <br /><br /><b>Warning</b>: file_put_contents(): Only 0 of 3 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>43</b> <br /><br /><b>Warning</b>: file_put_contents(): Only 0 of 3 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>46</b> <br /><br /><b>Warning</b>: file_put_contents(): Only 0 of 3 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>49</b><br /> Unraid 6.8.3 Auto Fan Control is current 2020.06.21 df -h gives: Filesystem Size Used Avail Use% Mounted on rootfs 2.9G 920M 2.0G 32% / tmpfs 32M 444K 32M 2% /run devtmpfs 2.9G 0 2.9G 0% /dev tmpfs 3.0G 8.0K 3.0G 1% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 196K 128M 1% /var/log /dev/sda1 3.8G 777M 3.0G 21% /boot /dev/loop0 9.2M 9.2M 0 100% /lib/modules /dev/loop1 7.3M 7.3M 0 100% /lib/firmware
  2. Indeed it is. Hold on to your hats boys ... this is a BIG one! =D Thanks Tom (and crew)!!
  3. Bingo! I don't want my cabinets relying on a PC for cooling functionality. And it goes far beyond cabinets, there are endless applications for cooling control. This too.
  4. If your project requires a motherboard and/or OS to function then I'm definitely not interested. I have several projects that could use better temperature (fan) control but only a few make use of a PC.
  5. I've been looking for a programmable fan controller for quite a while. For whatever reason there really is nothing out there unless you want to spend $100+ for something. What I would love to have right now would be capable of: - operation independent of any PC communication - 12V or 5V power supply - any number of 3-pin or 4-pin fan connections (even just a single fan would be great) - any number of thermistor connections - able to be programmed for min/max fan speeds and temperature setpoints - able to be programmed for linear/log speed curves If I could get a board with one temperature sensor and one fan connector that could be programmed with a few simple variables then I'd be tickled. The answer it seems is always, 'build it yourself using an Arduino'. Sure ... I get around to that some day, some year.
  6. Can you put this link in the first post? It could get tricky to find in the future. Thanks!
  7. Chugalug, thanks a bunch for the update. Please keep us posted if you find anything else (good or bad) about this card and it's performance. Glad to hear it's working better for you.
  8. Just checked the motherboard specs and it looks like it has two PCIe 3.0 slots (x16 x8) and the rest are PCIe 2.0. The card (PEX40064) supports up to PCIe 2.0 so you should be OK on the hardware side. This card uses the Marvell 88SE9215 chip. http://www.marvell.com/storage/system-solutions/assets/Marvell-88SE92xx-002-product-brief.pdf The problem might stem from the Gigabyte motherboard/BIOS. Picked up some related info here: http://lime-technology.com/forum/index.php?topic=23483.15
  9. Since the problem is isolated to the SM card, which card is it? Firmware version? Which version of UnRAID?
  10. These are the errors listed in the first link: download.lime-technology.com - The indicated domain download.lime-technology.com is not a zone: no authority information is announced for it. download.lime-technology.com may be a simple domain; it is handled by parent zone lime-technology.com. No authoritative servers could be reached to fetch authority parameters: this zone appears to be currently blacked out of the Internet, no domains in it can be resolved. - lime-technology.com delegates its DNS to 1 servers. This does not fulfill DNS' requirements, which mandate a minimum of 2 servers for each zone. As soon as the server will experience some downtime, all services associated with lime-technology.com will vanish from the Internet. You should get DNS redundancy immediately to fix this. - The DNS servers listed as authoritative for lime-technology.com are NOT sufficiently distributed. A range of clients can suffer extensive DNS latencies based on their geographical location, and the stability and availability of DNS can be affected by network problems, power outages, or natural disasters. - None of the servers serving lime-technology.com's DNS is reachable via IPv6. IPv6-enabled clients lime-technology.com will need to revert to compatibility IPv4 protocol for every look up of services of lime-technology.com. A growing number a IPv6-only clients will be unable to perform such look ups.
  11. Tom have you had a look at these links yet?
  12. I didn't splurge for the eSATA ports. Mine looked more like this one: http://www.ebay.co.uk/itm/SATA3-HD-supported-SATA-III-2-Internal-6Gbps-Ports-PCI-e-Card-ASM1061-Chipset-/131027160900
  13. I've had great results from the Asmedia ASM1061 card. http://lime-technology.com/forum/index.php?topic=18522.msg225517#msg225517
  14. I've had two UnMenu updates that do not seem to install, they always show when I check for updates: Any ideas?
  15. Thanks so much for explaining this! I've used UnMenu for a while but haven't discovered Screen yet.
  16. Well I tried rc16c again to get a pic of the screen and ... it booted!? So I guess it's 'fixed'? This time I only copied over bzroot and bzimage as I kept the new syslinux.cfg. Last time it loaded both files and started the initialization but got stuck along the way.
  17. ! rc16c update failed ! Just tried to update from rc12a and the system did not come up. Tried using Safe Mode as well with same result. Hooked up a monitor to see what's going on and it looked like it was stuck initializing the first drive (sda) or something. Will try to get back with some details soon. Went back to rc12a and system is running again.