February 21, 20197 yr Hello, i m using Unraid since 4 month right now. I switcht last week to new hardware. New MB New CPU New RAM New Networkcard. The updating was pretty easy. All works good. I now use bonding mode balance - alb of my MB 1GB nic and my PCI 1 GB nic. It works good and i can copy with 200MB´s. On monday i tried to copy again and after some sec´s the transfer broke down to somethink like 3 mb´s. i look via Putty at the Server nothink written there. I look via monitor at the Server and there stands: Tower login : Disabling IRQ #16 i startet my server new and all work fine again. Today it comes again. all the same only 3mb´s transfer and again Tower login : Disabling IRQ #16 I m new at unraid and at linux. Do you think it´s becaus the bonding mode? Can someone help me? I read in the Form that you need the diagnostics file. Thanks for you help right now. - redQs tower-diagnostics-20190221-1559.zip
February 21, 20197 yr Community Expert SASLP uses IRQ16, replacing the controller will fix the problem, ideally with an LSI HBA, bios update, using a different slot if available might also help.
February 21, 20197 yr Author thanks for the fast answer. you mean a bios update for my motherboard might help also? can you tell me where you saw that SASLP uses IRQ16?
February 21, 20197 yr Community Expert 13 minutes ago, redQs said: you mean a bios update for my motherboard might help also? Yes. 13 minutes ago, redQs said: can you tell me where you saw that SASLP uses IRQ16? I didn't, just assumed since they always seem to use it and it would explain the slow performance once the IRQ gets disabled, but you can confirm with: cat /proc/interrupts
February 21, 20197 yr Author BIOS is the latest update on it. I just use this Controller: SuperMicro AOC-SASLP-MV8 I just use it for get more SATA ports so i dont use raid or anythink. Bevor i move too the new hardware it work´s all good. The think is this PCI slot must work fine. Becaus bevor i moved it intoo my unraid it was my gaming rig an in this slot was my 1080. But i started new right now and try an other PCI slot.
February 21, 20197 yr Community Expert 4 minutes ago, redQs said: The think is this PCI slot must work fine. I not saying the slot is bad, just that in a different slot IRQ might not get disabled.
February 21, 20197 yr Author it comes again. different PCI slot. but the transfer speed dont break down. cat /proc/interrupts says this. does this help you? CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 13 0 0 0 0 0 0 0 IO-APIC 2-edge timer 8: 0 0 0 0 0 0 54 0 IO-APIC 8-edge rtc0 9: 0 0 0 0 0 0 0 0 IO-APIC 9-fasteoi acpi 16: 0 0 0 100000 0 0 0 0 IO-APIC 16-fasteoi ehci_hcd:usb1 17: 0 0 0 0 1196014 0 0 0 IO-APIC 17-fasteoi mvsas 18: 0 0 0 0 0 0 0 0 IO-APIC 18-fasteoi i801_smbus 23: 0 0 0 0 96 0 0 0 IO-APIC 23-fasteoi ehci_hcd:usb2 24: 0 0 0 0 0 0 0 0 PCI-MSI 327680-edge xhci_hcd 25: 0 0 0 0 0 0 13750 0 PCI-MSI 2621440-edge xhci_hcd 26: 0 0 0 0 0 0 0 0 PCI-MSI 2621441-edge xhci_hcd 27: 0 0 0 0 0 0 0 0 PCI-MSI 2621442-edge xhci_hcd 28: 0 0 0 0 0 0 0 0 PCI-MSI 2621443-edge xhci_hcd 29: 0 0 0 0 0 0 0 0 PCI-MSI 2621444-edge xhci_hcd 30: 0 0 0 0 0 0 0 0 PCI-MSI 2621445-edge xhci_hcd 31: 0 0 0 0 0 0 0 0 PCI-MSI 2621446-edge xhci_hcd 32: 0 0 0 0 0 0 0 0 PCI-MSI 2621447-edge xhci_hcd 33: 0 0 93062 0 0 0 0 0 PCI-MSI 512000-edge ahci[0000:00:1f.2] 34: 0 0 0 0 0 0 0 0 PCI-MSI 3145728-edge ahci[0000:06:00.0] 35: 0 0 0 0 0 0 0 0 PCI-MSI 3670016-edge ahci[0000:07:00.0] 36: 0 42208229 0 0 0 0 0 0 PCI-MSI 2097152-edge eth1 37: 0 0 0 6194125 0 0 0 0 PCI-MSI 409600-edge eth0 NMI: 24 8 0 0 10 9 0 0 Non-maskable interrupts LOC: 650503 1248013 711463 982474 796734 707417 709708 705084 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 24 8 0 0 10 9 0 0 Performance monitoring interrupts IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 188600 227830 32341 127065 15282 10074 5030 5259 Rescheduling interrupts CAL: 26297 32439 19056 17237 17020 20230 19347 18189 Function call interrupts TLB: 20984 29165 15495 13616 15124 18413 17602 16300 TLB shootdowns TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 0 0 0 0 Machine check exceptions MCP: 33 34 34 34 34 34 34 34 Machine check polls HYP: 0 0 0 0 0 0 0 0 Hypervisor callback interrupts HRE: 0 0 0 0 0 0 0 0 Hyper-V reenlightenment interrupts HVS: 0 0 0 0 0 0 0 0 Hyper-V stimer0 interrupts ERR: 0 MIS: 0 PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event NPI: 0 0 0 0 0 0 0 0 Nested posted-interrupt event PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event Edited February 21, 20197 yr by redQs
February 22, 20197 yr Community Expert It's now using IRQ17 which is unusual, but if IRQ16 gets disabled it won't affect the HBA.
February 22, 20197 yr Author So i can let it run like this? why did i got like that high counter on some other interrupts. Is this normal?
February 22, 20197 yr Community Expert 14 minutes ago, redQs said: So i can let it run like this? If everything is working correctly no problem. 14 minutes ago, redQs said: why did i got like that high counter on some other interrupts. Is this normal? Yes.
Archived
This topic is now archived and is closed to further replies.