rabidfibersquirrel

I have to say that after running this for a few weeks, my ginormous (575k tracks) Lidarr seems to have sped up considerably. It's still not fast enough that Limbo is able to pull any API data from it without timing out, but Lidarr doesn't hang up for hours on "Identifying Album" tasks any more. The GUI loads in under 2 minutes (never loaded in less than 5, and sometimes took 10 before). It seems to continue to improve over time. CPU usage in Lidarr is high quite often most of the time, but if that's the tradeoff for such improved responsiveness then I'll take it. Thank you for putting this together @Espressomatic . Excellent work so far. Now that Compose Manager Plus has been blacklisted, can we migrate to something like Portainer easily? I'm looking into it on my own, but wondered if you had some instructions ready to go. Thanks again!

Thank you so much for the explanation. That makes sense and I appreciate the work you've done on this! I have it up and running on UnRAID now, but I'm running into a problem with the Proxy. My Lidarr WebUI takes upwards of 5-10 minutes to load due to a 550k track library, and the proxy seems to be timing out right at 30 seconds when I go to http://<Unraid IP>:4811 I'm getting "Failed to load Lidarr Version 3.1.2.4913" Is there a way to extend the timeout? Lidarr is working fine when I go to its normal IP.

Any chance you'll add a template to CA?

I saw that Seerr has officially launched. Are we good to go to change the repo on the Overseerr container? Any changes need to be made?

@binhex Will you be merging your Overseerr container with Seerr, or have an pointers for seamlessly migrating?

I'm getting an error: The plugin folder.view.plg is not known to Community Applications and is possibly incompatible with your server I can't seem to locate it in CA anymore. Has it been pulled?

@doron I will be expanding my array some more soon. I prefer to use SAS HDDs due to their affordability, and will be going 18TB or larger. Are there any plans to add more support for the Toshiba models, or is there another brand that simply spins down reliably with the plugin? I plan on making a donation regardless. The plugin has been great aside from the Toshiba business! Thanks for all you do!

I can't say I'm fully confident that they did spin down. I think I remember seeing them spun down a few times, but it was a while back. Thanks again for looking into it.

Thank you for having a look @doron! It isn't consistent. It happened three times, then it went a couple of months without an occurrence, then it happened again on four drives at once. I switched to an LSI 9400-16i to rule out the HBA, and it did happen again a day later. Since that time, I just have them set to not spin down.

Hey @doron, any chance you can have a look at this? I've mentioned it a couple of times but it seems to have been missed. I had to set all my drives not to spin down at all because they become littered with read errors and disabled some of the times that they spin down. Thank you so much for having a look!

I'm having a similar problem, where I'm logging read errors on or immediately after spindown. Hoping to get some feedback. Right now I just have those three drives set to not spin down. In my case it's causing UnRAID to disable the drives.

To access those containers you won't be able to click on to the WebGUI, but you should be able to access them by IP:Port. That's how I do it via Tailscale and other methods.

Diagnostics attached! I'm having an issue where my Toshiba MG09 drives will occasionally count up read errors on spindown. This has happened three times now, where I'll get a bundle of read errors, and it has only happened with these drives so far. The first time it happened was with a single 12 TB drive that I assumed was just defective and swapped for a Seagate of the same capacity. A couple of months later I picked up three 18 TB drives of the same model, two for parity and one for data, to start upgrading my array disk sizes. A week after installation it happened with the one that was assigned to data (two months ago). It had clear SMART data so I ran it through another preclear cycle to make sure it was actually working okay before reassigning it to the array. All has been well since then. This morning I awoke to both parity disks in a failed state and both showing 80 read errors. It may bear mentioning that the first time this occurred was with an LSI 9300-16i HBA in IT mode that has since been replaced with an integrated Intel JBOD-only SAS HBA. I can't recall offhand which LSI chipset is in the new HBA, but it has no RAID capability. While it's certainly possible that both HBAs had issues, it's unlikely that both would only affect a specific brand of drive. Thanks in advance for your help! glizzyxl-diagnostics-20240824-0612.zip

Hi @JorgeB Thank you for the response. They aren't SATA drives so that won't work.

Diagnostics attached. This has happened three times now, where I'll get a bundle of read errors, and it has only happened with these drives so far. The first time it happened was with a single 12 TB drive that I assumed was just defective and swapped for a Seagate of the same capacity. A couple of months later I picked up three 18 TB drives of the same model, two for parity and one for data, to start upgrading my array disk sizes. A week after installation it happened with the one that was assigned to data (two months ago). It had clear SMART data so I ran it through another preclear cycle to make sure it was actually working okay before reassigning it to the array. All has been well since then. This morning I awoke to both parity disks in a failed state and both showing 80 read errors. It may bear mentioning that the first time this occurred was with an LSI 9300-16i HBA in IT mode that has since been replaced with an integrated Intel JBOD-only SAS HBA. I can't recall offhand which LSI chipset is in the new HBA, but it has no RAID capability. While it's certainly possible that both HBAs had issues, it's unlikely that both would only affect a specific brand of drive. Thank you all so much in advance for your help! glizzyxl-diagnostics-20240824-0612.zip