YouAreTheOneNeo

Members
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About YouAreTheOneNeo

  • Rank
    Member
  1. [Plugin] IPMI for unRAID 6.1+

    Indeed, many thanks for the effort you're putting into this. I updated the plugin this morning, but running ipmi2json from the command line (and the configure button) just gives me "Please stop ipmifan [19466]. Running ipmifan gives my board is not supported. I reinstalled the plugin after I wiped out the files at /boot/config/plugins/ipmi but no dice. An issue detecting my board for some reason? Ipmifan is shown as not running in the web GUI... Edit: Managed to get ipmi2json to produce a board.json file, although I'm not entirely sure how... Linux 4.9.30-unRAID. root@UnRaid:~# ipmifan ipmifan is not enabled in /boot/config/plugins/ipmi/fan.cfg type: ipmifan -f to force start root@UnRaid:~# ipmifan --debug ipmifan is not enabled in /boot/config/plugins/ipmi/fan.cfg type: ipmifan -f to force start root@UnRaid:~# ipmifan --help Process settings in ipmi plugin fan config. Control fans based on config values and [options]. Usage: ipmifan [options] -a, --auto set fans to auto --full set fans to full speed -f, --force force start -q, --quiet suppress all messages --debug turn on debugging --daemon run in the background --help display this help and exit --quit stop daemon if running --version output version information and exit root@UnRaid:~# ipmifan --quit 9502 is not currently running root@UnRaid:~# nano /boot/config/plugins/ipmi/fan.cfg root@UnRaid:~# ipmifan ipmifan[14512]: Your ASRock motherboard is not supported or setup yet Your ASRock motherboard is not supported or setup yet root@UnRaid:~# ipmifan --debug ipmifan[14810]: Your ASRock motherboard is not supported or setup yet Your ASRock motherboard is not supported or setup yet root@UnRaid:~# ipmifan --debug ipmifan[14972]: Your ASRock motherboard is not supported or setup yet Your ASRock motherboard is not supported or setup yet root@UnRaid:~# ipmifan --debug ipmifan[15016]: Your ASRock motherboard is not supported or setup yet Your ASRock motherboard is not supported or setup yet root@UnRaid:~# ipmifan --debug ipmifan[15062]: Your ASRock motherboard is not supported or setup yet Your ASRock motherboard is not supported or setup yet root@UnRaid:~# dmidecode -t 2 | grep 'Manufacturer' | awk -F 'r:' '{print $2}' ASRock root@UnRaid:~# dmidecode -t 2 | grep 'Product Name' | awk -F 'e:' '{print $2}' EP2C602 root@UnRaid:~# ipmi2json Please stop ipmifan [15062] then try again root@UnRaid:~# ps -A | grep 15062 root@UnRaid:~# ps -A | grep ipmi 8199 ? 00:00:32 kipmi0 root@UnRaid:~# ipmifan --quit 15062 is not currently running root@UnRaid:~# ipmi2json Checking IPMI fan Locations... Location 0-1: FRNT_FAN3 100%: 2400.00 33%: 1600.00 Location 0-2: none Location 0-3: FRNT_FAN1 100%: 2500.00 33%: 800.00 Location 0-4: FRNT_FAN2 100%: 2400.00 33%: 700.00 Location 0-5: FRNT_FAN3 100%: 2400.00 33%: 800.00 Location 1-1: CPU_FAN2_1 100%: 1400.00 33%: 500.00 Location 1-2: REAR_FAN2 100%: 2300.00 33%: 700.00 Location 1-3: none Saving board configuration... I manually modified the board.json file to reflect the board: root@UnRaid:/boot/config/plugins/ipmi# cat board.json { "ASRock": { "raw": "00 3a 01", "auto": "00 00 00 00 00 00", "full": "01 64 64 64 64 64", "fans": { "CPU_FAN1_1": "00", "REAR_FAN1": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00" } }, "ASRock1": { "raw": "00 3a 11", "auto": "00 00 00 00", "full": "01 64 64 64", "fans": { "CPU_FAN2_1":"00", "REAR_FAN2": "00", "FRNT_FAN4": "00" } } }root@UnRaid:/boot/config/plugins/ipmi# I have no idea why it decided to start working in the end, everything I could see suggested that ipmifan was not running.
  2. [Plugin] IPMI for unRAID 6.1+

    I'll see if I can finish something to test soon. Much obliged.
  3. [Plugin] IPMI for unRAID 6.1+

    Ah, okay. Yes, those are the commands that work. Here is an excerpt from the script that I wrote to do the fan speed control using a cron job based on the disk temperatures of the array: # IPMI Raw Command to run. For the EP2C602 there are two commands used to set various # fan speeds. These two commands are both set below. Replace with the appropriate raw # commands for your MotherBoard. IPMI_RAW_1="ipmi-raw 00 3a 01" IPMI_RAW_2="ipmi-raw 00 3a 11" # IPMI_RAW_1 Format: ipmi-raw 00 3a 01 CPU_1_OVERRIDE CPU_1 REAR_1 FRONT_1 FRONT_2 UNKNOWN # # IPMI_RAW_2 Format: ipmi-raw 00 3a 11 CPU_2_OVERRIDE CPU_2 REAR_2 UNKNOWN # # IMPI Fan speeds are defined as values between 00 and 64, where 00 is Auto, 01 is Min, and 64 is Max speed. I have only got 4 fans in my system at the moment, so I'm not sure which fans the unknown slots control. There's also room for two more CPU fans, so I would assume there is another raw IPMI command to control those ones. The board's smart fan setting lets the CPU get uncomfortably hot before rolling up the fan speed, and I find it unreliable. I also can't find a way to adjust the curve in the bios. Setting the CPU override to 00 ignores whatever CPU_X setting you put in the IPMI command and leaves them on auto. If you need any more info then let me know. Thanks for getting back to me so quickly.
  4. [Plugin] IPMI for unRAID 6.1+

    I've been having trouble with getting this working for an age now. I have an EP2C602, and everything is detected ok, all the sensors report the correct fan speeds / temperatures etc. ipmi-fan gives me "Your ASRock Board is not supported or setup yet", and the configure button on the fan page gives me the error "Please stop ipmifan [12820] then try again". I had to write a script to control the fan speeds and run it as a cron job, but this has had lots of updates now and I'm sure it's supposed to work. Have I missed something? How do I setup the plugin for my board? Thanks
  5. [Solved] Unable to run kindlegen

    Oh god I feel dumb now... Thanks!
  6. [Solved] Unable to run kindlegen

    Hi all, I'm unable to run kindlegen on UnRaid - I get the following error: cannot execute binary file: Exec format error I know this sounds like a strange issue, but I'm running a calibre web docker that uses kindlegen to convert to .mobi format to send to my kindle. Given that the docker processes run natively, I'm surprised that it doesn't work. I downloaded kindlegen from the following url: http://kindlegen.s3.amazonaws.com/kindlegen_linux_2.6_i386_v2_9.tar.gz, extracted it into a temporary folder, and attempted to execute it using ./kindlegen. Then I tried to chmod +x it just in case, and execute it again. Same result. I read somewhere that usually that means I have the binary for the wrong OS, like trying to execute an ARM binary on linux, but this is the linux binary running on... linux. What am I missing here? I have a feeling I'm missing something very, very simple... Thanks, PJ
  7. is it safe to use networkbridge on a wan connection?

    Is this the link you're looking for? https://forums.lime-technology.com/topic/39966-vm-usb-passthrough-multiple-devices-with-the-same-vendorproduct/
  8. All, I attempted to follow these guides: https://forums.lime-technology.com/topic/35112-guide-passthrough-entire-pci-usb-controller/ https://www.reddit.com/r/unRAID/comments/5irsa9/video_guide_how_to_easily_pass_through_a_usb/ I'm having issues with my particular hardware. I'd also like to apologise for the density of this post! The output of lspci is as follows: root@UnRaid:~# lspci | grep USB 00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 06) 00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 06) 0c:00.0 USB controller: NEC Corporation OHCI USB Controller (rev 43) 0c:00.1 USB controller: NEC Corporation OHCI USB Controller (rev 43) 0c:00.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04) I'm trying to pass through the NEC controller(s). Oddly, the two controllers 0c:00.0 and 0c:00.1 share the same ID: root@UnRaid:~# lspci -nnvv | grep NEC 0c:00.0 USB controller [0c03]: NEC Corporation OHCI USB Controller [1033:0035] (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation USB Controller [1033:0035] 0c:00.1 USB controller [0c03]: NEC Corporation OHCI USB Controller [1033:0035] (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation USB Controller [1033:0035] 0c:00.2 USB controller [0c03]: NEC Corporation uPD72010x USB 2.0 Controller [1033:00e0] (rev 04) (prog-if 20 [EHCI]) Subsystem: NEC Corporation uPD72010x USB 2.0 Controller [1033:00e0] The IOMMU group for these also contains the PCI bridge, but I read somewhere (I can't remember exactly where) that this doesn't usually matter: IOMMU group 16 [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6) [1033:0035] 0c:00.0 USB controller: NEC Corporation OHCI USB Controller (rev 43) [1033:0035] 0c:00.1 USB controller: NEC Corporation OHCI USB Controller (rev 43) [1033:00e0] 0c:00.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04) I blacklisted the three USB controllers in the syslinux configuration (attempted using both vfio-pci.ids and pci-stub.ids), and the controllers then appeared under "Other PCI Devices" in the VM. After adding them, and updating the config, I get the following error when the VM is launched: internal error: qemu unexpectedly closed the monitor: 2017-07-04T09:07:17.805585Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev2,bus=pci.0,addr=0x8: vfio: Error: Failed to setup INTx fd: Device or resource busy 2017-07-04T09:07:17.841241Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev2,bus=pci.0,addr=0x8: Device initialization failed I'm the exact opposite of an expert, so to me that is gibberish; however, after trawling the forums and google, I came across this thread on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2299835 In it, there it is mentioned that the PCIe card (I'm using plain old PCI) doesn't support PCI2.3 INTx disable, and thus requires an entire interrupt line to itself, which can be achieved by dropping anything that shares the interrupt line from it's driver by echoing a 1 into it's remove parameter. After further googling, I have seen that switching slots on the motherboard can change which interrupts are used. Unfortunately, I only have one PCI slot on the motherboard, and I had intended to use the PCIe x4 slot for a PCIe to M.2 adapter, to put in an NVMe SSD and pass it through to a windows guest. I have other, full sized, PCIe slots, but I had intended to use those for GPUs. Further output from lspci indicates that the three USB controllers are using three IRQ lines: root@UnRaid:~# lspci -v -s 0c:00.* 0c:00.0 USB controller: NEC Corporation OHCI USB Controller (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation USB Controller Flags: medium devsel, IRQ 16, NUMA node 0 Memory at df602000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: vfio-pci 0c:00.1 USB controller: NEC Corporation OHCI USB Controller (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation USB Controller Flags: medium devsel, IRQ 17, NUMA node 0 Memory at df601000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: vfio-pci 0c:00.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04) (prog-if 20 [EHCI]) Subsystem: NEC Corporation uPD72010x USB 2.0 Controller Flags: medium devsel, IRQ 18, NUMA node 0 Memory at df600000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 Kernel driver in use: vfio-pci and the output from the INTx check script indicates that my PCI card does indeed not support INTx Disable: root@UnRaid:~# /mnt/user/Downloads/intx_check.sh 0c:00.0 INTx disable support NOT available on 0c:00.0 I can't figure out how to interpret the output of cat /proc/interrupts to find out which other devices are using the same IRQ lines as these controllers, and whether or not it's actually viable to drop the shared devices from their driver. I apologise at how long this is: root@UnRaid:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12 CPU13 CPU14 CPU15 CPU16 CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 CPU24 CPU25 CPU26 CPU27 CPU28 CPU29 CPU30 CPU31 0: 139 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 2-edge timer 1: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 1-edge i8042 8: 17 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 8-edge rtc0 9: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 9-fasteoi acpi 12: 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 12-edge i8042 16: 196428 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 16-fasteoi ehci_hcd:usb1 18: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 18-fasteoi i801_smbus 23: 118 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 23-fasteoi ehci_hcd:usb2 25: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 16384-edge aerdrv, PCIe PME 26: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 18432-edge aerdrv, PCIe PME 28: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 32768-edge aerdrv, PCIe PME 30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 49152-edge aerdrv, PCIe PME 31: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 278528-edge aerdrv, PCIe PME 32: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 458752-edge PCIe PME 33: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 460800-edge PCIe PME 34: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 464896-edge PCIe PME 35: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 466944-edge PCIe PME 36: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 473088-edge PCIe PME 38: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 67141632-edge aerdrv, PCIe PME 40: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 67158016-edge aerdrv, PCIe PME 41: 538561 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 512000-edge ahci[0000:00:1f.2] 42: 544928 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 3670016-edge eth0-rx-0 43: 306504 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 3670017-edge eth0-tx-0 44: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 3670018-edge eth0 45: 213244 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 2621440-edge isci-msix 46: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 2621441-edge isci-msix 47: 32569 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 5767168-edge eth1-rx-0 48: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 5767169-edge eth1-tx-0 49: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 5767170-edge eth1 50: 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI 5242880-edge ahci[0000:0a:00.0] 72: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0 73: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DMAR-MSI 1-edge dmar1 NMI: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Non-maskable interrupts LOC: 3826188 2874305 2830163 2960436 2057691 1954701 1942347 1913162 1338836 1373719 1368412 1444601 1327281 1486811 1357234 1404403 1971863 2946981 2917786 2944396 1760475 1858298 1830511 1824985 1342180 1181314 1353681 1296533 1245308 1322828 1310406 1220719 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Performance monitoring interrupts IWI: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 420049 101399 29767 11440 6423 4132 3169 2871 4450 2663 2761 6610 2510 3404 2427 2576 2420 3244 3149 2814 2317 2341 2261 2827 2502 2156 2635 2391 2411 2288 2386 2430 Rescheduling interrupts CAL: 3509 4387 4313 4689 3977 3819 3324 2999 27663 20874 53354 29626 6826 6654 5872 16614 3204 3044 3066 2867 3089 3207 2964 3013 7043 5967 9490 6675 14728 50251 35245 18269 Function call interrupts TLB: 2886 3755 3673 4041 3331 3181 2680 2349 2249 1987 2543 1836 2045 2220 2131 1884 2601 2417 2431 2227 2452 2587 2491 2389 2104 2731 2201 2436 2338 2221 2003 2436 TLB shootdowns TRM: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Threshold APIC interrupts DFR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Machine check exceptions MCP: 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 Machine check polls ERR: 0 MIS: 0 PIN: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt notification event PIW: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event root@UnRaid:~# I also attempted to blacklist the PCI bridge itself, and pass that through to the guest using the <hostdev> tags, but I got more strange errors that seemed worse than the one above, and it didn't seem like a very good idea to me anyway. Does PCI even support PCI2.3 INTx Disable, or is that a feature of the newer PCIe bus only? Furthermore, given that I can't move the PCI card to another slot, because it is the only one, is it worth buying different hardware? I've seen another USB expansion card that uses a VIA chipset instead of a NEC one; what are the chances that it will support PCI2.3 INTx Disable? If all of this doesn't work, then are there any workarounds, or am I screwed? If you got this far, then thanks for reading! PJ Update: I picked up the new PCI card with the VIA chipset. I will update once I am home and able to fit it. Update 2: Fitted the new VIA chipset card. Running the INTx Disable Check script results in the card not supporting that feature either. I'm starting to think that it's a limitation of the older PCI bus.
  9. EP2C602 - IPMI Fan Control

    Yeah I had some issues. They haven't happened since I switched over to the intel chip SAS ports though. Which ones are you using?
  10. [SOLVED] Loss of Networking and Unresponsive - Complete System Hang

    Switching the SATA ports has led to a stable configuration, at least for the last two days. Does anyone know what the issue with those Marvell controllers is, and if it will be fixed?
  11. EP2C602 - IPMI Fan Control

    My motherboard is set to Smart Fan but it never changes the fan speed, that's why I wrote the script. I need to check mine, but which BIOS version are you running? I'm wonering if there was an update that perhaps fixed this. Either way, the Case Fans aren't controllable based on temperature as far as I can tell...
  12. [SOLVED] Loss of Networking and Unresponsive - Complete System Hang

    Okay thanks, I'll have a go when I get access to the PC later tonight.
  13. [SOLVED] Loss of Networking and Unresponsive - Complete System Hang

    Ah okay, I need to rebuild my array now because disk 1 has the red x next to it. I'm assuming that if I move the disks across to different SATA ports, I'll lose all my data, unless I have a fully working array and move them one at a time with a rebuild between disk moves?
  14. [SOLVED] Loss of Networking and Unresponsive - Complete System Hang

    That parity drive has had those two reallocated sectors for a few years IIRC. I've been keeping an eye on it since i noticed, and it's never gone up, so it wasn't something I worried about. I just can't work out why it would be freezing the way it is, other than the age of the disks. The cache and parity disks are attached to the onboard controller, the other two are connected via the marvell chip. Due to the restrictions in the case, it'd be a bit of a pain to move them over to the other intel SCU connectors on the board, but it could be done. Is the marvell chip known to cause issues?
  15. [SOLVED] Loss of Networking and Unresponsive - Complete System Hang

    Are they the same as the two sets of diagnostics files i've attached in the two .zip files on my original post?
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.