2 hours ago, SomeRandomSod said:

I'm running 6.6.7 and it seems the syslog feature is not available with your plugin, but also not available in the Settings tab (available as of 6.7).

Could do with an easy way of tailing syslog but can't seem to be able to until I either upgrade to 6.7 or find some other solution  

Yeah, because when I did that I never would have thought that 6.6.7 was ever going to be a thing as 6.7 had already started its testing.

 

Fixed.

Hello,

 

I did something stupid.

 

I was going through my settings and have CA Fix install for quite a while now (fixing little issues here and there) and I clicked on something with out reading it fully first. I clicked on something that read to the effect of fixing an issue with my cache drive and now all of my Tautulli history is missing, my Nextcloud wont work and i'm missing a ton of Plex server movie & TV images.

 

Does anyone have a clue what happened to my cache settings and how i can revert this mistake, or know where the data when so i can try pointing it to this location? I checked the actual cache drives and they are still there and have data on it, but i'm at a loss as to why abruptly with this one click its all F'd up?

 

Thanks,

Tabraxis.

 

 

 

1 hour ago, Tabraxis said:

I clicked on something that read to the effect of fixing an issue with my cache drive

FCP never actually fixes anything, but only either points to the appropriate forum post or the section within the OS for you to fix it.

 

If you're lucky, the diagnostics will show the error that you tried to fix (if the server had run a background scan, and you had FCP set to log the errors).  But, you'd have to post them regardless as there's nothing else that we can help you with without knowing anything about what may or may not be going on.

20 hours ago, Squid said:

FCP never actually fixes anything, but only either points to the appropriate forum post or the section within the OS for you to fix it.

 

If you're lucky, the diagnostics will show the error that you tried to fix (if the server had run a background scan, and you had FCP set to log the errors).  But, you'd have to post them regardless as there's nothing else that we can help you with without knowing anything about what may or may not be going on.

I came back today to find my log file usage at 100% and it filled with the attached two text files. I can provide the full list if its more helpful?  

 

 

example.txt

example2.txt

19 minutes ago, Tabraxis said:

can provide the full list if its more helpful? 

The full diagnostics would be more useful for people here

3 minutes ago, Squid said:

The full diagnostics would be more useful for people here

I just sent you a PM with the diagnostics data. 

1 minute ago, Tabraxis said:

I just sent you a PM with the diagnostics data. 

Please don't  Diagnostics are anonymized, and other persons may have more insight than whomever you choose to PM to.

 

But in this case, appdata share is set to use cache: Yes.  Usually you want it to be use cache:Prefer

 

Sorry, I don't often send diagnostics out, so I tend to be selective on where the go.

 

18 minutes ago, Squid said:

But in this case, appdata share is set to use cache: Yes.  Usually you want it to be use cache:Prefer

 

I've made the change to Prefer, and will be doing a restart next. Is it too much to assume that the cached appdata that my dockers are having issues with will go back to before the FCP mishap? Or is there anything else you can recommend I can do? 

Hi, first post here.  Thanks for all you do, Squid, I've been successfully using your plugins thanks to the SpaceInvader vids since I got my server up and running about 6 months ago.

 

