Free Man

That's a very nice way of saying RTFM... Sigh... one of these days, my reading comprehension will improve.

Hey, @Squid, sorry to bother you, but do you have any idea why I might be getting the FCP warning noted here: https://forums.unraid.net/topic/97351-plugin-spin-down-sas-drives/page/28/#findComment-1640664 I've gotten that the last 3 or 4 weeks since I installed it from CA...

Just installed this. Was hoping to have this beta running alongside the production version and just schedule them to run on different days. I only see one AppData Backup in my list of plugins, v2026.03.13, so I don't think it installed properly. I copy/pastad the URL from the first post. Am I missing something? Do I need to uninstall the Prod version first?

Thanks for the great write up, @Samsonight! Really appreciate it As an update for those following behind. The upgrade is really a piece of cake. BACKUP your Uptime Kuma appdata directory, add :2 to the repository entry. Start. Wait... My update took less than 20 minutes, but I wasn't paying attention to see exactly how long it was.

Yes. I auto update everything, so I'm always current as of "yesterday". Current version: 2026.10.12 100% reproducible here - Just finished another FCP scan: Just realized that I'm on SAS-Spindown v 2024.11.25 - rather old, is that the current version? There no indication of an update...

I just recently purchased my first SAS drive and installed it. After a couple of months of wondering why it was never spun down (as the newest drive in the array, it had the most space, so maybe it was constantly getting used)... I decided to look into it. Someone on the UnraidOfficial Discord server recommended that I install this plugin. I've gotta say, it WORKS!!! (for my drive, at least, I read the comment above about the hit-or-miss implementation of spin down). However, on the first weekly run of Fix Common Problems after installing it, I get a warning telling me The plugin sas-spindown.plg is not known to Community Applications and is possibly incompatible with your server This is more than confusing, since I installed it through the CA Apps tab (v4.x is the last time I installed a plugin by hand - don't even remember how!) and the plugin is still listed in Apps... Bizarrely, though, I cannot now find it in the Installed Apps section, even though it's listed as an installable plugin. Any idea what's going on here or why FCP would give me a warning about this? Sorry: Should have mentioned I'm on 7.3.4. I did install this on 7.3.3 and got the original warning there - I've just put off asking about it for a couple of weeks.

Sorry, didn't read in detail enough. 😀 Sure, I'll give the beta a go. It's not like a docker container where I just point it at :dev, so, without me having to go back too far, what's the install process to get the beta version?

Just came to ask the same thing. Thanks for posting, @Gyakusetsu !

Quick comment to mention that I'm on 7.3.4, production version of the plugin and it seems to be working great for me. Thanks for picking this up, chodeus!

You are a life saver! Apparently, this has been an issue for a while, but I haven't needed to hit up the App store for a while. Ran into this 2 days ago and was beating my head on the desk. Making that change, followed by ipconfig /flushdns at the command line and I'm back up and running.

Wow! Without stopping Docker or VMs first, just hitting "Stop" and "Proceed", it took 3:12 (192 seconds) to stop the array. The miracle is that I've had only 2 unclean shutdowns. I'll move the timeout from 90 to 230 seconds. I did a "Stop All" on the container page and that took 3:06 (186 seconds). I'll definitely add 30 seconds to that timeout as well. Follow up question, though: The setting (Settings | Docker| Docker Stop Timeout) appears to be the timeout for a single container stop. It's a default of 10, which seems very short to me. Do I want to test shutting down each individual container and set it to a comfort margin above the slowest recorded shut down time, or does this also apply to a bulk shut down, such as on a restart, therefore it needs to be larger than the combined time? For now, I've bumped the timeout from 10 seconds to 45, assuming my first theory is correct and it's not a total timeout.

I've rebooted my server twice in the last week or two. First time, I hit the "Reboot" button under Array Operations on the Main tab, the second time, I clicked the "Reboot now" button after installing the 7.3.1 upgrade (from 7.3.0). I have no idea what might have caused these unclean shutdowns, since I asked the server to do it, and it wasn't the result of a power outage or other unexpected situation. This afternoon, I tried shutting down the VM service, then rebooted, and it came up clean. I don't know if that had anything to do with it or not. Diagnostics are from after this most recent (successful/clean) reboot, though I don't know if they'll be all that helpful. I'm also attaching the copy of the syslog that's being written to a pool by the Syslog Server (don't know if that's got any older info that may not be included in the diagnostics). The upgrade & reboot happened on 1 June with the reboot starting at "Jun 1 16:54:29" (to make searching easier). If anyone can find a reason that the shutdown was unclean, I'll at least have an idea of what to watch for before doing a restart in the future. As it stands, it seems that shutting down the VM service (I only have one VM running) "fixes" the problem, so maybe it's not waiting long enough for the VM to stop and it still has files open, leading to the "unclean" tag when the server restarts? nas-diagnostics-20260603-1648.zipsyslog-192.168.1.5.log

Thank you!! I'm new to USB manager and enabled HUB Processing to see what it would do and got that message. Didn't realize that I must have also enabled USBIP at the same time. I was wondering what I broke... What is USBIP? Does that allow a VM to access a USB device that's elsewhere on the network?

Took me about as long to note your reply as it did you to note my post, so I'd say we're even. 😀 Thanks for the info. I'll try to remember that the next time I have an "issue" with DiskLocation. Note that issue is in quotes because I don't think I've had any other than of my own doing.

Fix Common Problems has alerted me that I'm getting Out Of Memory errors. I've noted that the dashboard shown RAM usage at ~75% for a while now, but I've not seen it hit 100%. Of course, that may be happening when I'm not looking. nas-diagnostics-20260503-1457.zip Open to recommendations, suggestions, fixes, whatever you got! TIA