L0rdRaiden

Members
  • Content Count

    388
  • Joined

  • Last visited

Everything posted by L0rdRaiden

  1. It would be nice to have this settings in the network configuration UI. Usually if you do a bond you will want to change the xmit_hash_policy
  2. Could a weekly reboot improve the situation? Usually is stable at least for 2 weeks, but could be a coincidence
  3. Same problem again, MEMTEST 86 from passmark says RAM is OK. RAM Freq now is at 2400Mhz Jun 9 12:01:09 Unraid webGUI: Successful login user root from 192.168.1.30 Jun 9 12:01:16 Unraid emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jun 9 12:01:53 Unraid kernel: veth6af80b0: renamed from eth0 Jun 9 12:01:53 Unraid kernel: eth0: renamed from veth4bba7ca Jun 9 13:02:16 Unraid kernel: BUG: unable to handle kernel paging request at fffff8ef07828908 Jun 9 13:02:16 Unraid kernel: PGD 0 P4D 0 Jun 9 13:02:16 Unraid kernel: Oops: 0000 [#1] S
  4. Memory now is running at 2400Mhz and still getting call trace errors, is there a way to troubleshoot more and find the root cause?
  5. Yes I have read it and I knew it but I'm not overcloking my RAM or my CPU But maybe operating memory at a frequency higher than the infinity fabric of chip may cause problems. https://www.tomshardware.com/reviews/amd-ryzen-5-1600x-cpu-review,5014-2.html But nothing in my setup is being overclocked or over voltage. As I said I have lower it down to 2400 to see how it goes.
  6. The memory runs at stock at 3000Mhz now it was running at 2933Mhz New bios versions (I have the latest) improved the memory compatibility and basically any board with a recent bios can run memories up to 3200Mhz. Anyway to will under clock it to 2400Mhz to see if it improves something. In any case can you identify in the logs something that may indicate that the problem might not be the memory? I have been copy pasting sections of it in google but I can't get any clear conclusion.
  7. My loop2 (docker image) gets corrupted every month or more frequently, I have as well 1 VM in cache drive but it always affects to loop2. What I always do is to rebuild the docker image but I'm getting "tired". I have already checked my RAM twice, and lower the freq in the BIOS, is not ECC. I need some help understanting this piece of log the call trace and the BTFRS errors, although I use XFS in cache and array. Considering the errors and warnings in the log, and the diagnistic file could someone please help me to troubleshoot this? Thanks in a
  8. I have downgrade to netdata/netdata:v1.21.0 and then I have come back to netdata/netdata and now it works. Maybe something was corrupt.
  9. I have this configuration and it was working until now I get this errors now Access to file is not permitted: /usr/share/netdata/web//index.html The logs repeats itself with other dockers I have. 2020-05-12 14:20:55: cgroup-name.sh: INFO: Running API command: curl --unix-socket /var/run/docker.sock http://localhost/containers/1659bb1d4973cd61bfb530260cf031019d70fdf973d8e2d0b06d4b82ea058e62/json 2020-05-12 14:20:55: cgroup-name.sh: INFO: docker container '1659bb1d4973cd61bfb530260cf031019d70fdf973d8e2d0b06d4b82ea058e62' is named 'Tautulli' 2020
  10. It would be nice to have a feature to notify everytime an error popups in unraid log.
  11. Try upgrading the BIOS and leaving Cstates enabled, it worked for me with a B350 Chipset and a Ryzen 2400G
  12. So, is there any conclusion or roadmap? or all this was for nothing?
  13. I get this error Missing root folder: /opt/radarr I have followed the instructions on the wiki https://github.com/Radarr/Radarr/wiki/Health-checks#missing-root-folder But he folder is empty, there is nothing inside. I am not using that folder in my Docker config either. Any idea on how to fix it?
  14. Why do I get this errors, how can I solve them? [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole WARNING Misconfigured DNS in
  15. But I understand that with this method I can bypass 1 of the 2 nics in the pcie card, and with the syslinux config I can only bypass both at the same time. Right?
  16. I have this right now in my syslinux file If I want to use this new method what do I need to remove from here? just this (vfio-pci.ids=8086:1521) or something else? I'm doing passthrough of a pcie network card with 2 nics. If I do the passthrough using this method (vfio-pci.cfg) all the other options of my syslinux config file still applies? Thanks in advance.
  17. @Squid can we have this or something similar by default in dockerman? It will help with the docker compose setup with many dockers like mailcow Also some kind of agregated template would be nice, to replicate what docker compose does in docker man.
  18. Yes, that must be, I was trying to setup wireguard, it worked but I was never able to see anything else than 192.168.1.200 which is my unraid machine. This one of the settings that had to be enable accoding to the guide. I will try again in a couple of months.
  19. It doesn't help me really, I am not a pro What I can tell you is that if I stop the array they disappear, but if I start it again they are created, but I don't know why yet
  20. Please find attached the diagnostics file. I will try to troubleshoot it tomorrow to see if I can delete them, but I would like to know what added them unraid-diagnostics-20200409-2253.zip
  21. Any clue on this? please I can not delete them.
  22. What are these "shim" gateways that have appeared in my unraid config? I can't find anything google