mudsloth

So, it works now... After disconnecting and reconnecting Connect, I didn't have a new Alert to try to filter on, I only had the archived Alerts. It didn't work on those. But now I have a fresh Alert and it filters that just fine. Once I archived that, the filter works on that new notification but not all the old ones. I think reconnecting Connect worked to fix it. Thanks!

Thanks for the suggestion. It's a minor annoyance so I probably won't get down to that level of troubleshooting, but it's good to know a next step if I do want to dig into it.

Nope, no difference in the behavior unfortunately.

With Connect

In the Notifications pane, I can choose Info or Warning and it will filter to only show notifications of those types. But when I select Alerts it will always say there are no notifications, even though in the unfiltered All Types view there are a few red Alerts. They appear to be labelled appropriately, appearing like this: or Any time I have an issue with Unraid it always seems to be user error, but I'm not sure why this isn't working. A very minor issue, but still slightly annoying.

I need help with adding multiple directories. I see these two settings in the container that I have: Path: /media: <- set to /mnt/user/Movies/ Variable: TRIMARR_MEDIA_PATH: <- set to /media How do I also add /mnt/user/TV/ to scan? The instructions for adding multiple directories via a | separator are associated with the variable, rather than the path settings. I feel dumb about this because I'm guessing it's pretty straightforward.

Same here. The space saving is a nice bonus, but not having to scroll a list of 50 subtitles in Plex when I need to keep the volume down while my son's sleeping is a huge QoL improvement for me.

You could also consider reading the filename for an imdb or tmdb ID for a match. TRaSH guides recommend this and I expect lots of people rely on TRaSH's suggestions. Typically in this format: {tmdb-345691} Regardless, this tool is phenomenal! Super simple and does exactly what I'd been wanting to do for library cleanup for a while. Thank you!

Oh well thanks for confirming. Good news, I already have a new case on hand I wanted to move everything to. Bad news, I'm heading out on holiday travels tomorrow so won't have time to do that for a while. None of my family is going to be watching Die Hard or Christmas Vacation on Christmas.

I was adjusting stuff in the case prior to the last restart, but definitely hadn't even nudged it in weeks before this happened after my restart for the upgrade. All the missing drives are attached to the same backplane. I guess it's pretty unlikely that it's not an issue with that hardware.

I upgraded from 7.2.0 to 7.2.2 and all of my array devices cannot be found. If I click on any of the dropdowns there are no drives found at all. My cache drive and my boot drive are still there. I downgraded to 7.2.0 and the problem persisted. I tried one more prayerful reboot because I didn't have any time to troubleshoot and it's still the same. Prior to this, my server had been up for over a month and I haven't physically touched it in that time so no cables would have gotten dislodged. It seems like a giant coincidence that this happened after I upgraded, but maybe it's related? Diagnostics are attached. Help! mud-diagnostics-20251221-1950.zip

Well I'm an idiot on the case sensitivity issue. I corrected it after doing a quick search and found this: https://forums.unraid.net/bug-reports/prereleases/case-insensitive-share-name-is-not-unique-r4112/ I may have some other issues to resolve, but I should just say that this is resolved since the main issue for my post is not actually an issue.

I upgraded to 7.2.0 from 7.1.2 last week. At the same time I switched out my cache drive to something bigger because it seemed like the old one was dying (it was pretty old). I'm continuing to experience some random errors with my downloading setup so I thought I'd try a reformat of my new cache drive. And, maybe switching to a different file system if that didn't work. As I started the process to move files from the cache to the array I noticed that my largest share was set to Cache storage instead of Array. Clicking on that share brings up the window below, where the options to modify the settings are greyed out. In the bottom right it also says "Case-insensitive Share name is not unique". I have no idea why it's like that because I definitely didn't create a new share with the same name. This feels like there are bigger issues at play that are causing a variety of symptoms, but I want to stop trying to fix it on my own in case I risk messing everything up. Diagnostics attached. mud-diagnostics-20251110-1243.zip

@r2range Thank you so much! I've been tearing my hair out for the last couple weeks.

Ah, no worries. Probably a bit outside my technical abilities at this stage. Thanks!