This error started about 6 months ago and I was told it was no big deal but it is driving me nuts. I was told it was a USB issue but only thing in USB is keyboard / mouse and connection to UPS which are all working fine.

 

irq 19: nobody cared found on your server

 

I have uploaded the diag file too... Yes I know I have an issue with drive 3 working that out with another member.

 

Thanks ahead for any help to remove this error.

unraid-diagnostics-20171118-1754.zip

Wow been a week now no one knows how to fix this issue?

On 18/11/2017 at 11:06 PM, gsd2012 said:

I was told it was a USB issue but only thing in USB is keyboard / mouse and connection to UPS which are all working fine.

 

There's nothing new to tell, a bios update may help, other than that ignore or get a different board.

Yeah did Bios Update. I have ignored it but it still fills up in Fixer apps, is there a way to ignore without it posting all the time?

Did you google  irq 19: nobody cared  and do a bit of research on the problem.  I found several threads there might throw some light on your problem.  I am afraid that it may be more of a hardware related issue than a software problem. 

I had this same error with my the first unRAID server I built back in late 2011.  I tried two different motherboards from two different manufacturers and a couple of BIOS revisions on each.  I continued to have the same issue.  It is definitely hardware related. 

 

In my case, it was not just a nuisance error.  It caused the throughput to tank on all the disks attached to a PCIE SATA card.  I finally narrowed it down to (in my case) switching the input on my monitor.  I had my desktop PC and unRAID server connected to the same monitor and every time I switched the input to the unRAID input I got the "IRQ xx: nobody cared" message and the disk slowdown.  In my case it was IRQ 16.  I solved it by simply attaching a dedicated monitor to my server. I got lots of great suggestions from the community, but, nothing worked until I finally figured out what caused the problem and simply quit doing that. 

 

There is no single cause for this issue.  It is purely hardware related and you have to figure out what the conflict is.  At least in your case it just appears to be an annoying message without detrimental side effects (other than filling the log).