May 23, 20197 yr @Squid There's a bug at https://github.com/Squidly271/fix.common.problems/blob/77d344ce93955e8efbc9560b1e1f14c9ab3e3e90/source/fix.common.problems/usr/local/emhttp/plugins/fix.common.problems/include/tests.php#L378 Need a period/full stop and a space btwn `questionBegin Investigation Here` Would you like me to submit a PR with a fix?
May 26, 20197 yr Hi- Every hour I get an email from my Unraid box, which I determined was due to an hourly cronjob run: root@Unraid:~# /usr/local/emhttp/plugins/fix.common.problems/scripts/scan.php HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device Any ideas on how to suppress this? Thanks!
May 26, 20197 yr Author 35 minutes ago, dcoulson said: Hi- Every hour I get an email from my Unraid box, which I determined was due to an hourly cronjob run: root@Unraid:~# /usr/local/emhttp/plugins/fix.common.problems/scripts/scan.php HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device Any ideas on how to suppress this? Thanks! Try checking for updates. Does today's change fix this?
May 27, 20197 yr 19 hours ago, Squid said: Try checking for updates. Does today's change fix this? I just updated to 2019.05.26 and still have the same issue. Any way to get debug/verbose logs out of the script to see what specifically is generating it?
May 27, 20197 yr 1 hour ago, Squid said: Show me your diagnostics unraid-diagnostics-20190527-1718.zip
May 28, 20197 yr Author On 5/27/2019 at 1:19 PM, dcoulson said: unraid-diagnostics-20190527-1718.zip 102.95 kB · 1 download Show me the output of these commands: hdparm -W /dev/sd* and hdparm -W /dev/nvme0n1
May 30, 20197 yr 15 hours ago, Squid said: Try today's update So far so good - Updated about 3hrs ago. No more emails. Did we fix something or just suppress the output?
June 24, 20197 yr I'm having an issue on one of my unraid servers where FCP times out, I get this in the error log: Jun 24 07:40:31 bigbird nginx: 2019/06/24 07:40:31 [error] 3771#3771: *8043 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.12.140, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.12.250", referrer: "http://192.168.12.250/Settings/FixProblems" Is there another error log that I can check to see what's happening? Edited June 24, 20197 yr by ThatDude typo
June 24, 20197 yr Author It's on the to do list to rearrange FCP from being subject to unRaid's hard 120 second limit on certain operations. In the meantime, after 2 minutes, it will never close the pop up. Give it another couple minutes, then when you reload the tab, the issue(s) will be listed if any are found.
July 7, 20196 yr I'm trying to fix "write cache disabled on parity". Used the solution listed- https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-755621. I get this- Linux 4.19.56-Unraid. root@Brunnhilde:~# hdparm -W 1 /dev/sdc /dev/sdc: setting drive write-caching to 1 (on) write-caching = 0 (off) root@Brunnhilde:~# Looks like it didn't work. The drive is an 8TB HGST (HGST Ultrastar He8 HUH728080ALE600) sata drive connected to a sata port on my motherboard. Any other ideas for a fix?
July 7, 20196 yr Author 9 minutes ago, wgstarks said: Any other ideas for a fix? Talk to WD or ignore it.
July 18, 20196 yr On 6/24/2019 at 2:20 PM, Squid said: It's on the to do list to rearrange FCP from being subject to unRaid's hard 120 second limit on certain operations. In the meantime, after 2 minutes, it will never close the pop up. Give it another couple minutes, then when you reload the tab, the issue(s) will be listed if any are found. I'm seeing the same problem. When I reload the page the scan starts again, does that mean no problems were found? I've included log and diagnostics files just in case. athena-diagnostics-20190718-1054.zip athena-syslog-20190718-1056.zip
July 25, 20196 yr I have run Extended Test and upon completion it says errors found. Where can I view these errors I assume there is a log?
July 25, 20196 yr 28 minutes ago, Gragorg said: I have run Extended Test and upon completion it says errors found. Where can I view these errors I assume there is a log? Settings>Fix Common Problems If you enable email notifications on your server they should also be listed there.
July 25, 20196 yr 1 hour ago, wgstarks said: Settings>Fix Common Problems If you enable email notifications on your server they should also be listed there. This only shows the regular scan errors. It does seem to show Extended Test results
September 9, 20196 yr September 8th update: "Don't check for docker apps having an update available for them unless running 6.8" So not checking for docker apps updates until 6.8 installed? I must be reading this wrong, lol.
September 9, 20196 yr Author September 8th update: "Don't check for docker apps having an update available for them unless running 6.8" So not checking for docker apps updates until 6.8 installed? I must be reading this wrong, lol.Nope why report an update is available when an update is always available until 6.8 is releasedSent from my NSA monitored device
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.