Just got the server back online (I'm running 6.6.7 stable) after having the USB drive die (without a backup, was able to copy the config folder, at least).  It seemed that some of the plugins may have become corrupted in the USB's death, I'm not sure.

 

I noticed my app tab was missing this morning when I went to add an app, and then saw these four plugins were missing due to errors:

 

 

I was able to get Community Applications installed and running again.  I went to re-add FCP, and it confirmed that it successfully installed, but it appears like this on the plugin page:

 

 

Clicking on it leads to a blank page under the settings header.  FCP does not appear on the settings page.

 

From my system log, the first four entries are all red, for errors.  I'm not very good at reading this sort of stuff, but I think it also shows where I tried to remove the FCP plugin around 9:03, and reinstall it around 9:04.

Apr 30 09:00:48 LCARS emhttpd: req (10): cmd=/plugins/dynamix.plugin.manager/scripts/plugin_rm&arg1=/boot/config/plugins-error/community.applications.plg&csrf_token=****************
Apr 30 09:00:48 LCARS emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin_rm /boot/config/plugins-error/community.applications.plg
Apr 30 09:00:55 LCARS emhttpd: req (11): cmd=/plugins/dynamix.plugin.manager/scripts/plugin_rm&arg1=/boot/config/plugins-error/fix.common.problems.plg&csrf_token=****************
Apr 30 09:00:55 LCARS emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin_rm /boot/config/plugins-error/fix.common.problems.plg
Apr 30 09:01:42 LCARS bunker: exported 961 files from /mnt/disk7. Duration: 00:00:00
Apr 30 09:01:42 LCARS bunker: exported 2994 files from /mnt/disk5. Duration: 00:00:00
Apr 30 09:01:43 LCARS bunker: exported 2185 files from /mnt/disk6. Duration: 00:00:01
Apr 30 09:01:43 LCARS bunker: exported 4552 files from /mnt/disk2. Duration: 00:00:01
Apr 30 09:01:43 LCARS bunker: exported 5528 files from /mnt/disk4. Duration: 00:00:01
Apr 30 09:01:45 LCARS bunker: exported 11868 files from /mnt/disk1. Duration: 00:00:03
Apr 30 09:01:45 LCARS bunker: exported 8120 files from /mnt/disk3. Duration: 00:00:03
Apr 30 09:03:31 LCARS emhttpd: req (13): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=remove&arg2=fix.common.problems.plg&csrf_token=****************
Apr 30 09:03:31 LCARS emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove fix.common.problems.plg
Apr 30 09:03:32 LCARS root: plugin: running: anonymous
Apr 30 09:04:17 LCARS emhttpd: req (14): cmd=/plugins/community.applications/scripts/pluginInstall.sh&arg1=install&arg2=https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/plugins/fix.common.problems.plg&csrf_token=****************
Apr 30 09:04:17 LCARS emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.sh install https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/plugins/fix.common.problems.plg
Apr 30 09:04:18 LCARS root: plugin: skipping: /boot/config/plugins/fix.common.problems/fix.common.problems-2019.03.26-x86_64-1.txz already exists
Apr 30 09:04:18 LCARS root: plugin: running: /boot/config/plugins/fix.common.problems/fix.common.problems-2019.03.26-x86_64-1.txz
Apr 30 09:04:18 LCARS root: plugin: running: anonymous

 

Let me know if I can provide anymore information that would help!

Without knowing the exact chain of events, the easiest solution is a simple reboot

Okay, rebooted, and the FCP plugin is showing up same as before with the file-type name instead of the display name.  Clicked remove, this was the feedback:

 

 

Reinstalling the plugin this time I noticed a line about the tar archive being corrupt:

 

 

Relevant part of log file (could the time error about the clock unsynchronized be contributing?  No idea what that's about):

Apr 30 12:01:21 LCARS ntpd[2510]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Apr 30 12:01:23 LCARS emhttpd: req (3): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=remove&arg2=fix.common.problems.plg&csrf_token=****************
Apr 30 12:01:23 LCARS emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove fix.common.problems.plg
Apr 30 12:01:23 LCARS root: plugin: running: anonymous
Apr 30 12:04:10 LCARS emhttpd: req (4): cmd=/plugins/community.applications/scripts/pluginInstall.sh&arg1=install&arg2=https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/plugins/fix.common.problems.plg&csrf_token=****************
Apr 30 12:04:10 LCARS emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.sh install https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/plugins/fix.common.problems.plg
Apr 30 12:04:16 LCARS root: plugin: skipping: /boot/config/plugins/fix.common.problems/fix.common.problems-2019.03.26-x86_64-1.txz already exists
Apr 30 12:04:16 LCARS root: plugin: running: /boot/config/plugins/fix.common.problems/fix.common.problems-2019.03.26-x86_64-1.txz
Apr 30 12:04:16 LCARS root: plugin: running: anonymous

 

Delete the .plg from config/plugins on the flash drive and the .txz from config/plugins/fix.common.problems reboot and reinstall

Sent via telekinesis

4 hours ago, Squid said:

Delete the .plg from config/plugins on the flash drive and the .txz from config/plugins/fix.common.problems reboot and reinstall

That seemed to be the trick, I now have it running the extended test.

 

Thanks again, for everything!

Hi folks. I've been having an issue using the Fix Common Problems plugin. I recently upgraded my server (replaced everything but the data drives), and after doing that i installed this plugin to clean up any issues. I've had a few times where i've been able to successfully run the plugin and it's given me some feedback, but most of the time when it runs, the "Scanning" dialog shows and never goes away. I noticed this in the logs which i'm assuming is the culprit: 

May  4 10:28:04 chunk nginx: 2019/05/04 10:28:04 [error] 9719#9719: *4080148 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.60, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.20", referrer: "http://192.168.0.20/Settings/FixProblems"

Aside from this issue, my server appears to be working great. I'm not really sure how best to troubleshoot this. I've attached diagnostics. Can anyone give me any pointers? Thanks.

chunk-diagnostics-20190504-1044.zip

Wait a couple of minutes, then reload the page.  The result(s) should be there.  Then you should be able to enable "Avoid Disk SpinUps" which should alleviate this to a certain point.

 

Barring that, it's on the todo list to work around unRaid's hard limit of 120 seconds for any particular operation.

Ahhh okay. Thanks very much @Squid. That seems to have worked. 

I'm getting a waring that I have "Marvel Hard Drive Controller Installed" but when I look at the system devices.. I don't see any Marvel listed. The only two "SATA" listings are

 

IOMMU group 17:[8086:8d7c] 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05)

[8086:8d62] 00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05)

 

