beaverly72

Members
  • Posts

    40
  • Joined

  • Last visited

Everything posted by beaverly72

  1. This is going to be a terrible post because I do not have a lot of information. I upgraded to 6.8.0-rc8 today from 6.8.0-rc7. I used the Unraid Nvidia plugin, but did not think that was the issue. After the upgrade my pfSense VM would halt while booting and never came up. I used the same Unraid Nvidia plugin to rollback to 6.8.0-rc7 and the VM booted without issue. If there are some logs that I can provide I will, but I am not sure where they would be, or even exist at this point since I rolled back and rebooted my server. I didn't see this issue reported so far from a quick search and wanted to see if anyone else was having this issue.
  2. So far so good. Thanks for all the hard work! Will be making a donation
  3. Ahhh....I tried searching first but apparently I gave up too fast. Thanks!
  4. I just updated from 6.7.2 to 6.8 rc5. The status bar at the bottom of the page has stated the array is down and the services are still starting since the reboot for the upgrade. Not sure exactly what logs to attach that would be helpful. Apparently whatever services it is, it did not stop the array from starting because the array is for sure started. Any help is appreciated.
  5. Rolled back to 2.3.9-1-05. Now working again. looks like 2.3.9-1-06 is not working
  6. Updated to latest version today and am receiving the following error. Container won’t start. OpenVPN config file (ovpn extension) is located at /config/openvpn/ipvanish-US-Atlanta-atl-a72.ovpn /usr/local/bin/init.sh: line 145: /usr/local/bin/dos2unix.sh: No such file or directory
  7. When attempting to pass my GPU through to my VMs I get the following errors. I have also attached the entire syslog file. Jun 29 22:57:46 LINK-SRV-001 kernel: pcieport 0000:00:03.1: AER: Uncorrected (Non-Fatal) error received: 0000:00:00.0Jun 29 22:57:46 LINK-SRV-001 kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Receiver ID)Jun 29 22:57:46 LINK-SRV-001 kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00200000/04400000 link-srv-001-syslog-20190630-1154.zip
  8. Just updated to 6.7.2. I don’t think that is the issue. Also was not able to start my KVM service until stopping and starting my array after a reboot. I also had to change my Unraid server IP today. Now seeing this error in the Syslog... The syslog file should also be attached. Jun 29 22:41:02 LINK-SRV-001 nginx: 2019/06/29 22:41:02 [error] 8430#8430: *26980 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "127.0.0.1" link-srv-001-syslog-20190630-0354.zip
  9. Thanks that worked, but very finicky. If I just updated the container it would fail and break. This would orphan the container and require me to download sabnzbd again. Only if I inserted that string during install would it work. Unfortunately this would cause me to configure all of my settings again. Not a huge deal, but I am assuming that’s not how it went for everyone.
  10. I hate to ask...can anyone let me know how to rollback. New to this and I don’t see a version key pointing to latest. I would attempt to append to the repo url, but not quite sure what I would use for the version?
  11. Seeing the same here. Thanks everyone...thought i was crazy 2.3.8 [0dd1f64]
  12. Thanks for the help, I am not sure what the issue was. I did perform the memtest which generated no errors. I believe it may have been an unstable version of a docker container, but do not know that for sure. The shutdown has not happened in almost two months now.
  13. I have not performed a memtest yet. I have heard anywhere from 3 to 5 passes by memtest are required to ensure the RAM has no issues. Does this seem accurate?
  14. I am dealing with an issue where my Unraid machine becomes unresponsive. I am a little confused because when I go to the diagnostic and view the logs, they seem to be only from after the server was rebooted. This has only start recently (within the past month) and seems to be every week or so. The last time machine became unresponsive on 1/29/2019 around 18:20. I did take a picture of what was on the screen before i performed a hard shutdown to reboot the machine. I am just not sure why the log files do not seem to include anything prior to the reboot. I am sure it is something I am doing incorrectly, but I am fairly new to Unraid. Any help is appreciated. link-srv-001-diagnostics-20190130-0545.zip