[Plugin] CA Fix Common Problems

[JustinChase]

30 minutes ago, Squid said:

58846 vs 58946 refer to setting up @binhex's VPN apps in either VPN mode or normal mode AFAIK.  You could term it a false positive, since that's how it's suggested to set up the apps (by removing one of them).  It's been previously suggested to me to put in a special test for binhex templates and I have elected not to because IMHO if the ports are listed in the template but not on your installed app, then it is an error / warning.  That, and its easy to ignore  (IE: don't want to go down the road of having checks for individual apps where its perfectly acceptable and even desired in some cases to set it up as such - I just don't have that much time on my hands)

 

 

The extended tests are basically full file system checks - permissions, duplicate filenames.  What you wanted to hit was "Re-Scan"

 

 

These are the warnings / errors that are ignored that are found in the last scan

 

These is the list of ALL errors / warning that you've ignored, regardless of whether its found on the last scan or not.  It's there to let you re-monitor an error that you've previously ignored, it isn't currently present, but you want to be alerted for should it happen again.

 

thanks for the quick response.  I'm curious where your test determines that I'm 'missing' 58946, since it's not listed in the docker settings (until I just added it)?  Do you compare it to the template you install from?  If so, I suspect that template has been changed since I originally installed my docker (very likely).  If not from your template, how do you determine it's missing?

 

I don't expect you to add special tests for certain dockers, for the reasons you've stated.

 

I would like it if I could get the 4 errors I see to consolidate to just the one error it's actually finding, it would just feel less 'messed up' with the one error, instead of showing 2 under errors, and 2 more (the same?) under all errors.

 

But, as I said I respect your time, and if it's not easy to do, so be it.

 

I started to re-scan before writing this, so maybe adding the 58946 to the docker will take care of all this; but it's not finished scanning yet, so I'm not sure.

 

Anyway, thanks again.

 

**it's still scanning, should it take this long?

Edited January 19, 2018 by JustinChase
update

[Squid]

30 minutes ago, JustinChase said:

thanks for the quick response.  I'm curious where your test determines that I'm 'missing' 58946, since it's not listed in the docker settings (until I just added it)?  Do you compare it to the template you install from?  If so, I suspect that template has been changed since I originally installed my docker (very likely).  If not from your template, how do you determine it's missing?

Its from the default template (current version)

 

30 minutes ago, JustinChase said:

**it's still scanning, should it take this long?

24 Minutes...  No it shouldn't.  1 minute tops

[JustinChase]

15 minutes ago, Squid said:

Its from the default template (current version)

 

24 Minutes...  No it shouldn't.  1 minute tops

 