IOMMU group 26:[8086:8d44] 00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05)

[8086:8d02] 00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05)

 

 

False positive?

7 hours ago, ziggie216 said:

I'm getting a waring that I have "Marvel Hard Drive Controller Installed" but when I look at the system devices.. I don't see any Marvel listed. The only two "SATA" listings are

 

IOMMU group 17:[8086:8d7c] 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05)

[8086:8d62] 00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05)

 

IOMMU group 26:[8086:8d44] 00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05)

[8086:8d02] 00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05)

 

 

False positive?

Post your diagnostics

9 hours ago, Squid said:

Post your diagnostics

 

tower-diagnostics-20190512-2244.zip

Your revo drive has a marvel controller.  Probably no issue with it, but it isn't a false positive

I just updated FCP, and started getting this warning, Diagnostics attached

 

Write Cache is disabled on disk1You may experience slow read/writes to disk1. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and advise

Write Cache is disabled on disk2You may experience slow read/writes to disk2. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and advise

Write Cache is disabled on disk3You may experience slow read/writes to disk3. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and adviseunraid-diagnostics-20190515-1942.zip

1 minute ago, Richjfree1 said:

I just updated FCP, and started getting this warning, Diagnostics attached

 

Write Cache is disabled on disk1You may experience slow read/writes to disk1. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and advise

Write Cache is disabled on disk2You may experience slow read/writes to disk2. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and advise

Write Cache is disabled on disk3You may experience slow read/writes to disk3. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and adviseunraid-diagnostics-20190515-1942.zip

 

Sorry, no dice. see below

 

 

Linux 4.18.20-unRAID.
Last login: Wed May 15 19:51:03 -0500 2019 on /dev/pts/0.
root@UNRAID:~# hdparm -W 1 /dev/sdh

/dev/sdh:
 setting drive write-caching to 1 (on)
 write-caching =  1 (on)
root@UNRAID:~# hdparm -W 1 /dev/sdi

/dev/sdi:
 setting drive write-caching to 1 (on)
 write-caching =  1 (on)
root@UNRAID:~# hdparm -W 1 /dev/sdj

/dev/sdj:
 setting drive write-caching to 1 (on)
 write-caching =  1 (on)
root@UNRAID:~# hdparm -W 1 /dev/sdk

/dev/sdk:
 setting drive write-caching to 1 (on)
 write-caching =  1 (on)
root@UNRAID:~# hdparm -W 1 /dev/sdg

/dev/sdg:
 setting drive write-caching to 1 (on)
 write-caching =  1 (on)
root@UNRAID:~#

?  You just enabled writecaching...

No sir, warning still exists, that is the current status of write caching on those drives