Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About DaemonHunter

  • Rank

Recent Profile Visitors

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

  1. In my case, it was the Cool N' Quiet setting that needed to be disabled. Once that was disabled everything started working fine.
  2. @tjb_altf4 Both containers used are linuxserver/sonarr. I have changed the port number inside the container using the web interface as you suggested, restarted the container and cannot access the web interface from port 80.
  3. The issue that I have found is that regardless of what port you set as the host port, it will change itself. This sounds a little confusing so I brought some screenshots. Picture_1: This photo is of a docker that is running locally on my Debian machine. The port passes through from 80 to 8989 properly. This photo shows that. Picture_2: This photo shows the config that is being used to create the docker in unRAID. The port configuration is setup correctly. Picture_3: This photo shows the config that was pushed did not work as it was setup. Picture_4: This photo shows it working on the default port, but not the one I setup. Picture_5: This photo shows that the config it was set to use did not work. I have this issue with all my dockers, but if I run them locally I have no issue. All symptoms point to there being something in unRAID that is not right. If anyone has a fix please let me know. Thanks, DaemonHunter
  4. I'm not sure if this is what did it, but I disabled the CPU governor in my BIOS and all my issues went away.
  5. Hello everyone. I am looking at implementing a setup of unRAID for a local business near me. I have used the system for about 2 years now at home and there are still a few things that I am not sure about. 1. Hypothetically, if you have a 1TB cache drive, and 8TB of data array storage available.... and are uploading a 2TB file to a cached share, how does unRAID handle the lack of space on the cache? Does it skip the cache and write to the array? Does it write to the cache until full then swap over to the array? Etc. 2. Suppose I want to run an OS router solution such as pfSense or vyOS as a virtual machine on the unRAID platform. Will unRAID be able to handle this or is it out of its league? Thanks for any support or answers I can receive. -DaemonHunter
  6. UPDATE: Have run a memtest with no issues. Formatted and reinstalled the unraid flash drive. The issue seems to be the Plex Transcoder? I have posted files of what I am seeing in the syslog as well as a recent diagnostics. steelmountain-diagnostics-20190212-0031.zip syslog_1.txt syslog_2.txt syslog_3.txt syslog_4.txt syslog_5.txt syslog_6.txt syslog_7.txt syslog_8.txt syslog_9.txt
  7. Could a docker container be causing it? The only recent change I have made is adding the H265ize docker container but have not had a chance to set it up. I noticed that it was running and using 80% of the CPU?? Before the memtest I think Im gonna delete this container and see if this issue persists. Is there a way to make sure everything that the container installed is removed?
  8. I am using linuxserver/plex. I will be running the memtest over the next 24 hours.
  9. I have added the logs from the last 3 lockups.
  10. Sorry I guess I should read my response before sending it. Yes I have a monitor attached as well. I am tailing the log files currently and will let you know the outcome when it locks up. @Hoopster I have not noticed any call traces in previous syslogs. All dockers are assigned via static IP. Thanks, DaemonHunter
  11. Yes I have a keyboard/mouse attached. both are unresponsive as if system locked up. I have not done a memtest yet. Would you recommend that for start? Thanks, DaemonHunter steelmountain-diagnostics-20190114-1416.zip
  12. Hello, I hope someone here has an idea of whats going on because I am all out! Anywhere between 6 hours to 48 hours, the server will become unresponsive. By unresponsive, I mean: 1. Will not respond to pings 2. Shares are not accessible 3. Docker containers are not available 4. The host itself is unresponsive (cannot even put in a username locally to take a look) The only resolution I have found is to perform a cold reboot to the server. If there is any diagnostic information that could help, please let me know and I will attach it. Thanks, DaemonHunter
  13. Yes I acknowledged the SMART warning on those drives. What I am not understanding is why the drives are going bad? Every drive in the system should be less that 1 1/2 years old, with about half of them being less than 6 months old.