After running the Fix Common Problems plugin, I received the error "Call Traces found on your server."  Per the suggested fix, I downloaded the diagnostics and started looking through the files.  In the "syslog" file I found the lines below that appear to be the "Call Trace" but I can't decipher what the issue(s) might be.  I'm hoping one of the fine people here can assist me!  Thanks for taking the time to look.

 

Nov  9 02:52:55 Tower kernel: Call Trace:
Nov  9 02:52:55 Tower kernel: [<ffffffff8129691e>] xfs_vm_releasepage+0x16/0x99
Nov  9 02:52:55 Tower kernel: [<ffffffff810c5502>] try_to_release_page+0x3e/0x47
Nov  9 02:52:55 Tower kernel: [<ffffffff810d5fb6>] shrink_page_list+0x63f/0x7f7
Nov  9 02:52:55 Tower kernel: [<ffffffff810d6941>] shrink_inactive_list+0x2ee/0x40d
Nov  9 02:52:55 Tower kernel: [<ffffffff810d720d>] shrink_node_memcg+0x4b6/0x658
Nov  9 02:52:55 Tower kernel: [<ffffffff810d746e>] shrink_node+0xbf/0x27a
Nov  9 02:52:55 Tower kernel: [<ffffffff810d746e>] ? shrink_node+0xbf/0x27a
Nov  9 02:52:55 Tower kernel: [<ffffffff810d813c>] kswapd+0x4a4/0x59e
Nov  9 02:52:55 Tower kernel: [<ffffffff810d7c98>] ? mem_cgroup_shrink_node+0x86/0x86
Nov  9 02:52:55 Tower kernel: [<ffffffff81063939>] kthread+0xdb/0xe3
Nov  9 02:52:55 Tower kernel: [<ffffffff8110c273>] ? kfree+0xdf/0xfa
Nov  9 02:52:55 Tower kernel: [<ffffffff8106385e>] ? kthread_park+0x52/0x52
Nov  9 02:52:55 Tower kernel: [<ffffffff8105c16c>] ? umh_complete+0x20/0x20
Nov  9 02:52:55 Tower kernel: [<ffffffff8105c28b>] ? call_usermodehelper_exec_async+0x11f/0x128
Nov  9 02:52:55 Tower kernel: [<ffffffff8167f785>] ret_from_fork+0x25/0x30
Nov  9 02:52:55 Tower kernel: Code: f6 ff ff 48 83 c4 38 5b 5d c3 55 c7 02 00 00 00 00 48 89 e5 c7 06 00 00 00 00 48 8b 07 f6 c4 08 75 02 0f 0b 48 8b 4f 30 48 89 c8 <48> 8b 38 f7 c7 00 10 00 00 74 08 c7 02 01 00 00 00 eb 11 48 8b 
Nov  9 02:52:55 Tower kernel: RIP  [<ffffffff812968d9>] xfs_count_page_state+0x21/0x50
Nov  9 02:52:55 Tower kernel: RSP <ffffc90001a3ba90>
Nov  9 02:52:55 Tower kernel: CR2: 0000000017919273
Nov  9 02:52:55 Tower kernel: ---[ end trace 06e94b055fcc8e40 ]---

 

Probably related to one of your drives formatted XFS.  The relevant info would be listed before the trace.  Odds on you'll need to Check Disk File System on that drive

Edited November 10, 20178 yr by Squid

 

7 minutes ago, Squid said:

Probably related to one of your drives formatted XFS.  The relevant info would be listed before the trace.  Odds on you'll need to Check Disk File System on that drive

 

 

Squid, thanks for the info.  Below is the info before the Call Trace.  How would I know which drive to check?  Thanks again!!

 

ov  9 02:52:55 Tower kernel: BUG: unable to handle kernel paging request at 0000000017919273
Nov  9 02:52:55 Tower kernel: IP: [<ffffffff812968d9>] xfs_count_page_state+0x21/0x50
Nov  9 02:52:55 Tower kernel: PGD 10057f067 
Nov  9 02:52:55 Tower kernel: PUD 10079a067 
Nov  9 02:52:55 Tower kernel: PMD 0 
Nov  9 02:52:55 Tower kernel: 
Nov  9 02:52:55 Tower kernel: Oops: 0000 [#1] PREEMPT SMP
Nov  9 02:52:55 Tower kernel: Modules linked in: vhost_net tun vhost macvtap macvlan kvm_intel kvm md_mod xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat it87 hwmon_vid bonding r8169 mii x86_pkg_temp_thermal coretemp i2c_i801 i2c_smbus i2c_core mpt3sas ahci raid_class libahci scsi_transport_sas [last unloaded: md_mod]
Nov  9 02:52:55 Tower kernel: CPU: 2 PID: 600 Comm: kswapd0 Not tainted 4.9.30-unRAID #1
Nov  9 02:52:55 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. P67A-UD3-B3/P67A-UD3-B3, BIOS F4 04/13/2011
Nov  9 02:52:55 Tower kernel: task: ffff88040c9aa640 task.stack: ffffc90001a38000
Nov  9 02:52:55 Tower kernel: RIP: 0010:[<ffffffff812968d9>]  [<ffffffff812968d9>] xfs_count_page_state+0x21/0x50
Nov  9 02:52:55 Tower kernel: RSP: 0018:ffffc90001a3ba90  EFLAGS: 00010296
Nov  9 02:52:55 Tower kernel: RAX: 0000000017919273 RBX: ffffea00036d0c40 RCX: ffff88000bad8000
Nov  9 02:52:55 Tower kernel: RDX: ffffc90001a3baa4 RSI: ffffc90001a3baa0 RDI: 00000000018ab515
Nov  9 02:52:55 Tower kernel: RBP: ffffc90001a3ba90 R08: ffffea00036d0c40 R09: 0000000000000230
Nov  9 02:52:55 Tower kernel: R10: ffff880012334800 R11: 000000000000002c R12: ffffc90001a3be58
Nov  9 02:52:55 Tower kernel: R13: ffff880013bdefb0 R14: ffffc90001a3bc38 R15: ffffea00036d0c60
Nov  9 02:52:55 Tower kernel: FS:  0000000000000000(0000) GS:ffff88041f480000(0000) knlGS:0000000000000000
Nov  9 02:52:55 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov  9 02:52:55 Tower kernel: CR2: 0000000017919273 CR3: 0000000115867000 CR4: 00000000000406e0
Nov  9 02:52:55 Tower kernel: Stack:
Nov  9 02:52:55 Tower kernel: ffffc90001a3bab0 ffffffff8129691e 0000000100000000 ffffea00036d0c40
Nov  9 02:52:55 Tower kernel: ffffc90001a3bac0 ffffffff810c5502 ffffc90001a3bba8 ffffffff810d5fb6
Nov  9 02:52:55 Tower kernel: ffff88040c9aa640 ffffc90001a3bb70 ffffc90001a3bc20 ffffc90001a3bc10
Nov  9 02:52:55 Tower kernel: Call Trace:

 

Just post the whole file

 

9 minutes ago, Squid said:

Just post the whole file

 

 

Here is the text from the file or you can look at the file itself, as it is attached as well.  Thanks for your help, Squid!!

 

Edit:

Removed syslog text in code box (I thought it would put a set size box, not lengthen the thread to the size of the code).  Sorry about that.

 

syslog.txt

Edited November 10, 20178 yr by FraxTech