3 minutes ago, McKentin said:

Anyone else having issue's with there CPU fan going nuts like a dyson? I had no problem with 6.3.5 and since i updated to 6.4.0 last night and when i run a handbrake docker only it goes crazy loud. Running an X99 board.

 

All ok in my case - CPU-Fan works as normal

49 minutes ago, citrius said:

I have the same issue.

I changed the port of Unraid GUI to 4443 and still the same issue. I tried even to turn off ssl but same problem.

This isn't related to 6.4 - LE made some changes that affected the docker which can be fixed

 

 

An other issue with 6.4: The sleep plugin is not working properly.

 

Plugin-Settings:

Execute function: Sleep

Wait for array inactivity: Yes, exclude Cache

 

When i watch a Movie, the Server went to sleep while the disk where the movie is stored on is still running.

Any suggestions?

Edited January 14, 20188 yr by Zonediver

Any love for gpu (ie nvidia/amd) passthrough to docker containers? Would really help considering the increase in availability of 4k media and being able to transcode it in the plex docker (even with my 12k passmark!! )

Sorry if I'm blind and it has been stated already.

One of my servers is not populating Temperatures for SSDs :

INTEL_SSDSA2BW160G3  *

INTEL_SSDSA2BW160G3  *

 

5 hours ago, bonienl said:

 

That is the issue. Before obtaining the plugin information a quick ping test is done to the google DNS server to ensure network connectivity. If this test fails no further reading is done.

 

Reconfigure your pfsense router to allow pings to 8.8.8.8 from local devices.

Thank you. I'll add that rule and test it out.

 

Butr things have gotten worse instead of better. My shares are randomly disapperring now. 4 times in past 16 hours.  They re-appear when I reboot. I think i'm going to roll back to 6.3.

12 hours ago, Squid said:

Patch detailed on the last page of its thread.

 

Should work perfectly, unless you're using it for SMB remote mounts in which case you *may* have to force v1 SMB mounts via its settings

 

I do have a small modification to my go file.  Could this somehow be the culprit? 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
/boot/cache_dirs  -w

echo 'SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="zwave"' > /etc/udev/rules.d/99-usb-serial.rules
udevadm control --reload-rules
udevadm trigger
sleep 5

With my plugins seeming to be within the normal range of plugins used, I'm at a bit of a loss for what the issue could be.

 

If this seems to be good, I'll update again to 6.4 and run in safe mode next with mover logging disabled.

Edited January 14, 20188 yr by Living Legend

21 hours ago, bonienl said:

The problem is your manually created network (homenet), it doesn't allow unRAID to create a custom network since the source is already used.

 

My recommendation is to do the following:

 

1. Temporary change the network type of your pi-hole container to "bridge"

2. Execute the following the remove and rebuild all docker networks

rm /var/lib/docker/network/files/local-kv.db
/etc/rc.d/rc.docker restart

3. You should now have eth0 or br0 as network.

# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
865de5dae5cd        br0                 macvlan             local
980f34d59a52        bridge              bridge              local
0a8621dc505b        host                host                local
46669c29d09e        none                null                local

4. Change the network type of your pi-hole container to br0 (eth0)

5. Assign a fixed IP address to the container.

 

Ps. Rereading your post. When you have a VLAN defined then it is necessary to assign a (fixed) IP address to it. This allows Docker to add it automatically to the list of available networks.

 

This post might help

 

 

Thanks so much this worked perfectly appreciate the quick and detailed response. So far other than 1 of my drives having an unreadable filesystem after upgrading 6.4.0 seems smooth!!

6 minutes ago, Living Legend said:

If this seems to be good, I'll update again to 6.4 and run in safe mode next with mover logging disabled

 

Also delete the line  /boot/cache_dirs -w in your go file. If you want to use cache_dirs, have a look at the Dynamix v6 plugins.

Edited January 14, 20188 yr by bonienl

