Squid
-
Posts
28,770 -
Joined
-
Last visited
-
Days Won
314
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by Squid
-
Getting constant activity on all harddrives
Squid replied to jeffmackinnon's topic in General Support
It appears that you have dual parity, and have turbo mode (reconstruct write) enabled in disk settings, and some process is currently writing to disk 2 @ 54.6 KB/s. Since you have zero cache-only shares, I'd surmise that you don't have a cache drive and the docker image is stored on disk 2 which is what would be resulting in the minimal write happening. -
As an aside, you will also have to have an array defined with unRaid (even if its only a single data drive) in order to use the system.
-
10:1 it's a misconfigured docker app creating them, but since you've ruled that out, the likely suspect is IPMI tools plugin. Removing the plugin and deleting those folders followed by a restart should tell you. If it is creating them, then should should post in it's support thread.
-
That would definitely cause the problem you're seeing. Only time the forum has ever seen that error is when either rootfs or tmpfs is completely full. If you can, post a diagnostics. Either way, a reboot is going to be required.
-
Limetech is conservative in which plugins ever get decided to be implemented. And, as the history of the cleanup plugin shows, data loss is quite possible depending upon how you've misconfigured an app. IE: There's been cases where a user has decided to place all of Plex's appdata within /mnt/user/Movies which also contains the movie files. Since that's the way Plex was configured, the plugin dutifully offers up the option to delete /mnt/user/Movies. Hence the reason for the banner, the big-ass note, and the confirmation popup.
-
Completely remove the first line.
-
Advanced view on the edit container screen, then show more settings, then adjust the path accordingly.
-
Have you checked for updates?
-
You need to post exactly what shows up when you edit the script in user scripts
-
Uninstall it, then install and run the appdata cleanup plugin
-
Post your diagnostics
-
If you look at the syslog (Tools), do you see "bread" errors?
-
Yeah, just reinstall from the link in the OP. I just pumped out a 13a version and inadvertently deleted the 13 version which resulted in that
-
Assuming that you're only accessing those containers via the local network (or via a VPN like wireguard / openVPN), then there's nothing particularly wrong or insecure per se about Sonarr being accessed via http. IE: If you're worried about a program running on your local network sniffing the packets running back and forth between your computer and Sonarr's GUI, then you've got far more important problems (like why is a program installed on your desktop sniffing the packets)
-
Doesn't appear that the messages from rpcbind can be silenced. But, I suppose that you can switch to SMB instead of NFS
-
If anyone happens to see an alert from FCP regarding "Security Violation / Blacklist" regarding anything from the Squid Repository (my plugins) or the Limetech Repository, this is a FALSE positive and already fixed.
-
how do you get rid of Bionic Folding at Home banner top of unraid
Squid replied to comet424's topic in General Support
By design... -
Boot time scheduling will never be added.
-
What are you expecting to happen? Does Schedule Applied appear and the Apply button go back to being grayed out after hitting it?
-
Upgrade your system. It's running an old version of the OS, and UD is not compatible anymore with it.
-
Just do what the message says to do shareInclude="disk1,disk2,disk3,disk4,disk5,disk6,disk7" You had a disk7 installed at one point, set up the share, then removed the disk without changing the setting. For the most troublefree experience, fix it.
-
You either don't have Unassigned Devices plugin installed, or have nothing mounted with it.
-
Only if you also want it in the cloud.
-
Have you tried doing what it suggested to do?
-
Looks like you have cabling problems to the cache drive. Reseat / replace. This cause caused issues with the filesystem on the cache drive. After reseating and rebooting post another set of diagnostics for the file system experts here to examine.
