ridley Posted June 26, 2016 Posted June 26, 2016 I noticed a Red Ball on Disk 6 Yesterday so I unassigned it and replaced it with a larger drive, but the rebuild seems to be going incredibly slowly at 2.6mb/s. I have looked through the syslog and cannot see anything (to my very much untutored eye) that is wrong. Any suggestions? syslog-2016-06-26.txt
ridley Posted June 28, 2016 Author Posted June 28, 2016 Can someone please have a look at the SYSLOG, my rebuild has been running for about 2 days and is still only going at 2.6mb/s and I cannot see anything wrong in the log. Can you? Should I stop it reseat all the cables and try again? syslog-2016-06-28.txt
RobJ Posted June 28, 2016 Posted June 28, 2016 Basically, you need to upgrade. You are running v5.0-rc12a which is quite old, with bugs long fixed. Syslog shows your problems started very quickly with IRQ16 being ignored. The first thing attached to it was one of the USB controllers, so that didn't hurt as far as I can see. But then it was assigned to mvsas, the module handling all disk access for the SAS card and all of its attached drives. An IRQ that isn't handled is a software bug somewhere (driver, driver support modules, motherboard, BIOS, etc). When the kernel detects it, it disables the IRQ, as untrustable, and that can be catastrophic or at least cause enormous slowdowns as the system switches to much slower polling based communications. I'm somewhat surprised the drives were not dropped, but since that didn't happen, mvsas apparently found slower ways to communicate and keep going. You need to upgrade your unRAID (Upgrading to UnRAID v6 guide). Your BIOS is from 2012 and showed other issues, so check also for a BIOS upgrade for your motherboard. You are also getting warnings from your UPS that your UPS battery needs to be replaced. And there's a misconfiguration in the email notification setup, but don't worry about it. It should be cleaned up once you upgrade to v6.
ridley Posted June 28, 2016 Author Posted June 28, 2016 Thanks for that. It has run at an OK speed before for the monthly parity check etc, so it seems strange that it is going slow now. Should I let it finish before upgrading, should only take a week or so or finish and upgrade? Or should I finish turn off USB in the BIOS and see what happens?
RobJ Posted June 29, 2016 Posted June 29, 2016 An unhandled, disabled interrupt can only be enabled by a reboot, so a reboot seems sensible to me. IRQ assignments, like a number of startup assignments in the kernel, can be somewhat random, perhaps why it has worked before. The syslog message "irq 16: nobody cared" is not good, but only harmful if IRQ16 is assigned to something you are using. If you drop down a little in the syslog from that message, you see "handlers" and one or more will be listed. In your case (happened 3 times), you'll just see a USB handler (usb_hcd_irq) the first time, which may be harmless as you would have seen a number of other errors if it had been the one your flash drive was using! But on the next error, the mvsas handler (mvs_interrupt) was involved, and that's bad. If you see that, you might as well reboot again, until you don't have an IRQ16 error message, or you do but it only involves the USB handler, AND the system is working fine. You need a USB controller on, at least the one your unRAID boot drive is using.
Squid Posted June 29, 2016 Posted June 29, 2016 An unhandled, disabled interrupt can only be enabled by a reboot, so a reboot seems sensible to me. IRQ assignments, like a number of startup assignments in the kernel, can be somewhat random, perhaps why it has worked before. The syslog message "irq 16: nobody cared" is not good, but only harmful if IRQ16 is assigned to something you are using. If you drop down a little in the syslog from that message, you see "handlers" and one or more will be listed. In your case (happened 3 times), you'll just see a USB handler (usb_hcd_irq) the first time, which may be harmless as you would have seen a number of other errors if it had been the one your flash drive was using! But on the next error, the mvsas handler (mvs_interrupt) was involved, and that's bad. If you see that, you might as well reboot again, until you don't have an IRQ16 error message, or you do but it only involves the USB handler, AND the system is working fine. You need a USB controller on, at least the one your unRAID boot drive is using. Looked up an old thread of yours talking about all of this How to resolve IRQ Conflicts in UnRaid If you have a decent motherboard manual, then you might also be able to work around the issue by playing with slot assignments http://i46.photobucket.com/albums/f109/squidaz/Untitled_zpsqqhqfhel.png[/img]
ridley Posted June 29, 2016 Author Posted June 29, 2016 Tried rebooting several times without luck. Would upgrading to V6 possibly help? Could it be an issue with having two SAS MVS cards in there?
RobJ Posted June 30, 2016 Posted June 30, 2016 Would upgrading to V6 possibly help? Since it's a bug somewhere, I'd upgrade everything you can. Upgrade unRAID to 6.1.9. Try to upgrade the motherboard BIOS. And try to upgrade the firmware on the SAS cards. Could it be an issue with having two SAS MVS cards in there? Don't know, but probably not. Did it work with the 2 of them before?
ridley Posted June 30, 2016 Author Posted June 30, 2016 It seemed to, at least it did the monthly parity check at approx 30mb/s.
ridley Posted July 2, 2016 Author Posted July 2, 2016 Wow: Upgraded to 6.1.9 rebuilding at 30Mb/s Fingers crossed this might be solved time will tell and I will let you know.
ridley Posted July 3, 2016 Author Posted July 3, 2016 OK all done and rebuild completed. Just checking everything now. Thanks for all the help. BTW V6 is really quite nice!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.