1 minute ago, bonienl said:

 

Also delete the line  /boot/cache_dirs -w in your go file. If you want to use cache_dirs, have a look at the Dynamix v6 plugins.

 

Okay.  I have done so.  Just downloaded 6.4 again.  I'll reboot and cross my fingers.

I'm now running 6.4 in safe mode?  What's next?  Do I wait a few hours to see if it crashes, or are the reports that I can pull now while it's running in safe mode to better determine what's going on?

Just noticed the bit about VLANs for containers/VMs, i dunno how i missed that in the RCs.  Nice Sunday afternoon project!

 

Good work!

7 hours ago, Koshy said:

Deleting CA Community Applications seems to have stopped it.

Its not just CA that's causing those errors.  So you do seem to have some other problems.  If I was going to take a guess, you have CA open (along with Preclear Disk) open on another system / browser tab from before your reboot to install 6.4

 

 

35 minutes ago, bonienl said:

 

Also delete the line  /boot/cache_dirs -w in your go file. If you want to use cache_dirs, have a look at the Dynamix v6 plugins.

 

unraid-diagnostics-20180114-1050.zip

 

I have updated the go file, booted into safe mode, and am now running on 6.4.

 

Here is the diagnostics file.  So far no issues.  Usually it takes 1-2 hours before a crash.  Is there anything I need to do besides sit and wait for a crash?  Assuming no crash, what's the next step?

8 minutes ago, Living Legend said:

 

unraid-diagnostics-20180114-1050.zip

 

I have updated the go file, booted into safe mode, and am now running on 6.4.

 

Here is the diagnostics file.  So far no issues.  Usually it takes 1-2 hours before a crash.  Is there anything I need to do besides sit and wait for a crash?  Assuming no crash, what's the next step?

You are getting a lot of log entries from what looks like the preclear plugin.
 

Jan 14 10:50:01 unraid crond[2418]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jan 14 10:50:03 unraid nginx: 2018/01/14 10:50:03 [error] 2673#2673: *3890 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:08 unraid nginx: 2018/01/14 10:50:08 [error] 2673#2673: *3502 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:09 unraid nginx: 2018/01/14 10:50:09 [error] 2673#2673: *3502 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:15 unraid nginx: 2018/01/14 10:50:15 [error] 2673#2673: *3502 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:19 unraid nginx: 2018/01/14 10:50:19 [error] 2673#2673: *3890 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:21 unraid nginx: 2018/01/14 10:50:21 [error] 2673#2673: *3890 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"

Remove the preclear plugin.

 

The Dynamix stats plugin cron is also exiting with an error.  Probably best to remove that for the time being.

 

8 minutes ago, dlandon said:

You are getting a lot of log entries from what looks like the preclear plugin.
 

Jan 14 10:50:01 unraid crond[2418]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Jan 14 10:50:03 unraid nginx: 2018/01/14 10:50:03 [error] 2673#2673: *3890 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:08 unraid nginx: 2018/01/14 10:50:08 [error] 2673#2673: *3502 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:09 unraid nginx: 2018/01/14 10:50:09 [error] 2673#2673: *3502 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:15 unraid nginx: 2018/01/14 10:50:15 [error] 2673#2673: *3502 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:19 unraid nginx: 2018/01/14 10:50:19 [error] 2673#2673: *3890 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"
Jan 14 10:50:21 unraid nginx: 2018/01/14 10:50:21 [error] 2673#2673: *3890 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.220, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.3", referrer: "http://192.168.1.3/Plugins"

Remove the preclear plugin.

 

The Dynamix stats plugin cron is also exiting with an error.  Probably best to remove that for the time being.

 

Hmm, maybe I'm confused with safe mode?  How are we getting errors from plugins even though I'm in safe mode and no plugins should be running?

3 minutes ago, Living Legend said:

 

 

Hmm, maybe I'm confused with safe mode?  How are we getting errors from plugins even though I'm in safe mode and no plugins should be running?

