online

It would be nice to get more visibility here because I agree the severity seems off for this type of event. A parity check start event is a desired expected action. Labeling it as "warning" suggests something unexpected or undesired has occurred, which isn’t true for routine maintenance. Infrequency alone doesn't justify a warning level; parity checks are part of normal operations, even if run weekly or monthly. If severely degraded performance is a concern, IMHO that should be monitored/alerted via actual resource metrics (e.g., sustained high iowait, disk queue depth, throughput drops, etc.), not assumed from the start of a scheduled parity check.

I ended up getting read-only filesystem alerts for the USB drive, which was causing all these issues above. Not sure how I missed these errors the first time around. Now it makes sense why I couldn't adjust share configurations. I do wish a descriptive error message appeared from the UI, like "Couldn't write updated configuration" rather than nothing. IMHO It is annoying that Unraid is suspectable to a single point of failure with a USB even if recovery is always possible. Guessing there are opinionated topics around that design. I'm also unsure how this occurred in the first place as I'm using a somewhat decent flash drive for my setup.

I believe so, I've run the mover multiple times while ensuring the share isn't being used by anything else (Docker container, SMB, etc.). Assuming I'm checking the right directories, I'm also not seeing this share in the Cache pool anymore. root@Tower:~# ls -l /mnt/cache/ | grep "plex-media" root@Tower:~# ls -l /mnt/user* | grep "plex-media" drwxrwxrwx 1 nobody users 5 Apr 22 18:07 plex-media/ drwxrwxrwx 1 nobody users 5 Apr 22 18:07 plex-media/ root@Tower:~# I'm also realizing I'm unable to adjust the backing storage for any Share, including new ones. I just created a new share where the backing storage pool was Cache only (no secondary storage). After creating, the share switched to using Array only. Attempting to switch from Array to Cache also doesn't change when saving. My instance seems to be having this issue across all shares. I have performed a reboot, which didn't resolve the issue.

I have a Share setup where the Primary storage is set to Cache and the Secondary storage is set to Array. I'm attempting to drop the Cache storage completely and use Array as the primary and only backing storage. Each time I attempt to save Primary storage to Array and Secondary storage as None, the change is reverted after saving. Existing Settings: Desired Settings: