Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About PanteraGSTK

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, that should be all you have to do. It worked for me moving from a much older docker to this one.
  2. I had that problem until I changed the Controller Host Name to its IP address.
  3. That's what I had been doing and it was working. Now it sort of isn't. When I create the .json I actually save it on the USG then pull it according to this. https://larskleeblatt.net/?p=36 It was working just fine. Thought I'd done something wrong in the syntax, but that wasn't it. It really seems like it's ignoring the file.
  4. I seem to be having the same issue. Settings are not being honored. When I SSH back into the USG, the firewall is still enabled.
  5. Docker has 21gb used. At one point it went over 30gb, but I've removed some dockers since then and it's been pretty stable at 21gb.
  6. Those warnings are pretty old. Most are just using something other than the default port. Haven't caused any issues at all for quite some time. I will look at resolving them. EDIT: Correction. I didn't notice they were template errors. I've corrected those. I have syslog enabled, but it looks like it was set to a "custom folder" which it shouldn't have been. I've corrected that.
  7. Upgraded the server to 6.8 and no issues other than two random reboots. Diagnostics attached. unraid-diagnostics-20191226-0918.zip
  8. Same here. Been using Sophos UTM for about 5 years or so. Fantastic product and pretty amazing what you get for the free license. It does have a learning curve though. I've had it running on an i3 with 8gb of ram and it hardly uses any resources with my config. I also run a pi-hole along side it and the combo is fantastic.
  9. Marking this solved...for the third time. I'm pretty confident this time that CPU0 is to blame. The memory all test fine, but the controller issue I got when I first got the CPU/Mobo/RAM combo makes it pretty obvious that is the case. It is possible that Socket 0 is the culprit, but I'll find that out when I move CPU1 to socket 0. I'll also moved the confirmed working RAM. If it all checks out I may grab another xeon 2670 off ebay and hope for the best. I was able to get through a parity check and multiple drives using the file integrity plugin. That plugin was an easy test because when I tried to use it in the past a reboot was pretty much always triggered on my 4TB drives. Another test that passed is downloading large files via usenet while also remuxing a file using makemkv. That's quite a lot of operations at once especially considering my kids were watching movies/tv via plex all at the same time. No reboot. If that didn't make it reboot, nothing will. Hopefully. Thanks for the help.
  10. While removing two sticks of ram seems to have helped, having that ram in netted the same behavior. Sometimes it would be fine, no reboots, sometimes the reboots would happen quickly. Removing CPU0 and associated RAM allowed an additional parity check to complete. No issues. I'll continue to test, but with the fact that I got memory controller errors with CPU0 when I first installed it, but they stopped when I moved the ram around the board points to CPU0 being the culprit. My PSU is a Corsair RMX850 and it's less than 5 years old. I tend to lean toward PSU in these situations too, but with all the other factors I'm confident that CPU0 is most likely the issue.
  11. Removing the memory may have helped, but it didn't fix it. I got through an entire parity check (with 2 parity drives at 50mbps). However, when I checked this morning it had rebooted again. Now to remove cpu0 and memory.
  12. It does sound like a normal power cycle. That's the strange part. I've not been able to capture anything that points me in any specific direction. When I first got the board and cpus, I had an issue where some memory wasn't recognized. I put them in alternate slots and forgot about it for a few years. I pulled those dimms and am testing again. If it reboots again, I'll pull the associated CPU and remaining dimms and just leave cpu1 and its memory.
  13. Yeah, I have. Many times. It's in a closet, but I'm 6 feet away from the actual server. I'll pull some memory, but it's a dual proc board so I'll have to be careful.
  14. Man, I really thought the new SAS card was going to fix this. I recently removed my SAS2LP card in favor of an LSI HBA, but during a parity check the system rebooted at 85%. I'm not finding anything in logs that tell me where to look. Any ideas on where to start?
  15. 3ware has 4 ports that control 4 drives each on a single card. The 2 LSI cards have 2 ports that control 4 drives each. I've got it down. I've got a breakout cable and a SATA cage with fan. I'll pull one drive at a time until 4 are done. Then I can swap cables between the 3ware card to the LSI. Then repeat until complete.