January 5, 20179 yr So I had this issue of very slow parity checks a few months ago, then I had a couple months where they went at normal 80mb/s speeds. Now the last few have been slow again 2 mb/s range. I've tried swapping out my sata card, which I recently changed when I did a motherboard and processor update, and it made no difference. Also, I just went through today and made sure all my cables were tight and seated. Any help or places to start looking would be appreciated. Occasionally, I also get a very slow file transfer as well which I assume is a related issue to this. syslog.txt unRAID-6.2.4.txt unraid-diagnostics-20170105-1549.zip
January 5, 20179 yr For V6, instead of syslog you should always post the complete diagnostics zip by going to Tools - Diagnostics.
January 5, 20179 yr IRQ16 was disabled, it's used by the SASLP, this explains the parity check speed slowing to a crawl, rebooting will fix but it will probably happen again. Try bios and/or firmware updates and using the SASLP in a different slot if available.
January 5, 20179 yr Author Rebooting does not help, did that several times today. So you think I need a bios update for my motherboard or the SASLP?
January 5, 20179 yr Reboot will help until it happens again, and it can be almost immediately , look for this in your syslog: Jan 5 15:11:11 unraid kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Jan 5 15:11:11 unraid kernel: CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.30-unRAID #2 Jan 5 15:11:11 unraid kernel: Hardware name: MSI MS-7850/Z97 PC Mate(MS-7850), BIOS V4.10 08/11/2015 Jan 5 15:11:11 unraid kernel: 0000000000000000 ffff88021fb03e70 ffffffff8136f79f ffff8800d4dd1800 Jan 5 15:11:11 unraid kernel: 0000000000000000 ffff88021fb03e98 ffffffff8107f8ce ffff8800d4dd1800 Jan 5 15:11:11 unraid kernel: 0000000000000000 0000000000000010 ffff88021fb03ed0 ffffffff8107fb9b Jan 5 15:11:11 unraid kernel: Call Trace: Jan 5 15:11:11 unraid kernel: <IRQ> [<ffffffff8136f79f>] dump_stack+0x61/0x7e Jan 5 15:11:11 unraid kernel: [<ffffffff8107f8ce>] __report_bad_irq+0x2b/0xb4 Jan 5 15:11:11 unraid kernel: [<ffffffff8107fb9b>] note_interrupt+0x1a0/0x22e Jan 5 15:11:11 unraid kernel: [<ffffffff8107d8d1>] handle_irq_event_percpu+0xe2/0xf0 Jan 5 15:11:11 unraid kernel: [<ffffffff8107d915>] handle_irq_event+0x36/0x54 Jan 5 15:11:11 unraid kernel: [<ffffffff810803c5>] handle_fasteoi_irq+0x8c/0xf4 Jan 5 15:11:11 unraid kernel: [<ffffffff8100e0e8>] handle_irq+0x17/0x1b Jan 5 15:11:11 unraid kernel: [<ffffffff8100db3e>] do_IRQ+0x46/0xc2 Jan 5 15:11:11 unraid kernel: [<ffffffff8162a6c2>] common_interrupt+0x82/0x82 Jan 5 15:11:11 unraid kernel: <EOI> [<ffffffff81508581>] ? cpuidle_enter_state+0xf0/0x148 Jan 5 15:11:11 unraid kernel: [<ffffffff8150853a>] ? cpuidle_enter_state+0xa9/0x148 Jan 5 15:11:11 unraid kernel: [<ffffffff815085fb>] cpuidle_enter+0x12/0x14 Jan 5 15:11:11 unraid kernel: [<ffffffff810765ca>] call_cpuidle+0x4e/0x50 Jan 5 15:11:11 unraid kernel: [<ffffffff81076752>] cpu_startup_entry+0x186/0x1fd Jan 5 15:11:11 unraid kernel: [<ffffffff81033d5f>] start_secondary+0xf4/0xf7 Jan 5 15:11:11 unraid kernel: handlers: Jan 5 15:11:11 unraid kernel: [<ffffffff814b1e61>] usb_hcd_irq Jan 5 15:11:11 unraid kernel: [<ffffffffa009560a>] mvs_interrupt [mvsas] Jan 5 15:11:11 unraid kernel: Disabling IRQ #16
January 5, 20179 yr Bios update for the board and changing slot it's what usually works best, try a different slot first if you can.
January 5, 20179 yr Author Ok, Thanks. I switched to the PCI E2 slot instead of the PCI E4 and started another parity check. It's around 50mb/s so far. Is that going to be a slower slot than the other? Should I do a bios update to get it working in the PCI E4 slot?
January 5, 20179 yr Author Well, I take it back. Ran great for about 15 minutes and then slowed to 2.7MB/s. Guess I need to try the bios update as I only have the 2 PCI slots available. unraid-diagnostics-20170105-1654.zip
January 5, 20179 yr Is there any point in trying the "irqpoll" boot option referred to in the error message? This suggests it might help where all else has failed, but obviously try a BIOS update first.
January 5, 20179 yr Worth a shot, upgrading to v6.3-rc may also work, would try that first if the bios update doesn't fix it.
January 5, 20179 yr Author Updated my bios and I'm 30 minutes into a parity check and haven't had the error yet. So far so good. I will look into those options if I have more issues. Thanks guys.
January 7, 20179 yr Author The check finished without the irq error. Averaged 80MB/s. Thanks for the help again...
August 7, 20178 yr Author I'm still having this IRQ16 disabled issue. I've changed slots for the SASLP, upgraded motherboard bios, replaced SASLP with a SAS2LP, and also tried irqpoll boot option which gave me an endless barrage of log errors. Any other ideas before i replace the motherboard? unraid-diagnostics-20170807-1449.zip
August 7, 20178 yr Not related to your issue, but you have Community Repositories installed. Uninstall it and install Community Applications. Seriously doubt if CR will work under 6.3.5 and may have adverse effects on the docker tab.
August 7, 20178 yr Author 2 minutes ago, Squid said: Not related to your issue, but you have Community Repositories installed. Uninstall it and install Community Applications. Seriously doubt if CR will work under 6.3.5 and may have adverse effects on the docker tab. Done. Thanks.
Archived
This topic is now archived and is closed to further replies.