Jump to content

Squid

Community Developer
  • Content Count

    20679
  • Joined

  • Last visited

  • Days Won

    231

Squid last won the day on May 30

Squid had the most liked content!

Community Reputation

2473 Hero

About Squid

  • Rank
    Why does gray hair grow so fast?

Converted

  • Gender
    Male
  • Personal Text
    AKA Flesh Gordon

Recent Profile Visitors

18466 profile views
  1. You should post your diagnostics. (Tools - Diagnostics, post entire zip file)
  2. You can ideally store it on the array (/mnt/user/scripts/myscript), or you can manually edit /config/plugins/ca.backup2/BackupOptions.json and change "preStartScript": "", to instead be "preStartScript": "/bin/bash /boot/config/plugins/user.scripts/scripts/CA-Backup_Stop/script",
  3. Isolating a core (Settings - CPU Pinning) means that unRaid AND docker containers will not use those cores at all. Docker pinning means that a container(s) will only use those cores which are allocated to it. BUT, those cores cannot also be isolated. VM pinning - a VM will only use the cores allocated to it. Generally used with isolation.
  4. Probably not the problem, but May 26 17:34:54 unraid root: plugin: installing: /boot/config/plugins/ca.resource.monitor.plg should not be installed on your system
  5. You're being bombed by un 4 04:40:04 Tower kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s). Jun 4 04:40:04 Tower kernel: NVRM: This can occur when a driver such as: Jun 4 04:40:04 Tower kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv Jun 4 04:40:04 Tower kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s). Jun 4 04:40:04 Tower kernel: NVRM: Try unloading the conflicting kernel module (and/or Jun 4 04:40:04 Tower kernel: NVRM: reconfigure your kernel without the conflicting Jun 4 04:40:04 Tower kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module Jun 4 04:40:04 Tower kernel: NVRM: again. Best to ask about this in the support thread for the Unraid-nVidia plugin
  6. As an aside, here's why there's two appdata shares By and large, the majority of apps within the Apps tab have a path mapping of /config (you can see it via Show More Settings / Advanced View when editing the app). Any path mapping of /config is automatically set to whatever the OS has set within Settings - Docker - Default Appdata Path. But, a small subset of applications do not have a /config settings for various reasons. One of these is piHole which has 2 path mappings (/etc/pihole and /etc/dnsmasq.d) Because neither of these is /config, the OS takes the host path as-is (which is on piHole set to /mnt/cache/appdata/...) This results in your situation of having the 2 separate folders. Note that even though the template directly references /mnt/cache, in the event that your system does not have a cache drive (or in the event of when 6.9 is released, the cache-pool the template references), then CA automatically adjusts the templates to match the user's system If there is no cache drive present in the system, CA will adjust the template to automatically directly reference an installed drive (eg /mnt/disk1 instead of /mnt/cache) If running 6.9 and a directly referenced cache pool does not exist, then CA will adjust the template to reference a cache-pool that is installed, with a fall back to an installed drive) These under the hood changes prevent the circumstance that pops up intermittently where the appdata for one of these few apps winds up being created in RAM instead of on a drive.
  7. As you've no doubt noticed, 20 minutes after you posted the next run of the feed re-added linuxserver's apps. What happens is that due to the complexity of the internet as a whole (rather surprising it even works at all to begin with), LSIO's repository failed to download after 5 attempts over the course of 15 minutes, so the feed just said "whatever, I don't care" and carried on it's merry way. This was a design choice. But, since it's rather annoying to me when this does happen seeing the posts by people worried about it, I've changed the coding so that in this circumstance, the feed will not update itself with the missing repository.
  8. https://forums.unraid.net/topic/71764-support-binhex-krusader/page/19/?tab=comments#comment-801982
  9. Yes Common reason would be that either you changed the Tag on the repository (eg: To roll-back an image), or the dockerHub author changed the FROM line in the dockerfile to reference a different base image.
  10. Separate source folders is outside of the realm of this plugin. You would need to issue the appropriate tar command via user scripts to accomplish this.
  11. I would think that they mean a zero'ing out / secure erasing of the drive. A low-level format is a misnomer since it hasn't been either necessary or even possible since IDE drives became a thing.
  12. Presumably, the drive you're having problems with is the one you've separately attached SMART for. It IS a 4TB (ST4000VN008)