EDACerton

I'll have to look at the exceptions bug, that should be an easy fix later on. There are a lot of things that can cause the drive to spin up -- even something like listing directory contents (depending on what data is cached, how folders are split, etc.). The monitor ignores directory activity like that by default since it creates a lot of noise and won't keep the array from stopping, but I can look at making that configurable in an update. Trying to chase spinups to that degree is probably going to be more pain than it's worth, though.

This plugin provides the storcli64 application for the Unraid CLI (used for management of MegaRAID adapters). Upstream: https://www.broadcom.com/support/download-search?dk=storcli

This plugin provides the ddrescue application for the Unraid CLI. Upstream: https://www.gnu.org/software/ddrescue/

This plugin provides the ncdu application for the Unraid CLI. Upstream: https://dev.yorhel.nl/ncdu

Exposing the Unraid WebGUI to the internet is not a recommended practice. A better approach is to configure a VPN (such as Tailscale) and then use that to provide a secure connection to the WebGUI. TOTP would be a nice addition for users who choose to expose the WebGUI anyways. In theory, it wouldn't be that hard to add to the login process (there are PHP libraries that exist to handle TOTP), but there would be some caveats (particularly, that the TOTP secret would have to be stored in plain text on the flash drive). I did even look to see if there was a practical way to add TOTP via a plugin, but all of the choices to do that are bad (requiring modifications to the WebGUI login code, etc.), so that's a no-go.

Anything including "usb" is flagged as drive related... you can add more specific searches in the configuration if you want: Settings -> Enhanced Syslog Settings -> Custom Match

The immediate thing that jumps out to me is that you have files from /mnt/user/system on disk3: system shareUseCache="prefer" # Share exists on cache, disk3 This is likely either the docker or libvirt image, as both are located in /mnt/user/system -- and, by default, anything with "system" in the name is automatically filtered out of file activity. I can see that your install is using the default exclusions: {"level":"info","filter":"(?i)appdata","time":1752107420,"message":"Adding exclusion filter"} {"level":"info","filter":"(?i)docker","time":1752107420,"message":"Adding exclusion filter"} {"level":"info","filter":"(?i)system","time":1752107420,"message":"Adding exclusion filter"} {"level":"info","filter":"(?i)syslogs","time":1752107420,"message":"Adding exclusion filter"} I would remove the exclusion for "system" (or even all of them), save settings, then check again after a bit.

Please install the "Plugin Diagnostics" app from CA, then generate and provide diagnostics for "File Activity".

In essence, your system was creating activity faster than it could report it, which is why the "queue overflow" message occurred. With the previous backend, a similar fault would silently drop the activity; the new backend recognizes that as a problem, but logs it more than it should (obviously). I've improved how this situation is handled in 2025.06.28: If a queue overflow occurs, file activity will make a few attempts at increasing the kernel limit to allow for more events to be retained After a certain point (right now, increasing that default from ~16K to around ~500K), it will log that it will not increase the limit any further; once this occurs, some activity messages may be lost (similar to the previous behavior), but no further messages will be logged about it. Feel free to give it a try :)

I’ll take a look at this in a bit, seems like you found a limit somewhere 😂

This is the updated version that is in CA.

Can you explain “having an error”? Does it work/just seeing an error in logs, or does it not work, and what does the error look like? There’s a couple places that could produce a similar message. Edit: I did a quick test on my computer, I see the same error in the Javascript console. This is harmless; it's checking to see if a UK-specific localization file exists (it doesn't, but it just falls back to en-US in that case). I'll look at suppressing that error in a future update, but for now you should be fine

Try using the "Clear Data" button on the settings page and see if they come back.

The plugin was replaced due to the conduct of the previous author. That's all that I will say on that. I'm always open to constructive feedback.

Derp. Testing a fix now. Edit: please enjoy 2025.06.14.

Future updates and support for this plugin will be provided here:

An improved filter will be in an upcoming release.

