Mors
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Mors
-
-
11 hours ago, doron said:
Sorry for my confusion.
Can you post the output of:
ls -la /usr/local/emhttp/plugins
This is showing it there right? still confused how I am missing the folder if it comes with the autofan install.
-
6 hours ago, doron said:
See previously in this thread. The autofan plugin has a bug that causes SAS drives (only) to be spun up periodically (every few minutes - basically, the polling interval).
Yea, I am not confused about any of this. You'd have to read my comments to understand what my issue is, but basically I do not have the directory to put the modified script into, to then fix auto fan (or so it appears to me, I am a linux novice).
-
1 minute ago, SimonF said:
Do you have autfan plugin installed?
I realized 60 seconds after posting you would ask, and I edited with more info.
-
10 hours ago, SimonF said:
I think this will be the root fs of the docker not of the host. you may need to add a mapping for the host root.
Open a terminal and run ls /usr/local/emhttp/plugins/dynamix.system.autofan/script
And just to be like confirming I am not an idiot (hopefully), I have both SAS spin down and Auto Fan installed and enabled. You can even see the SAS only not spinning down in my gui.
Those are 2 shucked WD drives, they spin down with no issue.
and a picture of my log, the only activity I have is the temp being polled.
-
3 hours ago, SimonF said:
You need to put in /usr/local/emhttp/plugins/dynamix.system.autofan/script it should exist if you have autofan installed.
you can add cp and a chmod +x to the go file to install at boot or use a user script.
So excuse my ignorance, but I used Krusader to search for the "emhttp" folder, because thats where I can't seem to go any further.
-
On 6/19/2022 at 3:28 AM, doron said:
Okay @DavidNguyen, here goes.
Again, please note this is not sanctioned by the plugin author and should be considered a hack, just for testing.
Also note that I didn't package it back into plugin format, which means that the change will be lost upon reboot.
Attached please find the modified script "autofan".
Steps to activate:
- Place the script in /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/
- chmod 755 autofan
- Go to settings, Fan Auto Control, set the function to "Disable", then Apply
- (Make sure process "autofan" is not running)
- Set function back to "Enable", then Apply
You should now have autofan function without offending your SAS drives.
Please report success / issues.
Pardon what I'm sure are some extremely stupid questions, but is this a directory you need to make? I cant seem to find where this is to drop the script into. I dont see anything like this when I browse either my shares, my boot flash drive or my cache disk. I assume the plugins are installed in the config folder of my boot flash drive, but I don't see where this directory would be or would be created (I assume this is all going on the flash drive).
furthermore can I use the userscripts plugin to automate having this run everytime I boot up? I see discussion few posts after this "hack" to fix autofan was posted but unfortunately that is greek to me as well. I dont shut down very often, but I like to streamline where I can as I am such a novice I try to get it running in a fire and forget sort of way.
-
51 minutes ago, itimpi said:
You might want to look into installing the Parity Check Tuning plugin to reduce the impact on daily use so you do not mind running the check more frequently (e.g. monthly).I will absolutely check this out. It has been a good learning experience. I realize now since I hadn't run one in so long, I think the estimate says 18 but I think from reading through that plugin thread, it ended up being so long and I had meant to investigate if there was a way to do the check in parts. The whole reason this all came up is I happened to be going out of town and knew there would be no use for my server for 2+ days and was planning to do a check over the weekend.
I'll mark one of the responses in the thread as a solution so we stop pinging this thread but I appreciate all the help.
-
On 6/17/2022 at 2:37 AM, JorgeB said:
Disk is not being detected, assuming it's also connected to the LSI check its BIOS, if it's not detected there it also won't be in Unraid.
I restarted the box in anticipation of plugging in a monitor and keyboard to assess, and the drive showed back up, but now it looks like unraid is rebuilding the drive.
I had not done anything other than start the array in maintenance mode, I hadn't added any data or done anything since the disk appeared offline. I'm surprised unraid is showing the missing and now back disk as "emulated" and is rebuilding it. It was time to do a parity check anyways (takes 18-24 hours to do one so I hadn't run one in 6+ months).
-
I am sorry if I am a bit of a noob at this, I haven't had any issues I couldn't google and solve before, but this one has stumped me a bit.
I attached the Diag Zip if someone who is a real expert could maybe give me a tip. I figure I either need to try unplugging and replugging all the cables (I have not changed anything hardware wise in over 250+ days, the server sits on a cabinet and is never touched really), but I figure this could be an issue since this is a drive shuc'd out of a mybook\myelements drive (or I need to tape over some pins based on other tip threads).
Thanks for your time
[Plugin] Spin Down SAS Drives
in Plugin Support
Posted
So everything is working now, I assume somewhere along the way (beyond the typo in SimonF's post, which I didn't catch either) I assume I must have had a typo myself. Though I find it very strange that I can't browse to the folder in Krusader, I am sure I have a setting not checked somewhere.
The big thing was finally seeing something about the MC command, which might be second nature to all your Linux guru's but until I remembered that is how you easily navigate and do things like put this script in the folder I felt like I was taking crazy pills a bit. One of those things where there is just so much info, and so many spaceinvader videos, that finding what you're looking for, and I spent a semi long googling and searching around these forums, can end up being quite daunting since you get a lot of relevant but not specific info.
Anyways, thanks to both @SimonF and @doron . If I can trouble you for one more question, now that I see what I did, why would you need a script or anything further to make this work everytime on boot? Since we replaced the already used script with your new code, wont this just automatically run on boot since Autofan uses this script?