that page gives me a warning about my adblocker, but ghostery shows nothing for that page, uBlock Origin only shows the server IP and paypalobjects (which really concerns me now that I've seen it), but both are green/allowed.

 

I'm not sure what it's detecting as an ad blocker, nor how/where to whitelist.

 

I opened another tab, went to the server, and can navigate fine, and stopped the array.  Went back to the fix common problems and it pops up telling me its scanning and blocks navigation on/from that page.

 

i guess I'll have to reboot the server??

 

No, the scanning window went away, so I restarted the array, and checked again, and it's showing an error 'array not started'.  it's as if it's not refreshing.  I re-scanned again, and it finished quick enough, and now I have no errors

 

I am concerned about the redirects though, paypal objects and github (screenshot below).  github is fine, but why is paypay objects.com being linked from this page?

Edited January 19, 2018 by JustinChase
more info

[Squid]

17 minutes ago, JustinChase said:

I'm not sure what it's detecting as an ad blocker, nor how/where to whitelist.

The ad blocker test ( @bonienl supplied it to me way back when ) means that your browser is removing an element on the FCP page that's designed to trigger ad-blockers (but is in no way an ad - pretty standard test AFAIK).  The test is there because some ad blockers do interfere with the operation of unRaid's UI.  Obviously your's isn't, but is still triggering the error.  I wouldn't worry about it.

 

17 minutes ago, JustinChase said:

paypal objects

 

Click "HELP" or Credits, and all will be made clear. 

 

GitHub is my avatar.  And it is https to begin with.

 

 

Edited January 19, 2018 by Squid

[JustinChase]

2 minutes ago, Squid said:

The ad blocker test ( @bonienl supplied it to me way back when ) means that your browser is removing an element on the FCP page that's designed to trigger ad-blockers (but is in no way an ad - pretty standard test AFAIK).  The test is there because some ad blockers do interfere with the operation of unRaid's UI.  Obviously your's isn't, but is still triggering the error.  I wouldn't worry about it.

 

Click "HELP" or Credits, and all will be made clear

 

I was just concerned the ad block issue is/was related to the scanning taking forever.  I just went back to the page and the scanning window came back up; even though it had finished the last time i was on the page.

 

I checked credits and see where it comes from.  I didn't realize it would scan that part of the page if credits window wasn't opened.  Guess I was wrong.  Link works

 

Thanks again for everything,

[Squid]

12 minutes ago, JustinChase said:

Link works

Thank you.  Always appreciate it

[cherritaker]

Is anyone having trouble with the plugin being stuck on the Scanning screen. I recently noticed this after updating to 6.4.0 and ran into this issue after running the plugin it never finished scanning and made my server unresponsive. If i tried to stop it or reboot or shutdown it would just hang. I had to hard reset it. I installed a new clean version of Unraid on a new flash drive and ran into the same issue after over a hour still stuck on the scanning screen. And once again after attempting to stop uraid or reboot it just hangs. Doesn't stop it and becomes unresponsive. This is a screenshot of my motherboard ipmi that i don't quite understand when i run the plugin. Any help would be appreciated.

[Squid]

Is anyone having trouble with the plugin being stuck on the Scanning screen. I recently noticed this after updating to 6.4.0 and ran into this issue after running the plugin it never finished scanning and made my server unresponsive. If i tried to stop it or reboot or shutdown it would just hang. I had to hard reset it. I installed a new clean version of Unraid on a new flash drive and ran into the same issue after over a hour still stuck on the scanning screen. And once again after attempting to stop uraid or reboot it just hangs. Doesn't stop it and becomes unresponsive. This is a screenshot of my motherboard ipmi that i don't quite understand when i run the plugin. Any help would be appreciated.

You would need to post what's showing before that. Ideally the diagnostics or at least the syslog

 

Sent from my SM-T560NU using Tapatalk

 

 

 

[cherritaker]

Ok i'm trying to do that right now but as soon as i install the plugin or start it nothing works. It wont allow me to do a diagnostic download i did capture another screenshot gonna try some more in maintenance mode. 

[Squid]

Something else is wrong.

 

From the local console (or SSH), can you do this then

tail -f /var/log/syslog > /boot/syslog.txt

and then install FCP and when it crashes the syslog will be saved on the flash drive

[Squid]

Got your PM (yes they're safe to post publicly).  Your problem is identical to this one:

 

 

If you want, tomorrow I can bang together a special version of FCP for you to manually install to see exactly where the issue is.

[cherritaker]

Thanks squid that sounds great. 

[Squid]

6 hours ago, cherritaker said:

Thanks squid that sounds great. 

Try this.  From a command prompt,

 

cd /tmp
wget https://github.com/Squidly271/fix.common.problems/raw/master/archive/fix.common.problems-2018.01.20-x86_64-1.txz
installpkg fix.common.problems-2018.01.20-x86_64-1.txz

Then, open up the log window on unRaid's UI and go to Settings - Fix Common Problems

 

If the log Window doesn't show Fix Common Problems and start scrolling, then hit ReScan

 

Post the output when it crashes

[cherritaker]

Ok just got around to it . 

Quote

ErrorWarningSystemArrayLogin

Jan 19 21:45:12 Tower root: Starting virtlockd...
Jan 19 21:45:12 Tower avahi-daemon[3788]: Joining mDNS multicast group on interface veth5d47390.IPv6 with address fe80::98d7:efff:fe72:c02e.
Jan 19 21:45:12 Tower avahi-daemon[3788]: New relevant interface veth5d47390.IPv6 for mDNS.
Jan 19 21:45:12 Tower avahi-daemon[3788]: Registering new address record for fe80::98d7:efff:fe72:c02e on veth5d47390.*.
Jan 19 21:45:12 Tower root: Starting virtlogd...
Jan 19 21:45:12 Tower root: Starting libvirtd...
Jan 19 21:45:12 Tower kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 19 21:45:12 Tower kernel: mdcmd (70): check correct
Jan 19 21:45:12 Tower kernel: md: recovery thread: check P Q ...
Jan 19 21:45:12 Tower kernel: md: using 1536k window, over a total of 5860522532 blocks.
Jan 19 21:45:12 Tower kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 19 21:45:12 Tower kernel: Ebtables v2.0 registered
Jan 19 21:45:13 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state
Jan 19 21:45:13 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Jan 19 21:45:13 Tower kernel: device virbr0-nic entered promiscuous mode
Jan 19 21:45:13 Tower avahi-daemon[3788]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Jan 19 21:45:13 Tower avahi-daemon[3788]: New relevant interface virbr0.IPv4 for mDNS.
Jan 19 21:45:13 Tower avahi-daemon[3788]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Jan 19 21:45:13 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state
Jan 19 21:45:13 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state
Jan 19 21:45:13 Tower dnsmasq[8845]: started, version 2.78 cachesize 150
Jan 19 21:45:13 Tower dnsmasq[8845]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify
Jan 19 21:45:13 Tower dnsmasq-dhcp[8845]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Jan 19 21:45:13 Tower dnsmasq-dhcp[8845]: DHCP, sockets bound exclusively to interface virbr0
Jan 19 21:45:13 Tower dnsmasq[8845]: reading /etc/resolv.conf
Jan 19 21:45:13 Tower dnsmasq[8845]: using nameserver 192.168.1.1#53
Jan 19 21:45:13 Tower dnsmasq[8845]: read /etc/hosts - 2 addresses
Jan 19 21:45:13 Tower dnsmasq[8845]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 19 21:45:13 Tower dnsmasq-dhcp[8845]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 19 21:45:13 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Jan 19 21:46:01 Tower sSMTP[11632]: Creating SSL connection to host
Jan 19 21:46:01 Tower sSMTP[11632]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Jan 19 21:46:04 Tower sSMTP[11632]: Sent mail for [email protected] (221 2.0.0 closing connection q65sm21535051pfj.137 - gsmtp) uid=0 username=root outbytes=719
Jan 20 03:40:01 Tower root: mover: started
Jan 20 03:40:01 Tower root: mover: finished
Jan 20 20:29:10 Tower login[35308]: ROOT LOGIN on '/dev/pts/1'
Jan 20 20:38:29 Tower kernel: md: sync done. time=82396sec
Jan 20 20:38:29 Tower kernel: md: recovery thread: completion status: 0
Jan 20 20:39:02 Tower sSMTP[36789]: Creating SSL connection to host
Jan 20 20:39:02 Tower sSMTP[36789]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Jan 20 20:39:05 Tower sSMTP[36789]: Sent mail for [email protected] (221 2.0.0 closing connection o1sm25605527pfa.101 - gsmtp) uid=0 username=root outbytes=753
Jan 20 20:39:13 Tower root: Fix Common Problems Version plugin: xml parse error
Jan 20 20:39:15 Tower root: Performing HPApresent
Jan 20 20:39:15 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Jan 20 20:39:15 Tower kernel: IP: isci_task_abort_task+0x18/0x334 [isci]
Jan 20 20:39:15 Tower kernel: PGD 0 P4D 0 
Jan 20 20:39:15 Tower kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Jan 20 20:39:15 Tower kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod bonding igb ptp pps_core i2c_algo_bit ipmi_ssif sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd isci libsas ahci libahci intel_cstate intel_uncore intel_rapl_perf scsi_transport_sas i2c_i801 i2c_core mxm_wmi wmi ipmi_si button [last unloaded: pps_core]
Jan 20 20:39:15 Tower kernel: CPU: 0 PID: 34152 Comm: kworker/u80:0 Not tainted 4.14.13-unRAID #1
Jan 20 20:39:15 Tower kernel: Hardware name: Supermicro X9DR3-F/X9DR3-F, BIOS 3.2a 07/09/2015
Jan 20 20:39:15 Tower kernel: Workqueue: scsi_tmf_1 scmd_eh_abort_handler
Jan 20 20:39:15 Tower kernel: task: ffff881ec0ce0e00 task.stack: ffffc90027980000
Jan 20 20:39:15 Tower kernel: RIP: 0010:isci_task_abort_task+0x18/0x334 [isci]
Jan 20 20:39:15 Tower kernel: RSP: 0018:ffffc90027983ce8 EFLAGS: 00010296
Jan 20 20:39:15 Tower kernel: RAX: ffffffffa00a5cbb RBX: ffff880902c2e9a8 RCX: 0000000000000000
Jan 20 20:39:15 Tower kernel: RDX: ffff88103f418420 RSI: 0000000000000a00 RDI: 0000000000000000
Jan 20 20:39:15 Tower kernel: RBP: 0000000000000000 R08: 00000000000000f1 R09: 0000000000000000
Jan 20 20:39:15 Tower kernel: R10: 0000000000000003 R11: ffff881ec0ce0ec0 R12: ffff88102a9d9000
Jan 20 20:39:15 Tower kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000000
Jan 20 20:39:15 Tower kernel: FS: 0000000000000000(0000) GS:ffff88103f800000(0000) knlGS:0000000000000000
Jan 20 20:39:15 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 20 20:39:15 Tower kernel: CR2: 0000000000000000 CR3: 0000000001c0a001 CR4: 00000000001606f0
Jan 20 20:39:15 Tower kernel: Call Trace:
Jan 20 20:39:15 Tower kernel: ? __blk_run_queue+0x3e/0x46
Jan 20 20:39:15 Tower kernel: ? blk_finish_plug+0x20/0x2d
Jan 20 20:39:15 Tower kernel: ? run_scheduled_bios+0x378/0x3a1
Jan 20 20:39:15 Tower kernel: ? get_nohz_timer_target+0x18/0x8b
Jan 20 20:39:15 Tower kernel: ? cpuacct_charge+0x2c/0x6b
Jan 20 20:39:15 Tower kernel: ? dequeue_entity+0x49a/0x4bf
Jan 20 20:39:15 Tower kernel: ? pick_next_task_fair+0x227/0x3d9
Jan 20 20:39:15 Tower kernel: ? put_prev_entity+0x21/0x2d9
Jan 20 20:39:15 Tower kernel: sas_eh_abort_handler+0x2a/0x3c [libsas]
Jan 20 20:39:15 Tower kernel: scmd_eh_abort_handler+0x35/0x8f
Jan 20 20:39:15 Tower kernel: process_one_work+0x146/0x239
Jan 20 20:39:15 Tower kernel: ? rescuer_thread+0x258/0x258
Jan 20 20:39:15 Tower kernel: worker_thread+0x1c3/0x292
Jan 20 20:39:15 Tower kernel: kthread+0x10f/0x117
Jan 20 20:39:15 Tower kernel: ? kthread_create_on_node+0x3a/0x3a
Jan 20 20:39:15 Tower kernel: ret_from_fork+0x1f/0x30
Jan 20 20:39:15 Tower kernel: Code: e8 5d 41 5c 41 5d c3 b8 05 00 00 00 c3 b8 05 00 00 00 c3 41 57 41 56 41 55 41 54 55 48 89 fd 53 4c 8d 75 08 48 81 ec 68 01 00 00 <48> 8b 07 c7 44 24 10 00 00 00 00 c7 44 24 18 00 00 00 00 48 8b 
Jan 20 20:39:15 Tower kernel: RIP: isci_task_abort_task+0x18/0x334 [isci] RSP: ffffc90027983ce8
Jan 20 20:39:15 Tower kernel: CR2: 0000000000000000
Jan 20 20:39:15 Tower kernel: ---[ end trace 4dd18234501c86b0 ]---

Jan 20 20:40:08 Tower root: Fix Common Problems Version plugin: xml parse error
Jan 20 20:40:09 Tower root: Performing HPApresent
Jan 20 20:40:23 Tower root: Fix Common Problems Version plugin: xml parse error
Jan 20 20:40:24 Tower root: Performing HPApresent
Jan 20 20:42:08 Tower nginx: 2018/01/20 20:42:08 [error] 3841#3841: *250918 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.24, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/Settings/FixProblems"
Jan 20 20:42:23 Tower nginx: 2018/01/20 20:42:23 [error] 3841#3841: *250916 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.24, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/Settings/FixProblems"

 

Edited January 21, 2018 by cherritaker

[Squid]

8 hours ago, cherritaker said:

Ok just got around to it .

ok.  I see what test its failing on.  Can I see your diagnostics.  

[cherritaker]

Here they're.

tower-diagnostics-20180121-0815.zip

syslog.txt

[Squid]

ok.  Can you do these commands.  It may crash your system though, but its just doing the same test as where its crashing in the plugin.

 

/sbin/hdparm -N /dev/sdc
/sbin/hdparm -N /dev/sdb

 

[cherritaker]

After doing the commands i get this. 

root@Tower:~# /sbin/hdparm -N /dev/sdc

/dev/sdc:
 max sectors   = 1953525168/1953525168, HPA is disabled
root@Tower:~# /sbin/hdparm -N /dev/sdb

/dev/sdb:
 max sectors   = 1953525168/1953525168, HPA is disabled

 

[Squid]

huh.  

 

Save the attached file to the flash drive and then do

/boot/test.php

  Also grab another syslog after running

 

test.php

[cherritaker]

After running the command the system crashes so i can't do a diagnostic so i had the log window open and copied it here it is.

Quote

Jan 21 11:03:14 Tower kernel: docker0: port 6(veth43d329e) entered forwarding state
Jan 21 11:03:15 Tower root: binhex-delugevpn: started succesfully!
Jan 21 11:03:15 Tower emhttpd: shcmd (210): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1
Jan 21 11:03:15 Tower kernel: BTRFS: device fsid ede5162b-39cd-4c5d-9f9e-e6b908692fb7 devid 1 transid 180 /dev/loop3
Jan 21 11:03:15 Tower kernel: BTRFS info (device loop3): disk space caching is enabled
Jan 21 11:03:15 Tower kernel: BTRFS info (device loop3): has skinny extents
Jan 21 11:03:15 Tower root: Resize '/etc/libvirt' of 'max'
Jan 21 11:03:15 Tower kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824
Jan 21 11:03:15 Tower emhttpd: shcmd (218): /etc/rc.d/rc.libvirt start
Jan 21 11:03:15 Tower root: Starting virtlockd...
Jan 21 11:03:15 Tower root: Starting virtlogd...
Jan 21 11:03:15 Tower root: Starting libvirtd...
Jan 21 11:03:15 Tower kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 21 11:03:15 Tower emhttpd: nothing to sync
Jan 21 11:03:16 Tower kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 21 11:03:16 Tower kernel: Ebtables v2.0 registered
Jan 21 11:03:16 Tower avahi-daemon[4043]: Joining mDNS multicast group on interface veth43d329e.IPv6 with address fe80::5097:4ff:fe87:dee6.
Jan 21 11:03:16 Tower avahi-daemon[4043]: New relevant interface veth43d329e.IPv6 for mDNS.
Jan 21 11:03:16 Tower avahi-daemon[4043]: Registering new address record for fe80::5097:4ff:fe87:dee6 on veth43d329e.*.
Jan 21 11:03:16 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state
Jan 21 11:03:16 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Jan 21 11:03:16 Tower kernel: device virbr0-nic entered promiscuous mode
Jan 21 11:03:17 Tower avahi-daemon[4043]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Jan 21 11:03:17 Tower avahi-daemon[4043]: New relevant interface virbr0.IPv4 for mDNS.
Jan 21 11:03:17 Tower avahi-daemon[4043]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Jan 21 11:03:17 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state
Jan 21 11:03:17 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state
Jan 21 11:03:17 Tower dnsmasq[11210]: started, version 2.78 cachesize 150
Jan 21 11:03:17 Tower dnsmasq[11210]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify
Jan 21 11:03:17 Tower dnsmasq-dhcp[11210]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Jan 21 11:03:17 Tower dnsmasq-dhcp[11210]: DHCP, sockets bound exclusively to interface virbr0
Jan 21 11:03:17 Tower dnsmasq[11210]: reading /etc/resolv.conf
Jan 21 11:03:17 Tower dnsmasq[11210]: using nameserver 192.168.1.1#53
Jan 21 11:03:17 Tower dnsmasq[11210]: read /etc/hosts - 2 addresses
Jan 21 11:03:17 Tower dnsmasq[11210]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 21 11:03:17 Tower dnsmasq-dhcp[11210]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 21 11:03:17 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Jan 21 11:04:47 Tower login[17042]: ROOT LOGIN on '/dev/pts/1'
Jan 21 11:05:28 Tower login[17861]: ROOT LOGIN on '/dev/pts/0'
Jan 21 11:05:42 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Jan 21 11:05:42 Tower kernel: IP: isci_task_abort_task+0x18/0x334 [isci]
Jan 21 11:05:42 Tower kernel: PGD 0 P4D 0 
Jan 21 11:05:42 Tower kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Jan 21 11:05:42 Tower kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod bonding igb ptp pps_core i2c_algo_bit ipmi_ssif sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd isci libsas intel_cstate intel_uncore ahci intel_rapl_perf libahci scsi_transport_sas i2c_i801 mxm_wmi i2c_core wmi ipmi_si button [last unloaded: pps_core]
Jan 21 11:05:42 Tower kernel: CPU: 0 PID: 1559 Comm: kworker/u80:1 Not tainted 4.14.13-unRAID #1
Jan 21 11:05:42 Tower kernel: Hardware name: Supermicro X9DR3-F/X9DR3-F, BIOS 3.2a 07/09/2015
Jan 21 11:05:42 Tower kernel: Workqueue: scsi_tmf_7 scmd_eh_abort_handler
Jan 21 11:05:42 Tower kernel: task: ffff88103b087000 task.stack: ffffc90007ad0000
Jan 21 11:05:42 Tower kernel: RIP: 0010:isci_task_abort_task+0x18/0x334 [isci]
Jan 21 11:05:42 Tower kernel: RSP: 0018:ffffc90007ad3ce8 EFLAGS: 00010296
Jan 21 11:05:42 Tower kernel: RAX: ffffffffa0067cbb RBX: ffff8810383afda8 RCX: 0000000000000000
Jan 21 11:05:42 Tower kernel: RDX: ffff88103f418420 RSI: 0000000000000a00 RDI: 0000000000000000
Jan 21 11:05:42 Tower kernel: RBP: 0000000000000000 R08: 000000000000011a R09: 0000000000000000
Jan 21 11:05:42 Tower kernel: R10: 0000000000000003 R11: ffff88103b0870c0 R12: ffff88102a1f3800
Jan 21 11:05:42 Tower kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000000
Jan 21 11:05:42 Tower kernel: FS: 0000000000000000(0000) GS:ffff88103f800000(0000) knlGS:0000000000000000
Jan 21 11:05:42 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 21 11:05:42 Tower kernel: CR2: 0000000000000000 CR3: 0000000001c0a005 CR4: 00000000001606f0
Jan 21 11:05:42 Tower kernel: Call Trace:
Jan 21 11:05:42 Tower kernel: ? native_sched_clock+0x54/0x7a
Jan 21 11:05:42 Tower kernel: ? sched_clock+0x5/0x8
Jan 21 11:05:42 Tower kernel: ? sched_clock+0x5/0x8
Jan 21 11:05:42 Tower kernel: ? sched_clock_cpu+0x10/0xb7
Jan 21 11:05:42 Tower kernel: ? update_rq_clock+0x19/0x86
Jan 21 11:05:42 Tower kernel: ? get_nohz_timer_target+0x18/0x8b
Jan 21 11:05:42 Tower kernel: ? cpuacct_charge+0x2c/0x6b
Jan 21 11:05:42 Tower kernel: ? dequeue_entity+0x49a/0x4bf
Jan 21 11:05:42 Tower kernel: ? pick_next_task_fair+0x227/0x3d9
Jan 21 11:05:42 Tower kernel: ? put_prev_entity+0x21/0x2d9
Jan 21 11:05:42 Tower kernel: sas_eh_abort_handler+0x2a/0x3c [libsas]
Jan 21 11:05:42 Tower kernel: scmd_eh_abort_handler+0x35/0x8f
Jan 21 11:05:42 Tower kernel: process_one_work+0x146/0x239
Jan 21 11:05:42 Tower kernel: ? rescuer_thread+0x258/0x258
Jan 21 11:05:42 Tower kernel: worker_thread+0x1c3/0x292
Jan 21 11:05:42 Tower kernel: kthread+0x10f/0x117
Jan 21 11:05:42 Tower kernel: ? kthread_create_on_node+0x3a/0x3a
Jan 21 11:05:42 Tower kernel: ret_from_fork+0x1f/0x30
Jan 21 11:05:42 Tower kernel: Code: e8 5d 41 5c 41 5d c3 b8 05 00 00 00 c3 b8 05 00 00 00 c3 41 57 41 56 41 55 41 54 55 48 89 fd 53 4c 8d 75 08 48 81 ec 68 01 00 00 <48> 8b 07 c7 44 24 10 00 00 00 00 c7 44 24 18 00 00 00 00 48 8b 
Jan 21 11:05:42 Tower kernel: RIP: isci_task_abort_task+0x18/0x334 [isci] RSP: ffffc90007ad3ce8
Jan 21 11:05:42 Tower kernel: CR2: 0000000000000000
Jan 21 11:05:42 Tower kernel: ---[ end trace a66947bacdc42531 ]---

 

[Squid]

1 hour ago, cherritaker said:

After running the command the system crashes so i can't do a diagnostic so i had the log window open and copied it here it is.

Quote

But what was the last thing it showed before it crashed?  Or did it show nothing?

[cherritaker]

Quote

Jan 21 11:08:32 Tower nginx: 2018/01/21 11:08:32 [error] 4096#4096: *885 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.24, server: , request: "POST /webGui/include/Download.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/Tools/Diagnostics"
Jan 21 11:12:40 Tower shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/appdata/plexpass/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-362c5db2e09418a244b673d47c178dec-925acc3c-ae37-4f38-a96a-4a0aa9e68a62
Jan 21 11:12:40 Tower shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/appdata/plexpass/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-362c5db2e09418a244b673d47c178dec-925acc3c-ae37-4f38-a96a-4a0aa9e68a62
Jan 21 11:12:40 Tower shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/appdata/plexpass/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-362c5db2e09418a244b673d47c178dec-925acc3c-ae37-4f38-a96a-4a0aa9e68a62
Jan 21 11:13:11 Tower shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/appdata/plexpass/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-362c5db2e09418a244b673d47c178dec-c4a47f8d-a421-414c-a030-1737810ae094
Jan 21 11:13:11 Tower shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/appdata/plexpass/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-362c5db2e09418a244b673d47c178dec-925acc3c-ae37-4f38-a96a-4a0aa9e68a62
Jan 21 11:13:11 Tower shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/appdata/plexpass/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-362c5db2e09418a244b673d47c178dec-c4a47f8d-a421-414c-a030-1737810ae094
Jan 21 11:13:11 Tower shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/appdata/plexpass/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-362c5db2e09418a244b673d47c178dec-925acc3c-ae37-4f38-a96a-4a0aa9e68a62

Done

this is the only thing i saw it do.

Linux 4.14.13-unRAID.
Last login: Sun Jan 21 11:05:28 -0800 2018 on /dev/pts/0.
root@Tower:~# /boot/test.php
parity  sdg
disk1  sdn
disk2  sdq
disk3  sdf

 

Edited January 21, 2018 by cherritaker

[Squid]

one last thing then

/sbin/hdparm -N /dev/sdf

[cherritaker]

Should i be restarting the server every time i do a command?

Quote

Linux 4.14.13-unRAID.
Last login: Sun Jan 21 12:42:33 -0800 2018 on /dev/pts/2.
root@Tower:~# /sbin/hdparm -N /dev/sdf

/dev/sdf:

 

[Squid]

Shouldn't matter.

 

Here's the thing.  That drive particular drive (disk 3) for whatever reason crashes the hdparm command.  But disk 2 which is an identical drive works.  No real idea here.

 

What I've done though is water down the test to only look at the Parity disks.  They're the only ones that really matter on the test anyways.  The test was at least getting through your 1st parity.  If it still crashes (when it hits parity 2), my advice is going to be to remove FCP.