Jump to content

Squid

Community Developer
  • Posts

    28,777
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Are you sure about that? Have you done a rescan since you switched (or has another scan been run)
  2. You should post your diagnostics at a start and then also enable the syslog server (mirror to flash) and then upload the result after a crash
  3. The flash drive has been mounted read-only because of issues. A reboot should hopefully repair the flash drive. Failing that, shutdown and pull the stick and run the filesystem checks on it via Windows. Failing that, transfer to a new flash device.
  4. Nothing. Either navigate to your flash drive via Network, Flash on your other computer or shutdown the server, pull the flash drive. When you're in it, delete network.cfg from the config folder
  5. Apps and FCP are only compatible with 6.9.0+ The URL you're trying to use is ancient and outdated. Download the zip file from https://unraid.net/download Make a backup of your flash drive Extract all of the bz* files from the archive and put them onto the root of the flash Turn your server back on
  6. You have to run a correcting parity check.
  7. Look for a docker container referencing /mnt/cache/... in one of it's host paths.
  8. That's an oops on my part... Removed as part of removing the extended tests. I'll add it back in tomorrow
  9. Not an issue for you. This is what it's all about Dec 12 18:05:40 Tower mcelog: mcelog read: Function not implemented Googling that brings up only a single relevant reference, so not quite sure what to make of it, but I wouldn't worry
  10. So, from a command prompt ping -c3 208.67.222.222 Says destination unreachable?
  11. At the very least, post your diagnostics anyways and run memtest from the boot menu for a minimum of 2 complete passes
  12. While you have set the memory speed correctly, have you also set in the BIOS Typical Idle Power (or similar wording) to be Typical (or similar)
  13. One suggestion found via Google would be to run the memory at it's stock speed (2133) instead of underclocking it to 1866. Look in the BIOS for various settings.
  14. You can also try setting static DNS addresses (I'm a fan of 208.67.222.222 and 208.67.220.220) instead of pointing the DNS to the router's IP address
  15. Extended Tests are now removed from FCP Extended tests had their use a number of years ago, but nowadays No matter what you do it's a given that it will always return issues Those issues are not "real" per se They're primarily tests for SMB compatibility, (and any errors are once again not "real" issues) It takes forever to run
  16. Always best to ask in the applicable support venue. Click on the icon and if running binhex, select Support Thread. LinuxServer you're best off selecting Discord
  17. https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7M7CBCVU732XG
  18. https://wiki.unraid.net/Manual/Troubleshooting#System_Diagnostics
  19. You should post your diagnostics when that slowdown is taking place
  20. A probable fix for this is in 6.12 which is currently undergoing internal beta testing...
×
×
  • Create New...