kennymc.c

Ich habs mal korrigiert. Ist aber auch im Englischen nicht eindeutig, da es eher nach einer Statusangabe klingt als der Name für einen Button, der eine Aktion auslöst.

I already solved the problem. See my comment at the top of the post. Where does it show 0 rpm? If I let IPMI control all or some of the fans they will always run at full speed. Even with fan thresholds adjusted my Noctua fans will sometimes report a false rpm to trigger the IPMI fan failure control that lets all fans run at full speed. With this plugin I can set a minimum speed to not trigger this behaviour. With 30% minimum speed they still run at 300 rpm. Seems to be a know problem with this brand.

Edit: Solved by resetting the BMC and then restarting fan control I am also having problems with all my fans running at full speed after upgrading the BIOS and BMC firmware of my Supermicro board today. I already tried stoping and starting fan control, adjusted the minimum fan speed and also did a system reboot. Fan thresholds have been adjusted to match the low rpm of my Noctua fans. This is the fan log: 2024-02-03 18:37:39 Starting Fan Control 2024-02-03 18:37:39 Board: Supermicro Board Model: X11SCH-LN4F 2024-02-03 18:37:39 SM Board selection: 11 2024-02-03 18:37:39 Setting fans to full speed 2024-02-03 18:37:49 Fan:Temp, FAN1234(33%):CPU Temp(30C), FANA(28%):HDD Temp(Spundown) 2024-02-03 18:41:50 fan control config file updated, reloading settings 2024-02-03 18:41:50 Fan:Temp, FAN1234(41%):CPU Temp(29C), FANA(31%):HDD Temp(31C) 2024-02-03 18:41:51 Stopping Fan Control 2024-02-03 18:41:51 Setting fans to auto 2024-02-03 18:41:56 Starting Fan Control 2024-02-03 18:41:56 Board: Supermicro Board Model: X11SCH-LN4F 2024-02-03 18:41:56 SM Board selection: 11 2024-02-03 18:41:56 Setting fans to full speed 2024-02-03 18:42:06 Fan:Temp, FAN1234(41%):CPU Temp(28C), FANA(31%):HDD Temp(31C) And these are my settings:

Das Problem ist, dass die json Dateien für den Docker Healthcheck alle 5 Sekunden immer wieder mit dem fast selben Inhalt überschrieben werden. Nur der Timestamp ändert sich. Der Bug ist auch hier beschrieben:

Since you even get this notification when notifications are disabled I would definitely prefer an option to disable the success notification. I first thought this was a bug. I also only want notifications when something goes wrong. Everything else can be found in the sys log.

I think I have solved the problem: I simply stopped the array while the USB hdd was turned on and mounted. When the USB hdd then also got unmounted, I switched it off and restarted the array, waited a while and stopped it again. The messages in the log did not appear anymore. Starting the array worked again without any problems.

That is my backup usb hdd which only gets powered on during weekly backups. Strange that this only happens when the array is stopped and when the hdd is not powered on. I assume I should run xfs_repair? Which /dev should I choose? There is no dm-5 in /dev, just dm-1 to 4. I tried it with the corresponding id sdf and sdf1 but this results in bad primary superblock - bad magic number !!! shortly after starting a dry run. I let it run with sdf for many hours (8 TB hdd) but it ends with Sorry, could not find valid secondary superblock Do i have to add something because the drive is luks encrypted?

It happens as soon as you stop the array and then the callback messages reappear every minute until the array is restarted. Diags have been saved after the array has been stopped and restarted around two minutes later. smartserver-diagnostics-20230926-1942.zip

Ok, I created a PR so that it matches the current English translation file.

No one who has an idea why these messages appear even with a new USB flash? I have recently rebooted the system and it worked fine so far. Is it possible that these are leftovers from the corrupt old USB flash, since they also have the same block numbers?

Thanks for this quick update. I noticed that the on/off sliders are not included in the translation files. Also "Force Update" is still show in English although it has been translated. Another issue is that as soon as I click on a container name, menu entry or button on the Docker tab and come back the Add Folder button is in English. Only by reloading the page it is translated again. I could reproduce this with Chrome and Safari after I deleted my browser cache. Firefox doesn't seem to be affected. On the VM tab this button is always in English.

I created a German translation. Maybe this could be moved to GitHub like with most of the other translations and plugins (https://github.com/unraid/lang-en_US)? This would also simplify updates and bug fixes. de.json

I noticed this syslog entry when opening the Docker tab: [error] 8653#8653: *609961 open() "/usr/local/emhttp/plugins/folder.view/langs/de.json" failed (2: No such file or directory) while sending to client, client: 192.168.1.101, server: 192-168-1-201.xxx.myunraid.net, request: "GET /plugins/folder.view/langs/de.json HTTP/2.0", host: "192-168-1-201.xxx.myunraid.net", referrer: "https://192-168-1-201.xxx.myunraid.net/Docker" The mentioned json file for the German translation indeed does not exist. Unfortunately, I can't find a folder for this plugin in the English GitHub Unraid translation repository, so this file can't exist. Or is there (for whatever reason) another way chosen for the translation of this plugin?

Today I wanted to install the 6.12.4 update. When I stopped the array as recommended before the update, I noticed again the same Buffer I/O error messages in the log with exactly the same block numbers, which I already had before the last update and which then caused the flash drive to set itself to read-only after a reboot. This can't indicate a corrupt USB flash drive again, can it? I can restart the array afterwards without any problems. However, I would like to know what these messages mean exactly, since I use a completely new USB flash drive of the same model, which has also lasted the last few years with various updates.

Has anyone compared the changes that seem to have been made with 6.12.4 with the previous version? Maybe it's just something that is not relevant for the script.