So recently I was looking at the log files for my unraid as Plex started to run very slowly and transcoding was having a hard time. I noticed that the log file kept repeating this sequence over and over:

 

Jun 21 22:26:09 Tower kernel: mptbase: ioc0: LogInfo(0x31120200): Originator={PL}, Code={Abort}, SubCode(0x0200) cb_idx mptbase_reply

Jun 21 22:26:08 Tower kernel: mptbase: ioc0: LogInfo(0x31120200): Originator={PL}, Code={Abort}, SubCode(0x0200) cb_idx mptscsih_io_done

 

I am really not sure what the above means and any help would be greatly appreciated so I can get to the bottom of why my server is starting to run sluggish.

 

Thank you community!

 

EDIT: Running Unraid 6.1.9

syslog.txt

Please see Need help? Read me first!, and attach the diagnostics zip.  We appreciate the syslog, but with v6 we prefer the full diagnostics, which includes the syslog plus much more.

My apologies RobJ. I have attached the ZIP file now.

 

Thanks for the heads-up, I'll remember that for the future.

tower-diagnostics-20160622-2202.zip

I'm sorry, I really don't have anything helpful to say.  I've looked long and hard online, and there are other instances of those messages, but no help anywhere for them.  I also tried to learn something useful to interpret the codes in them, but found nothing.  Only the Abort is clear, which usually means breakage and/or implies poor performance, which you already knew.  You know it's an issue with a drive attached to the MPT SAS card, and perhaps you can figure out which drives are involved in the Plex transcoding, being read from, or written to, or used for temp storage.  Some additional comments -

 

* The first syslog was just repeats of those 2 lines, did not have the first errors encountered.  The diagnostics was after a fresh boot, and had no MPT related issues at all, so neither were able to provide any additional clues.  However, since you've upgraded, sometimes more recent drivers fix issues, so it's possible you won't see the problem again.  But if you do, please get the diagnostics from that session.  Most useful would be a complete syslog that covered the period the issues begin in.

 

* Your diagnostics were quite puzzling!  Your first post indicates you were running 6.1.9, the syslog and vars from the diagnostics indicate you are now running 6.2-beta23, but the diagnostics contents are more consistent with 6.1.9!  There are 5 new items added to the diagnostics as of beta23, and this diagnostics zip only had one of them, which I don't understand at all.  It's possible your update to beta23 was only partial(?).  I would check the Plugins page for additional updates to the Dynamix plugin.

 

* The syslog indicates that 2 of your onboard SATA ports are using an emulated IDE mode.  It's usually better (a bit faster and safer) to change that to a native SATA mode like AHCI.  When you next boot, go into the BIOS settings and change that to AHCI if possible.

 

* Your BIOS is somewhat old, from 2010, and I noticed considerable workarounds for it.  You may want to check for a newer BIOS.  And you might want to check for newer firmware for the SAS card too, it could fix the issues.

 

* I noticed you have Bonding on, but only one NIC.  Wouldn't it be better to turn bonding off?  (But you may know of advantages I don't!)

I truly appreciate all the help and advice you have given me Rob, not just in this post, but in prior posts!

 

I did upgrade to 6.2.0-beta23 before I replied to your comment so that is why some of the log shows 6.1.9 and other parts show the new version (I didn't fully start everything because of the errors generated)

 

I figured out that my "side drive" that I use to hold SickBeard, SAB, and Plex was failing so I have replaced that with a new SSD (just having trouble getting that working now )

 

I did a lookup for my BIOS and I have the latest version, it is just an old motherboard so the BIOS is going to be outdated

 

I tried to change the emulated IDE made to AHCI, but it said I would lose all the data so I did not do that change as I can't afford to lose the data now

 

The bonding mode is an oversight on my part and I will change that on my next reboot.

 

To sum up, my drive I refer to as Xfiles that is not part of the array or cache seems to be failing and I have replaced it with a 480GB SSD. My problems aren't over yet though as now I'm having issues getting everything working with the new drive as when I mount the drive to /mnt/Xfiles it is only showing 7GB available, so I have to figure out why. Again, I appreciate all the help and advice you have provided to me!