matty2k

Members
  • Posts

    104
  • Joined

  • Last visited

Everything posted by matty2k

  1. It is exactly: Invalid TLD There is no DNS entry for 'NASA.fritz.box', recommend setting your TLD to 'local' or adding a DNS entry for 'NASA.fritz.box'. Fix it here: I am also using pihole as main DNS server and all listed devices are xxx.fritz.box BR
  2. I think since 2022.01.01 my TLD fritz.box is reported in common problems. fritz.box in Germany is a wide spread TLD used by AVM Fritz!Box. Kind regards
  3. Meanwhile I tried to investigate a little more. Regarding the time (see above) is when Jellyfin does the library scan and extracting covers (both scheduled at 02:00). Perhaps the crash / mce error is linked to this activity. Furthermore, mce seems to be outdated. I now get the note to update to newer version. I am on RC2 actually. Since 14 days the server is running without crash/reboot now. kind regards
  4. Indeed! Deactivating MFA im NORDVPN Account makes it immediately possible to use the container again. TNXs for the Tipp.
  5. did not change the template or anything in the network settings. yesterday the container was working well. today the container stopped and is not starting again. I just checked User and PW on wb login. All working and correct. [services.d] done. 'nordvpn login --nordaccount' will become the default login method in the future. Invalid Username or password. [cmd] /bin/sh exited 1 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
  6. Then, are the 100MB/s and duration realistic speed for parity check with my disks or is the speed too slow?
  7. Not sure if this issue is related to RC2, but I realized, that my last parity check while on RC1 was a lot faster than may recent parity check on RC2. I have attached the diagnostics too, but do not experiencing any problems. Array configuration did not change. All drives are still the same. Some more data is now stored on the drives, but not double (what also would not significantly influence the time). Actually I only set up syslog server and storing syslog on USB flash for investigating two reboots in the past. I have also realized decreased speed when copy data with krusader from disk share to diskshare. nasa-diagnostics-20211214-1934.zip
  8. Dear team, now this happens with two different docker container - one with unraid template - docker baikal - and one from docker hub without unraid template - domoticz/domoticz. The Docker creates directories which do not have sufficient permissions for the docker itself. Strangely it is in booth cases only one specific folder which only has r-x permission. Most other have rwx. of course getting one error when the docker tries to write in that directory. also tried to change permissions with midnight commander to rwx without solving the error. I am on 6.10 RC2
  9. Perhabs I have found one origin of this error message. If the requests are comming from one Windows Machine, try to deactivate the recent file history in your windows explorer. When there are files from any unraid share, windows tries to access this files when opening the explorer. I need to observe if this really is my rootcause. https://answers.microsoft.com/en-us/windows/forum/all/how-to-hide-recent-files-from-quick-access/6f7ade2a-d706-45a6-a89e-789669abcab9 BR
  10. I am on 6.10 RC2 getting the same failure: Error: Z-Stick Gen5: Driver Failed!! Actually trying to use the domoticz docker from domoticz itself. How do you pass through the usb device in extra parameters? I am trying like this: --device=/dev/bus/usb/001/003:/dev/ttyACM0 But not sure if correct. By the way .. the domoticz container from linixio is working out of the box with --device /dev/ttyACM0:/dev/ttyACM0. Regards
  11. Tried to change permissions via midnight commander to rwx without success. Also tried to add PUID 99 PGID 100 variables to template without success. Using 6.10 RC2
  12. OK. Did run memtest86 latest version 9.3 two times with 4 passes for all 13 different RAM tests with finally 0 failures. I also checked for new bios upgrade but I am on the latest. Again I would like to mention that the problem occurred with 6.10RC2 on RC1 the system was stable more than 14 days. best regards.
  13. nasa-diagnostics-20211126-1050.zipAgain, today 26th of November I have a new entry in the log: 02:00:14 NASA kernel: mce: [Hardware Error]: Machine check events logged very similar timestamp. how to figure out details? already installed mcelog and activated syslogserver. but still no clue.
  14. Got one unexpected reboot/crash again. 3 days later on 23rd of November. Strangely nearly the same time 02:07. Last time Nov 19 02:03. How to figure out? regards
  15. Had an unexpected crash/reboot last night. Now doing a parity check. And realized high read rates on an unassigned and unmounted drive .. is that normal? Amount of reads is similar to the reads on the array .. strange! nasa-diagnostics-20211119-1349.zip
  16. Dear team, last night I encountered a sudden server reboot/crash. The log and also fix common problems show "Machine Check Events detected on your server". Also some warning about: mcelog: failed to prefill DIMM database from DMI data. I have attached the diagnostics. Is there some serious hardware error I need to worry about? How to get more details? Server was running nearly 2 weeks on 6.10RC2. kind regards nasa-diagnostics-20211119-0754.zip
  17. Is this docker still supported for unraid? If I search via CA Applications it is not listed anymore. I need to klick on "show more results". Then the container is shown on docker hub.
  18. Hi folks, same here. Requests come from one client in the network which is using only SMB access to the server. Restarting the client did not solve the problem. regards
  19. In the template simply select nordlynx instead of openvpn … simple as it …
  20. Yes. For me it is working with 6.10RC1. Both work Latest and Master Branch as well. Always stuck at „connecting“ but connection is established correct.
  21. Regarding Baikal .. I just installed from ckulka/baikal:nginx. Installation OK. While doing the config I get following error: Validation error The FOLDER containing the DB file is not writable, and it has to. Please give write permissions on folder /var/www/baikal/Specific/db I only have empty baikal/Specific/ folder, no db. Any ideas how to solve the problem? Regards
  22. Same here. NordVPN is working but the log still chowing connecting.
  23. Is it possible to upload pictures into one (user) folder without creating subfolders for year and months