Future updates and support for this plugin will be provided here:

Future updates and support for this plugin will be provided here:

Reserved.

Reserved.

Reserved.

Overview File Activity is a powerful Unraid plugin that helps you understand exactly what’s causing your disks to spin up by showing recent file write and modify activity across your array, pools, cache, and unassigned devices. With a brand new Go-based backend for improved performance and reliability, File Activity makes it easier than ever to track down unwanted disk activity and optimize your server. Key FeaturesGo-Based Backend: The new watcher backend is written in Go for greater speed, efficiency, and stability. Advanced Sorting & Filtering: Sort and filter activity by date, action, file path, or disk group to quickly find what you’re looking for. Share Activity View: See activity grouped by share for a high-level overview. Customizable Monitoring: Choose which disks, SSDs, cache, or unassigned devices to monitor. Efficient Log Management: Automatic log rotation keeps performance high and storage usage low. How File Activity Helps YouTroubleshooting Disk Spinups: Quickly identify which files or processes are causing disks to spin up unexpectedly. Plugin & Docker Debugging: See if a plugin, Docker container, or VM is writing to disk when it shouldn’t. Changeloghttps://github.com/dkaser/unraid-fileactivity/releases Feedback & SupportQuestions, suggestions, or issues? Reply to this thread or open an issue on GitHub: https://github.com/dkaser/unraid-fileactivity/issues.

Overview Open Files is a troubleshooting plugin for Unraid that helps you quickly identify which files are currently open on your array and which processes are holding them. If you’ve ever had trouble shutting down your server cleanly, or wondered what’s keeping your disks busy, Open Files gives you the answers in a single, easy-to-use page. Key FeaturesLive View of Open Files: Instantly see all files currently open on your array, including the process name, PID, and file path. Identify Shutdown Blockers: Find out exactly which processes are preventing a clean shutdown, so you can take action. Process Management: Optionally kill processes directly from the plugin interface to free up locked files. Filter and Sort: Quickly filter and sort the open files table to focus on what matters. How Open Files Helps YouTroubleshooting Shutdowns: If Unraid won't stop the array or shut down cleanly, Open Files shows you exactly which files and processes are still active. Safe Maintenance: Before performing maintenance or upgrades, ensure no critical files are in use. User and Plugin Debugging: See if a user, Docker container, or plugin is holding files open unexpectedly. Changeloghttps://github.com/dkaser/unraid-openfiles/releases Feedback & SupportQuestions, suggestions, or issues? Reply to this thread or open an issue on GitHub: https://github.com/dkaser/unraid-openfiles/issues

Overview Enhanced Log is a powerful syslog enhancement plugin for Unraid, designed to help you get the most out of your system logs. If you’ve ever struggled to find important events in a sea of log entries, or wished for more control over how your logs are displayed, Enhanced Log is for you! Why Use Enhanced Log?The stock Unraid log viewer is functional, but Enhanced Log takes your troubleshooting and monitoring to the next level: Custom Highlights: Easily add your own rules to highlight log entries by keyword, severity, or pattern. Make critical events stand out with custom colors. Advanced Filtering: Instantly filter logs by category (e.g., drive-related, file system, network), keyword, or your own custom rules. Focus on what matters most. Counts Page: See a summary of recurring log messages, with counts for each unique entry. Quickly spot patterns, repeated errors, or noisy services. How Enhanced Log Helps YouDrive Issues: Instantly highlight and count all SMART errors or drive-related warnings, making it easy to spot failing hardware. Network Troubles: Filter and colorize network-related log entries to quickly diagnose connectivity problems. Security Monitoring: Highlight and count failed login attempts or suspicious activity. Plugin Debugging: Filter logs to focus on messages from a specific plugin or service. Changeloghttps://github.com/dkaser/unraid-enhancedlog/releases Feedback & SupportQuestions, suggestions, or issues? Reply to this thread or open an issue on GitHub: https://github.com/dkaser/unraid-enhancedlog/issues.