Tuftuf

Members
  • Content count

    127
  • Joined

  • Last visited

  • Days Won

    1

Tuftuf last won the day on June 11

Tuftuf had the most liked content!

Community Reputation

10 Good

About Tuftuf

  • Rank
    Advanced Member
  1. Let me know if you make any progress on this. I'd need to check but I think I get the same sensors as you. 1 Fan and 2 or 3 Temps. I've worked out one of the temps is the external temp sensor, I got a little cable in my motherboard box and when connected I can make the values go up by holding on to it. I may of done that with a second temp value as well (I have two external temp things) but i'm not sure now. either way the values I get today are not very useful.
  2. Have you looked at this ?
  3. I have not seen any comments about loading the vbios for the nivida cards. I forget now if that was limited to passing through the primary or required for secondary cards as well.
  4. I think we have come to the conclusion that cAdvisor is showing the correct information but it does not mean the cores are isolated. Also I expect you can see on the dashboard the cores are not doing anything when your VM is stopped. If they are then something is using it. Something else may be the cause of the increased latency.
  5. I managed to prove myself wrong, so I have to agree its just how it's displayed.
  6. @Squid Are you sure about this? It might just be the wording of your reply that has me confused. You said that what you're seeing is that you're only allowing Unraid to execute on certain cores. and not limiting the particular application by extended parameters. The syscfg isolcpus setting is not allowing Unraid to access certain cores or any application unless allowed by an extended parameter. I would have expected cAdvisor to only show the cores Unraid is allowed on. I'm trying to find a command I used to check this when I first applied isolcpus setting as I've only just started using cAdvisor, and can't say what it used to show. EDIT - Well based on this it does seem to be working. root@Tower:~# cat /sys/devices/system/cpu/isolated 8-15 root@Tower:~# cat /sys/devices/system/cpu/possible 0-15 root@Tower:~# taskset -cp 1 pid 1's current affinity list: 0-7 root@Tower:~# lscpu | grep CPU.s CPU(s): 16 On-line CPU(s) list: 0-15 NUMA node0 CPU(s): 0-15 root@Tower:~# cat /proc/$$/status|tail -6 Cpus_allowed: 00ff Cpus_allowed_list: 0-7
  7. You can turn it off yourself if needed It's listed in this file as pcie_ace_override=downstream root@Tower:/boot/syslinux# pwd /boot/syslinux root@Tower:/boot/syslinux# cat syslinux.cfg default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS (With ACS) menu default kernel /bzimage append pcie_acs_override=downstream isolcpus=8,9,10,11,12,13,14,15 initrd=/bzroot label unRAID OS (without ACS) menu default kernel /bzimage append isolcpus=8,9,10,11,12,13,14,15 initrd=/bzroot
  8. Is that based on an understanding of Unraid or KVM? It's the complete opposite to the RHEL docs for running KVM for example. I still don't agree it's simply memory fragmentation. Unraid generally shows me a % of how much memory is in use, I don't know for certain where this value is taken from but this value generally gives a good indication to how much is in use by VM's for example (also other stuff but they are the ram heavy resource). I've run many VM's on this system already, right now i'm trying to hunt down what is causing the memory % to be so high when I can't find it in processes/memory usage. I'm not saying this is a bug but I wanted to find what was using the memory. I'll reboot and see! EDIT - root@Tower:~# free -m total used free shared buff/cache available Mem: 32128 22494 333 573 9300 8417 Swap: 0 0 0 root@Tower:~# TVHeadend and Java were using a lot less after a reboot. I can control TVH's usage but will need to find out what was using java. nevermind!
  9. But it makes it available when requested and in this case the VM wouldn't start. Something is holding onto it. EDIT - I was running the VM with 8GB ram for the last two nights, nothing has changed but the VM today will only start with 6GB. I understand I have a lot running and things change but I'm just trying to see what is using it. I expect if i reboot I'll have both VM's running with 8GB along with everything else.
  10. I have three VM's running and IMO should have 8GB free. Something is using a lot more than it should and I can't seem to see what. root@Tower:~# free -m total used free shared buff/cache available Mem: 32128 29076 350 871 2701 1526 Swap: 0 0 0 root@Tower:~#
  11. I have more memory in use than I can find allocated to processes, I should have around 23/24GB in use out of 32GB (after starting the VM discussed below) Any suggestions how to track down the missing RAM usage? I've been running a second Windows VM with a GPU and today was unable to start it due to unable to allocate memory. It required 8GB, I have 32GB and my system showed 76% in use. Reducing the VM to 6GB allowed it to start taking me to 95% which grew to 96% a few minutes later. root@Tower:~# ps aux | awk '{print $6/1024 " MB\t\t" $11}' | sort -n [Cut around 40 processes all less than 100mb, most less than 30mb, everything above 100MB is shown below] 109.688 MB /opt/splunk/bin/python 116.438 MB /usr/local/sbin/shfs 124.473 MB node 137.062 MB mono 151.145 MB splunkd 176.051 MB java 193.863 MB bin/mongod 205.191 MB /usr/lib/jvm/java-7-openjdk-amd64/bin/java 271.27 MB mono 321.172 MB /usr/bin/java 394.312 MB mono 1587.43 MB java 4113.69 MB /usr/bin/tvheadend 4332.82 MB /usr/bin/qemu-system-x86_64 6226.94 MB /usr/bin/qemu-system-x86_64 8331.22 MB /usr/bin/qemu-system-x86_64
  12. The issue you likely had prior to RC7a was with C-State in the bios, it causes the system to crash when idle. Disabling it fixed the issue but since RC7a this isthe ssue no long occurs. Regarding sensors, some people have been able to force the detection but for myself I still don't see temps within unraid.
  13. On the unraid system, can you bring up terminal and try ping 10.0.0.1 >-- If this does not work then you won't be able to access the internet. ping 8.8.8.8 >-- If this works then you have internet access. ping google.com >-- If this does NOT work but ping 8.8.8.8 does work, then you have a problem with DNS. "Under Main tab, I cannot start the array..." Cannot contact key-server"." This would imply that test 2 and 3 will fail as the error messaging is stating it cannot reach out to Lime Tech to validate your trial. You could try connecting your mac directly to the Unraid server and manually set an IP of 10.0.0.50 for example and then try accessing 10.0.0.131. FYI (ping google.com or ping 10.0.0.1) will not work when your cable is directly attached. Does your router give out IP's using DHCP? What happens if you tell Unraid to automatically get an IP address?
  14. I've not used this docker.. BUT... 1. There will be a docker support thread, you can find the link to it from the docker or from the CA apps where you installed the docker. Or check out the docker section on the forum and you should find the threard. 2. Did you put the Username and Password into the docker config? I thought for PIA and these dockers you place the username/password within the docker template prior to clicking start.
  15. Did you ever find out why the traffic was blocked? Bypassing one IP is easy enough..
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.