I suspect that the preclear plugin is not respecting the safe mode.  Remove it for now.

2 minutes ago, Living Legend said:

How are we getting errors from plugins

You're not misunderstanding safe mode.  No plugins are currently installed on your system.

 

The preclear errors are probably because you still have another browser open to a preclear page or something.

 

The cron error from system stats actually shouldn't be happening as that issue was supposedly fixed along time ago.

Upgraded from 6.35 oip 6.4 using the plugins method with no trouble.   I made sure any other plugin that needed to be updated was done first.  Even the reboot seemed faster.

 

 

edit:  Spoke too soon.  Speedtest no longer works because it keeps saying that it needs python 2 from the NerdPack plugin.  Well I remove & then reinstall NerdPack & it keeps complaining about python 2.  Finally I tired to install python 2 by itself & it tells me that it is already installed.  I did stop/restart my server.

Edited January 14, 20188 yr by lovswr

7 hours ago, johnnie.black said:

 

Try redoing your flashdrive, backup first, redo with v6.4 then restore the config folder from the backup.

Thanks for the suggestion.

 

I wiped my USB thumb drive, installed v6.4 to it, and then copied my old config folder to the thumb drive.  Same result:  Get messages during boot about not being able to mount the UNRAID thumb drive.  System comes up configured as tower, no password, no ethernet connection, etc.  Nothing about these errors appear in the syslog file.

 

I then re-installed v6.3.5 to the thumb.  System comes up normally.

 

Any further suggestions on how to figure out where the incompatibility could be?  Should I start a separate thread?

39 minutes ago, Living Legend said:

 

 

Hmm, maybe I'm confused with safe mode?  How are we getting errors from plugins even though I'm in safe mode and no plugins should be running?

Its a problem with 6.4  Looks like the fix LT put in place (IIRC sometime in the 6.3 series) was reverted, and all .cron entries are being parsed on bootup, and not the ones which are actually installed (as its supposed to work)

 

Reopened my defect report:

 

 

Edited January 14, 20188 yr by Squid

2 minutes ago, marcosv said:

Thanks for the suggestion.

 

I wiped my USB thumb drive, installed v6.4 to it, and then copied my old config folder to the thumb drive.  Same result:  Get messages during boot about not being able to mount the UNRAID thumb drive.  System comes up configured as tower, no password, no ethernet connection, etc.  Nothing about these errors appear in the syslog file.

 

I then re-installed v6.3.5 to the thumb.  System comes up normally.

 

Any further suggestions on how to figure out where the incompatibility could be?  Should I start a separate thread?

Have you tried a USB 2.0 port?

4 minutes ago, dlandon said:

Have you tried a USB 2.0 port?

 

My motherboard,  ASRock EP2C602-4L/D16, does not have USB 3.0 ports.

Hi,

i just updated today to 6.4 and i'm having problems with my windows vm 

 

when i start it it keeps spamming this error

Jan 14 17:35:54 Server kernel: vfio-pci 0000:00:02.0: BAR 2: can't reserve [mem 0xc0000000-0xcfffffff 64bit pref]
to the console, until it fills the log folder.

 

it's a windows 10 vm with igpu passthrough, and the device mentioned in the log seems to be the intel gpu.

does anyone know how that can be solved?

 

thank you

 

 

server-diagnostics-20180114-1740.zip

Edited January 14, 20188 yr by francesco995

4 minutes ago, marcosv said:

 

My motherboard,  ASRock EP2C602-4L/D16, does not have USB 3.0 ports.

Hmmm... Just occurred to me to ask: whereas my motherboard does not have USB 3.0 ports, the thumb drive I'm currently using is a USB 3.0 drive (Ultra Fit 64GB USB 3.0 Flash Drive).  Could there be an incompatibility between 6.4 and using a USB 3.0 boot drive in USB 2.0 ports?