Lothar

Members
  • Posts

    20
  • Joined

  • Last visited

Lothar's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I have those shares set to prefer cahce, should I set them to only? I have my flash drive set as private, do I need to set it to public for container access? Yes I can see the orphaned docker images, thanks fopr the head up. I forgot that you can see these in the advanced settings. For now I am turning off auto update for docker.
  2. I think that I am having simular issue. Every 2 - 3 months I loose a docker container. I have to reinstall making sure to use the same folder in appdata and everything is good again. I just lost 2 yesterday during a parity sync. I have attached my diagnostics file. server-diagnostics-20201102-1808.zip
  3. Thank you, I remember reading about this before but thought it was fixed in an update so I ruled it out. However, reading through that thread It seems that on some hardware there must still be issues. After looking at how internal and external docker IP addresses work I realize that I do not need to assign separate addresses. I have changed them to bridge and will see if that solves it.
  4. I have been having issues with this server off and on since I built it a year ago. I thought I had the problems resolved but about a month ago it became unstable again. The symptoms are random but most of the time the first sign of trouble is that the shares become inaccessible, or are very slow, or become write protected. Restarting the array will resolve these problems. However, sometimes the web UI becomes unresponsive also. I have gone as far as doing a clean install of UnRAID preserving only the shares.cfg and network.cfg. I attached the diagnostics file from when it crashed last. There are many call traces with CPU warnings. Any help would be appreciated. kossnet-server-diagnostics-20190426-1733.zip
  5. I have been unable to get the custom schedule to work for the parity check on both of my servers. I would like it to run the first Monday of every other month at 02:00. This is how I set it - Custom, Monday, First week, 02:00, Jan-Mar-May-Etc. With these settings applied it will run every single Monday. What am I missing?
  6. The new fan script in the latest release 2018.10.14. Is working very well for me. No more having to adjust the settings on my hard drive fans on FANA to get them in control after reboot. Thank you for the great work.
  7. 30 sec. on temp. and 2 min. on HD. The fans were at full RPM for 15-20 min. While I was troubleshooting. I had the same thing happen on my backup server that I updated after. It may have something to do with going from 2 decimal places to one, as the settings were saved from the previous version at 2 decimals but when moved were corrected to one.
  8. You'll have to give me a little more info. I have the exact board and it's working for me. What are your fan settings? What does the ipmifan log say? Clear the log and start and stop the fan control. You can also stop fan control and run ipmifan - - debug and post the ipmifan log. I did get it working, just moved fan control settings around it started functioning normally.
  9. I am having issues with the latest update 20180520. The plugin no longer controls my fans all are running at full RPM. I have tried uninstalling and re-installing. This is on a Supermicro X11SSH-F. EDIT Fixed now. I had to reset all temp and fan settings.
  10. Last night my server was unresponsive, no WebUI or video out. I had to turn it off and restart it. It would not finish booting, I get a BTRFS critical device loop2 corrupt leaf error, that would display four times. Knowing it had to be the cache drive I pulled it and unRAID now boots. I have everything backup up on the cache drive so no worries there. But what would cause this? There were no power outages however, my internet was going up and down last night before this happened. I really do not want to put the SSD cache back in just to have it happen again. The drive is a 1TB M.2 NVME drive. Are there any known issues with these? I have attached the diagnostic file, but it is from after I got the system booted. Update, it turns out that this happened during a parity check, which is odd as I do not have parity checks scheduled right now. server-diagnostics-20180505-1543.zip
  11. Just mover at 02:00 it runs every day. I did swap out the cache SSD a couple of weeks ago to a 1TB drive.
  12. My backup server shows call traces at 04/29 04:30. Any help would be appreciated. Also is there any way to determine what the issue is without having to look through all of the files manually. I now to search for the keyword Warning, but what else? Thanks Lothar server2-diagnostics-20180430-1501.zip