fireflower

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by fireflower

  1. Thanks, edited one on the / folder and it seemed to do the trick. Made a backup this time so when I update next time my configs don't get lost lol.
  2. I think I am starting to go nuts but updated DDclient and it rewrote over my config and now I see to have 4-5 ddclient.confs in various locations, which one I should use?
  3. Okay, I found a workaround for me that lets me use VM's, dockers and I don't have to go into bios to disable IOMMU which disables virtualization (Thanks Dell!) Boot option: iommu=soft and you can use the USB device on Dell R410. Confirmed the card working newer hardware correctly with unRAID so it was a host hardware problem all along. I don't need IOMMU isolation so desperately for PCIE passthrough on my machine but it would have been nice but this should work also because I can still run dockers & VM's.
  4. Reporting: This card still has issues with unRAID 6.9 beta22 release. Somebody asked me to try ACS patch boot options and that way I got card's both hosts or single host passed to VM or let unRAID use other but the problem is the card does not work in unRAID or VM's guest OS (tried Fedora 31) Which is expected result because IOMMU groups are not anymore respected but the card still won't work under unRAID with IOMMU on. I think I will next try the card with newer hardware and see might this just be somekind mobo / bios incompatibility which I hear are a rare thing.
  5. seems like this version doesn't support "Finish and stop folding", instead it just starts a new WU.
  6. Had odd behavior myself today also where had to reload "fan_manual_enable". I don't know what has caused the problem but strangely it happened today for you and I.
  7. Tried to disable IOMMU (Virtualization support) groups in bios like somebody suggested, well the card works now in unraid with keyboards at least. Cannot say it is a solution though because doing this practically makes unRAID then unable to run virtual machines or containers, which then again is like why even bother using unRAID? Wanted to check the card actually works properly in other distros, so took Linux Mint 19.3 and it was able to use the card with IOMMU groups enabled and create VM's and give access to one of the controllers on the card for that VM. The fix would be very much appreciated.
  8. This script has not been tested to work with R720 or none other server than R410. The basic script is pretty easy to transfer to other systems if you have just have raw codes for fans. Crontab * * * * * should run the script every minute but guess */1 * * * * works also because it literally tells cronjob to run every minute of every minute.
  9. I have done testing, finished another 5 WU:s, only 1 seems to have been accepted, uploading fails "connection refused / no connection / expected 512 bytes, got 0" etc. It is just not downloads that is overwhelmed at foldingathome, even uploads can fail and for some reason uploads clear from queue without succeeding. At least for GPU WU's, dunno what is the problem.
  10. Thanks, I will run a few WU's gpu only and see am I getting 'rewarded' or something odd happening at my or f@h end.
  11. Is it normal for GPU points not to be updated regularly at f@h? According to logs I have finished about 10 WU and uploads succeeded with -70-100k points estimate but I see only my CPU WUs earning points.
  12. Well managed to finish one WU then again back to the loop
  13. Reported this as a bug because with even newer kernel cannot get the card to work in unRAID or with passthrough to a VM.
  14. The problematic card: Card: Allegro USB-C 4-port PCIe https://www.sonnettech.com/product/allegro-usbc-4port-pcie.html Use case for card: 4x 10Gbit USB-C connections for cold backup drives / USB nics / etc. I have waited pretty patiently for unRAID to have 5.X kernel with drivers to use this card but then turns out unRAID has a problem with this card. Because unRAID refused to use the card itself, I tried to passthrough it to VM to test some of my USB-C cards but I get the error below. I tried first XML editing for passthrough and then blacklisting the device. Got the same error with both ways. internal error: qemu unexpectedly closed the monitor: 2020-03-20T17:17:14.681758Z qemu-system-x86_64: -device vfio-pci,host=0000:05:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio 0000:05:00.0: failed to setup container for group 15: Failed to set iommu for container: Operation not permitted internal error: qemu unexpectedly closed the monitor: 2020-03-20T17:31:44.966753Z qemu-system-x86_64: -device vfio-pci,host=0000:06:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio 0000:06:00.0: failed to setup container for group 16: Failed to set iommu for container: Operation not permitted I am happy to try any possible fixes. rs1-diagnostics-20200320-1933.zip
  15. Updated to this today but still I don't get the https://www.sonnettech.com/product/allegro-usbc-4port-pcie.html usb extension card to work directly with unraid. Unraid is not using any of the devices that I try connect to it, mouse, keyboard, usb-stick or nic. I bought this card to give my server USB 3 ports to backup data faster to cold storage and have an option to connect extra nics or faster nics to very limited 1U chassis. When I use lsusb -t it seems like I have the hubs there but nothing that I connect to the hub seems to do anything. $ lsusb -t /: Bus 12.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M /: Bus 11.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M /: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M rs1-diagnostics-20200319-2257.zip
  16. Could you elaborate a little? Like I said I am pretty new to Linux environment. I checked my BIOS certainly doesn't have any option related to this.
  17. I want unRAID to be able to use it also so I can take cold backups directly to external drive instead using RJ45 (which is slower & also other services via network get slowed down).
  18. So I bought Allegro USB-C 4-port PCIE card for my unRAID server to get faster USB connection and way to attach cheaper USB 2.5 nics or 5Gbit nics when I need them. Card page: https://www.sonnettech.com/product/allegro-usbc-4port-pcie.html Unfortunately unRAID doesn't seem to try utilize the card though it is posted in IOMMU groups but no USB device works on it. (keyboard, mouse or usb-stick, let alone a nic). So wondering do I have to get different kernel version of unRAID or build my own unRAID with exact kernel version that has support for this? I am pretty beginner when it comes to Linux, so I would appreciate detailed instructions what to do. Down below is system devices posted: IOMMU groups 15 & 16 are the USB controller IOMMU group 0: [8086:3403] 00:00.0 Host bridge: Intel Corporation 5500 I/O Hub to ESI Port (rev 13) IOMMU group 1: [8086:3408] 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13) IOMMU group 2: [8086:340a] 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13) IOMMU group 3: [8086:340e] 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13) IOMMU group 4: [8086:342e] 00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 13) [8086:3422] 00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13) [8086:3423] 00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13) IOMMU group 5: [8086:3430] 00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) [8086:3431] 00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) [8086:3432] 00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) [8086:3433] 00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) [8086:3429] 00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) [8086:342a] 00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) [8086:342b] 00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) [8086:342c] 00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13) IOMMU group 6: [8086:3a37] 00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a38] 00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a3c] 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 IOMMU group 7: [8086:3a34] 00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a35] 00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a36] 00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 [8086:3a39] 00:1d.3 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a3a] 00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 IOMMU group 8: [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) [102b:0532] 07:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) IOMMU group 9: [8086:3a16] 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller [8086:3a22] 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller IOMMU group 10: [14e4:163b] 01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5716 Gigabit Ethernet (rev 20) [14e4:163b] 01:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5716 Gigabit Ethernet (rev 20) IOMMU group 11: [1000:0058] 02:00.0 SCSI storage controller: Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS (rev 08) IOMMU group 12: [12d8:2308] 03:00.0 PCI bridge: Pericom Semiconductor Device 2308 IOMMU group 13: [12d8:2308] 04:01.0 PCI bridge: Pericom Semiconductor Device 2308 IOMMU group 14: [12d8:2308] 04:02.0 PCI bridge: Pericom Semiconductor Device 2308 IOMMU group 15: [1b21:1242] 05:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller IOMMU group 16: [1b21:1242] 06:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller IOMMU group 17: [8086:2c70] fe:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers (rev 02) [8086:2d81] fe:00.1 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder (rev 02) IOMMU group 18: [8086:2d90] fe:02.0 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 0 (rev 02) [8086:2d91] fe:02.1 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 0 (rev 02) [8086:2d92] fe:02.2 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 0 (rev 02) [8086:2d93] fe:02.3 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 1 (rev 02) [8086:2d94] fe:02.4 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 1 (rev 02) [8086:2d95] fe:02.5 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 1 (rev 02) IOMMU group 19: [8086:2d98] fe:03.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers (rev 02) [8086:2d99] fe:03.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Target Address Decoder (rev 02) [8086:2d9a] fe:03.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller RAS Registers (rev 02) [8086:2d9c] fe:03.4 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Test Registers (rev 02) IOMMU group 20: [8086:2da0] fe:04.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Control (rev 02) [8086:2da1] fe:04.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Address (rev 02) [8086:2da2] fe:04.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Rank (rev 02) [8086:2da3] fe:04.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Thermal Control (rev 02) IOMMU group 21: [8086:2da8] fe:05.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Control (rev 02) [8086:2da9] fe:05.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Address (rev 02) [8086:2daa] fe:05.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Rank (rev 02) [8086:2dab] fe:05.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Thermal Control (rev 02) IOMMU group 22: [8086:2db0] fe:06.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Control (rev 02) [8086:2db1] fe:06.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Address (rev 02) [8086:2db2] fe:06.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Rank (rev 02) [8086:2db3] fe:06.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Thermal Control (rev 02) IOMMU group 23: [8086:2c70] ff:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers (rev 02) [8086:2d81] ff:00.1 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder (rev 02) IOMMU group 24: [8086:2d90] ff:02.0 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 0 (rev 02) [8086:2d91] ff:02.1 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 0 (rev 02) [8086:2d92] ff:02.2 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 0 (rev 02) [8086:2d93] ff:02.3 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 1 (rev 02) [8086:2d94] ff:02.4 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 1 (rev 02) [8086:2d95] ff:02.5 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 1 (rev 02) IOMMU group 25: [8086:2d98] ff:03.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers (rev 02) [8086:2d99] ff:03.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Target Address Decoder (rev 02) [8086:2d9a] ff:03.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller RAS Registers (rev 02) [8086:2d9c] ff:03.4 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Test Registers (rev 02) IOMMU group 26: [8086:2da0] ff:04.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Control (rev 02) [8086:2da1] ff:04.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Address (rev 02) [8086:2da2] ff:04.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Rank (rev 02) [8086:2da3] ff:04.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Thermal Control (rev 02) IOMMU group 27: [8086:2da8] ff:05.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Control (rev 02) [8086:2da9] ff:05.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Address (rev 02) [8086:2daa] ff:05.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Rank (rev 02) [8086:2dab] ff:05.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Thermal Control (rev 02) IOMMU group 28: [8086:2db0] ff:06.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Control (rev 02) [8086:2db1] ff:06.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Address (rev 02) [8086:2db2] ff:06.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Rank (rev 02) [8086:2db3] ff:06.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Thermal Control (rev 02) CPU Thread Pairings Pair 1: cpu 0 / cpu 12 Pair 2: cpu 1 / cpu 13 Pair 3: cpu 2 / cpu 14 Pair 4: cpu 3 / cpu 15 Pair 5: cpu 4 / cpu 16 Pair 6: cpu 5 / cpu 17 Pair 7: cpu 6 / cpu 18 Pair 8: cpu 7 / cpu 19 Pair 9: cpu 8 / cpu 20 Pair 10: cpu 9 / cpu 21 Pair 11: cpu 10 / cpu 22 Pair 12: cpu 11 / cpu 23 USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 003: ID 0fce:e134 Sony Ericsson Mobile Communications AB Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 0624:0248 Avocent Corp. Virtual Hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub SCSI Devices [0:0:0:0] disk SEMC SD CCR-80 9454 /dev/sda 7.94GB [1:0:0:0] disk ATA TOSHIBA HDWN180 GX2M /dev/sdb 8.00TB [2:0:0:0] disk ATA TOSHIBA HDWN180 GX2M /dev/sdc 8.00TB [5:0:0:0] disk ATA T-60 601b /dev/sdd 60.0GB
  19. Beta branch had a small update, more features coming 🔜
  20. Thanks, had to just add "bash" to front of my script on crontab and again good to go.
  21. So, my fan scripts stopped working completely after update and I cannot figure out why I cannot get them back. root@Romuserveri1:/boot/config/scripts/fans# ls -lha total 28K drwx------ 2 root root 4.0K Dec 16 09:41 ./ drwx------ 3 root root 4.0K Sep 24 16:37 ../ -rw------- 1 root root 1.9K Sep 25 03:30 r410_fan_manual_enable.sh -rw------- 1 root root 4.0K Sep 25 03:30 r410_fan_script.sh -rw------- 1 root root 12K Dec 16 09:41 r410_fanspeeds_table.xlsx root@Romuserveri1:/boot/config/scripts/fans# chmod +x r410_fan_script.sh root@Romuserveri1:/boot/config/scripts/fans# ls -lha total 28K drwx------ 2 root root 4.0K Dec 16 09:41 ./ drwx------ 3 root root 4.0K Sep 24 16:37 ../ -rw------- 1 root root 1.9K Sep 25 03:30 r410_fan_manual_enable.sh -rw------- 1 root root 4.0K Sep 25 03:30 r410_fan_script.sh -rw------- 1 root root 12K Dec 16 09:41 r410_fanspeeds_table.xlsx root@Romuserveri1:/boot/config/scripts/fans# chown root:root r410_fan_script.sh root@Romuserveri1:/boot/config/scripts/fans# ls -lha total 28K drwx------ 2 root root 4.0K Dec 16 09:41 ./ drwx------ 3 root root 4.0K Sep 24 16:37 ../ -rw------- 1 root root 1.9K Sep 25 03:30 r410_fan_manual_enable.sh -rw------- 1 root root 4.0K Sep 25 03:30 r410_fan_script.sh -rw------- 1 root root 12K Dec 16 09:41 r410_fanspeeds_table.xlsx root@Romuserveri1:/boot/config/scripts/fans# chmod +x r410_fan_script.sh root@Romuserveri1:/boot/config/scripts/fans# ls -lha total 28K drwx------ 2 root root 4.0K Dec 16 09:41 ./ drwx------ 3 root root 4.0K Sep 24 16:37 ../ -rw------- 1 root root 1.9K Sep 25 03:30 r410_fan_manual_enable.sh -rw------- 1 root root 4.0K Sep 25 03:30 r410_fan_script.sh -rw------- 1 root root 12K Dec 16 09:41 r410_fanspeeds_table.xlsx root@Romuserveri1:/boot/config/scripts/fans# chmod 777 r410_fan_script.sh root@Romuserveri1:/boot/config/scripts/fans# ls -lha total 28K drwx------ 2 root root 4.0K Dec 16 09:41 ./ drwx------ 3 root root 4.0K Sep 24 16:37 ../ -rw------- 1 root root 1.9K Sep 25 03:30 r410_fan_manual_enable.sh -rw------- 1 root root 4.0K Sep 25 03:30 r410_fan_script.sh -rw------- 1 root root 12K Dec 16 09:41 r410_fanspeeds_table.xlsx root@Romuserveri1:/boot/config/scripts/fans# Ideas?
  22. Hello, I am a bit new to server grade gear but I wrote a bit script, where friend helped me a little bit with bash piping. This script is available from github: https://github.com/Tulikukka/Dell-R410-fan-speed-controller-script Features: Requires just ipmitool package Bash script updates fan speeds every minute based on uptime's "average" load. example code made for 2x L5640 (2x60W TPD) @ 25C ambient has excel for fan speed hex values. Colors are used to guide tweakers. Special thanks to Jamie's blog to get me started using ipmitool. Suggestions, tweaks, etc. are welcome.
  23. Cisco RJ45-DB9 (rs232, serial, console) cable is not pin compatible with Eaton / APC / Tripp-lite / et cetera. You need to make your own or buy a correct one. Sad truth is every maker makes their own version not pin compatible with others. Other important thing is that baud rate is correct, because some ups wont respond to incorrect baud (such as APC)
  24. Did you try running autodetect? And what did it show? Auto detect set up tripplite usb, I checked with laptop that windows based poweralert local works and shows all values correctly so I would assume the configuration file in nut is wrong for this? Also don't know does it makes a difference but this is 230V model.