rainformpurple

Community Applications v2025-06-02 confirmed to be working as expected on 6.12.15. Thanks!

I'm getting a blank page on versions 2025-05-29 and 2025-05-29a. Downgrading to 2025-01-28 fixes the issue, but I'm then being asked to upgrade. On my test server I performed the upgrade, and it's right back to blank apps page. All my servers are on 6.12.15.

Cool, thanks.

Yeah, no, me neither Here's basically what I did: 1. Stop array & shut down server 2. Add drive cage with 3x18TB drives 3. Start server 4. Unassign 6TB parity drive 5. Assign 18TB as new parity drive 6. Start array in maintenance mode & rebuild parity for 25 hours 7. Stop array 8. Assign new 2x18TB drives + old 6TB parity drive to array 9. Start array in normal mode, let disk sync run for 27 hours I haven't stopped the array since the disk sync.

Sure: The drive is currently a member of the array, is active and works fine. The other three 18TB drives I installed also showed up under HistDev, and I was able to remove those by clicking the X.

Thanks, I've reposted in the support thread.

Hi all, I recently upgraded my server with more storage space, and decided that in order to maximize storage space, I would add the old 6TB parity drive as a storage drive alongside the new drives. Apart from a DOA drive, this went well and after 25 hours of parity rebuild followed by 27 hours of disk clear/parity sync, everything works. However, the old parity drive, which obviously was known to the system, is now stuck in Historical Devices. The Remove button/cross doesn't work and is white rather than red. When I point to it, the cursor doesn't change, indicating there is no link to whichever function will trigger when clicked. Is this something a reboot will fix? Or stop the array, remove drive from HistDev, then restart the array? If so, I'll just leave it until my replacement 18TB arrives, as I will have to stop the array to add the new disk at that point anyway.

Hi all, I recently upgraded my server with more storage space, and decided that in order to maximize storage space, I would add the old 6TB parity drive as a storage drive alongside the new drives. Apart from a DOA drive, this went well and after 25 hours of parity rebuild followed by 27 hours of disk clear/parity sync, everything works. However, the old parity drive, which obviously was known to the system, is now stuck in Historical Devices. The Remove button/cross doesn't work and is white rather than red. When I point to it, the cursor doesn't change, indicating there is no link to whichever function will trigger when clicked. Is this something a reboot will fix? Or stop the array, remove drive from HistDev, then restart the array? If so, I'll just leave it until my replacement 18TB arrives, as I will have to stop the array at that point anyway.

I can definitely empathise with his reasons, but it was very sudden. Hopefully someone else will pick it up and continue the builds.

Hi, I couldn't find any support threads for randomninjaatk's docker containers (lidarr-extended, radarr-extended, sonarr-extended), so I'll try here. I'm running lidarr-extended and sonarr-extended and they now appear as "Not available" in my docker list. They are also removed from Community Apps and I can't find them on Docker Hub anymore either. The GitHub page at https://github.com/RandomNinjaAtk/docker-sonarr-extended states that the repo is deprecated and will be archived. I guess that goes for lidarr-extended and radarr-extended as well. Does anyone know the reason for this? Is there a replacement for these docker containers? The extended features of these containers were really useful in grabbing Youtube series and things like that, and it's too bad randomninjaatk decided to deprecate the containers.

Yeah, it was a rollercoaster. I thought I'd get away with a quick 30 minute upgrade, but it turned into a 4 hour forensics job. Today I've been slowly fixing docker issues that popped up because I forgot that newer versions of unRAID weren't happy about how things were on 6.9. As I don't trust automated scripts I don't know what actually do, I'm changing the permissions by hand for the shares I know I have to change, and then I'll see about the rest later, if at all necessary.

Yeah, that went straight to hell in a handbasket. Upon rebooting into the supposedly upgraded system, the console starts spewing error messages stating GLIBC_2.34 cannot be found (required by rm and sleep). My USB key has also been blacklisted for some reason, and no dockers nor VMs are started. The WebUI is only half-way functioning and doesn't display any meaningful data (no disks show up, no server stats, no plugins show up, no controls work, nothing. Exactly what I was afraid of what would happen, in other words. I'm not saying it's related to the tailscale plugin in any shape way or form, just to make that clear. Currently trying GUI safe mode to see what's going on and to see if I can get it working enough to contact Limetech support to have un-blacklist my USB drive. Edit 1: Downgrading to 6.9.2 got rid of the error spewing, and it appears my USB drive isn't blacklisted anymore... I'm not entirely sure what's going on, but something isn't right. As a curious aside, the tailscale plugin now works and I've re-registered my server with the Tailscale mothership and everything works as expected. Edit 2: I couldn't let this lie and had to tinker with it. I nuked all my plugins and now it works with 6.11.5, so I'm adding back the plugins one by one to see which (if any) breaks my server. Edit 3: The culprit is a user script I have written, which tries to install some packages and that breaks everything, requiring a hard reboot to get out of. The script is now disabled and things look fine. Edit 4: The problem was that I for some ducked up reason installed a package named aaa_glibc_somethingsomething.txz that apparently worked enough on 6.9.2 to allow the audio tools I installed via the same script to work. That caused various problems when installed on 6.11.5, as the installed version of glibc is newer. After booting into safe mode a number of times I have verified that this was indeed the cause and that package is no longer installed on boot. I'm currently working my way through the list of packages to find compatible versions, and I feel that this is something that maybe could be installed via Nerd Tools. The mismatched glibc also caused all the other problems with the unRAID WebUI, registration retrieval status, network issues, etc. My USB key is not blacklisted, the mismatch caused the verification to fail miserably and probably receiving garbage data back, leading it to think that the USB key was blacklisted. That is sorted now and everything works. In any case, my server is now finally upgraded to 6.11.5 and the tailscale plugin works perfectly

The plugin didn't make any difference, so I'm currently upgrading my server to 6.11.5, which I should've done many moons ago anyway. I'll report back once the upgrade is complete.

Yeah, I keep putting off updating, because I never seem to find the time to deal with eventual problems that may arise by doing so. I should probably just do it. Some day. I'll install the Unassigned Devices Preclear plugin and see if that fixes it temporarily. Thanks!

Sure thing. aram-diagnostics-20230510-1429.zip