buscopina

@DataCollector Danke nochmal für den Hinweis mit der ASM1166 Karte - inzwischen habe ich die erhalten und auch endlich mal flashen können, C10 wird wie gehabt erreicht, passt also alles. Kurz was anderes (und gerne Hinweis, falls ein neuer Thread von Nöten wäre): Ich baue jetzt ein paar Sachen noch ein und wollte bei der Gelegenheit auch das BIOS mal flashen. Hatte aber Probleme mit der 21er Version, wegen des standardisierten Safe Boots. Selbigen konnte ich im Bios nicht deaktiveren (ausgegraut) und ich konnte nur noch ins Bios booten, kein Unraid via Stick... gibt's da einen Workaround wie das dennoch geht bzw. gilt es etwas zu beachten wenn man kein klassisches OS wie Windows oder Linux einsetzt? Momentan bin ich auf der 19er Version und da geht alles.

Did you adjust anything in the meantime? Upgrade, downgrade, modifications?! If so, maybe you should tell us what did the trick so others can follow accordingly 😉

Interesting. In my case I have xfs encrypted drives and - for now - it’s only a ssd within the pool that spins up immediately. I will test a a simple downgrade to 7.3.0 once I am back at the office… Edit: I installed another PCIe ASM card, attached a new hdd and now everything is back to normal. That means: I did not change anything in my setup (e.g. go file) but had to reboot the server. I am unaware what did the trick but not all hdds and ssds are sleeping after the default spin down time (45 minutes). I know, no real solution to follow but at least it seems to work (again).

Not in my case. After ripping out the HDD that did spin up immediately after a manual spindown it's now a second cache device /ssd) that wakes up immediately... not that much of a nuisance as there is no mechanical spinning but it's really strange behaviour that was not an issue before.

I had the same error but rolling back to 7.3.0 or 7.2.7 did not do the trick. Meanwhile I deleted the drive from the array (Toshiba N300) and everything's back to normal... I was just tired of looking what caused the drive to be spun up immediately as I could not find anything unusual within the logs... Just wonder if it is more drive related as my Seagate Exos were not affected and always remained spun down.

I had the same problem with a Toshiba N300 - the Seagate Exos are not affected, just the Toshiba. Couldn't find the culprit, so I took out the Toshiba of the Array (and the whole system)

I ran into a similar issue. It's just a Toshiba NAS drive that is woken up immediately after being spun down. Same thing with So currently I am on 7.3.1... Just wondering if a downgrade to 7.2.x would be a workaround... I am not happy with a 40is minute wakup all the time... in my case it does not spin down anyway and ther is no other thing running apart from the immediate SMART check.

Yep, it seems that this Plugin is not working as expected anymore with the newes Unraid release... I have rolled back to @alturismo 's PWM Fan plugin even if it is not as customizable as this one. Instead of the CPU Fan I am now controlling another case fan that helps cooling the upper compartment of the NAS with CPU temp and the lower one based on HDD temps... CPU itself is handled via BIOS directly... A pity that this one seems to have been abandoned now...

Lieber @DataCollector , merci vielmals. Auch für die Nachfrage, da war ich nämlich unpräzise. Momentan habe ich keinen echten PCI Platz belegt, nur der blikvm ist momentan in einem PCIEX-Slot drin, aber hier ja ohne Funktion. Die Erweiterung benötige ich nur für mechanische Platten. Sollte ich doch später umschichten, würde ich alle SSDs dann ohnehin über das Mainboard direkt anschließen und nicht über die Zusatzkarte. Zwei mechanische HDDs könnten obendrein als BackUp-Hot-Swaps genutzt werden, je nach dem, auf welches Gehäuse ich jetzt gehe. -> Sehe ich das dann am Ende richtig, dass ich hier theoretisch nach Preis der Dinger gehen könnte, richtig? Ich bin ja fast schon soweit, dass ich sage, es kommt eh alles irgendwo aus China, dass es am Ende kaum Unterschiede geben wird. Eilig ist im Übrigen diesmal nichts, sondern ein kleines Projekt, das ich bis Mai wohl angehen werde. P.S.: Danke auch @_alo_ (will ich nicht vergessen haben :))

Kurze Frage in die Runde in Sachen ASM1166: Ich werde meinen Server nun doch erweitern (müssen), also benötige ich mehr Sata Anschlüsse. Habt Ihr denn Empfehlungen, welche Erweiterungskarten mit dem Board gut harmonieren? PCIe oder die Erweiterung am M2-Slot (ich hab einen noch frei) - welcher Hersteller, etc. Bei den einschägigen Seiten habe ich natürlich geschaut, aber da sind auch viele nonames drin und ich weiß nicht recht, worauf ich achten muss.

Unfortunately the error persists. I changed the PWM headers and - as expected - the NAS ran fine for a while. The plugin could control turning fans on when hdds were spinning and swithed them off when they are asleep. After 5 days suddenly both fans spun up full speed which I could only resolve with a reboot. Bottom line: It might be the mainboards culprit so I am either going back to let the fans just spin with slow rpms and don't bother at all. Or I am digging into the fact that it might be a BIOS issue and some of the old roms solve it. Or try a different solution within Unraid (Docker). But thanks anyway for the effort you put into this plugin. So far the most promising for me even if it did not survive the week in my case :)

Identify does not work, this fan just ignores the command(s). When doing the "Run Now" the log shows the Manual Run entry with the correct RPMs in the log but does not trigger the adjustment based on hdd temperature. I probably will open the NAS and try a different header as you suggested and work it over. To my understanding it's just a bit weird that only one fan "misbehaves" and this also only after a certain period of time (couple of days) where it worked flawlessly.

Okay, same error. HDDs are spun down, so no temperature is shown and the two fans should remain off. Unfortunately the front fan is spinning at full speed at 1280rpms. Tried to disable the plugin and the rear fan is spinning up (as intended) but after activating the plugin only the rear fan goes down again whereas the front fan is just spinning at 1280rpms. That said: It seems that the connection from the plugin to the front fan is somehow interrupted. Unfortunately a simple deactivate acticate procedure does not get the fan to work normal and neither does a manual operation (run now) changes anything. Only a reboot does the job. But as my server idles when I am away it's a bit of a nuisance if this happens regularly - in this particular case after 9 days - and the log does not show anything unfortunately. Last spinup of disks has been on the 9th, full speed of one array fan on the 12th not following the plugin's parameters.

I will do. When the issue occured it was the rear fan that went up to 1280rpm with no reason as the hdds were asleep and therefor the fans should be switchef off - but I could not manage to get it switched off at all even if I turned off and on the plugin. At this very moment the fans are both setup with a minimum of 20% when the hdds are spinning/in use.

I did reboot the server and jumped into the BIOS. Unfortunately all settings have already been set properly: PWM / Manual plus Fan Stop disabled... so this was not the issue... Any further ideas? After the reboot the plugin works again as intended but I do suppose that the error will occor after some time again.