kennymc.c

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.

Is there a way to enable/disable the schedule of a script via shell command?

Unfortunately, even with the updated script, I still get an error message when stopping Docker: Jul 28 20:03:42 smartserver root: stopping dockerd ... Jul 28 20:03:44 smartserver root: umount: /var/lib/docker_bind: not mounted. Jul 28 20:03:44 smartserver docker: Error: RAM-Disk bind unmount failed while docker stops! Jul 28 20:03:44 smartserver docker: RAM-Disk removed Jul 28 20:03:44 smartserver emhttpd: shcmd (222): umount /var/lib/docker But the RAM-Disk seems to be created without errors when starting Docker and I also get the Success message every 30 minutes Jul 28 20:06:07 smartserver root: starting dockerd ... Jul 28 20:06:07 smartserver docker: RAM-Disk created root@smartserver:~# mount | grep tmpfs | grep docker tmpfs on /var/lib/docker/containers type tmpfs (rw,relatime,inode64) tmpfs on /mnt/cache/system/docker/docker/containers type tmpfs (rw,relatime,inode64)

I wasn’t quoting your post. Your fix is working fine which doesn’t include the updated line

This doesn't work for me with 6.12.3. I can't see any logs related to the RAM disk script when replacing this line and stopping Docker.

I figured out why the second channel had disappeared. I had deactivated FANA in the global available sensors, because I did not connect a fan to this pin header. When I plugged in the fan to test it on FANA and then turned on this setting again, the second channel was visible again. But it is in fact just called FANA even if it also controls FANB. I think this is a bug, because as soon as I deactivate FANA again, FANA in fan control also disappears even if there is still a fan connected to FANB. Probably it was not considered during the development that there are also boards with a FANB header. Unfortunately, I now have another problem. According the sensors, although I have only connected a fan to FANB, FANA is now reporting 0 rpm. Other not connected pin headers are shown as N/A. Unfortunately a reboot doesn't help. I have the same problem with FANB when I connect the fan to FANA. Even if both are not connected, they are still shown as connected with 0 rpm. EDIT: Had to factory reset the IPMI interface to solve this. Maintenance/Unit Reset didn't work.

At least there were two different channels where I could assign each of them to specific sensors or hard drives. I used to have an additional fan connected to FANA. Could this cause the channel to disappear because the plugin just checks if a fan is connected to FANA but not FANB? This would also explain why the channel reappears when you connect something to FANA instead of FANB.

ID | Name | Type | Reading | Units | Event 4 | CPU Temp | Temperature | 32.00 | C | 'OK' 71 | Inlet Temp | Temperature | N/A | C | N/A 138 | PCH Temp | Temperature | 62.00 | C | 'OK' 205 | System Temp | Temperature | 31.00 | C | 'OK' 272 | Peripheral Temp | Temperature | 46.00 | C | 'OK' 339 | VRMCpu Temp | Temperature | 39.00 | C | 'OK' 406 | M2NVMeSSD Temp1 | Temperature | N/A | C | N/A 473 | M2NVMeSSD Temp2 | Temperature | N/A | C | N/A 540 | FAN1 | Fan | 500.00 | RPM | 'OK' 607 | FAN2 | Fan | 400.00 | RPM | 'OK' 674 | FAN3 | Fan | N/A | RPM | N/A 741 | FAN4 | Fan | N/A | RPM | N/A 808 | FANA | Fan | N/A | RPM | N/A 875 | FANB | Fan | 300.00 | RPM | 'At or Below (<=) Lower Non-Critical Threshold' 942 | DIMMA1 Temp | Temperature | N/A | C | N/A 1009 | DIMMA2 Temp | Temperature | 30.00 | C | 'OK' 1076 | DIMMB1 Temp | Temperature | N/A | C | N/A 1143 | DIMMB2 Temp | Temperature | 30.00 | C | 'OK' 1210 | 12V | Voltage | 12.22 | V | 'OK' 1277 | 5VCC | Voltage | 5.06 | V | 'OK' 1344 | 3.3VCC | Voltage | 3.32 | V | 'OK' 1411 | VBAT | Battery | N/A | N/A | 'battery presence detected' 'Unrecognized Event = 0100h' 'Unrecognized Event = 0200h' 'Unrecognized Event = 0400h' 'Unrecognized Event = 0800h' 'Unrecognized Event = 1000h' 'Unrecognized Event = 2000h' 'Unrecognized Event = 4000h' 1478 | VCPU | Voltage | 1.16 | V | 'OK' 1545 | VDIMMAB | Voltage | 1.22 | V | 'OK' 1612 | VCC_SA | Voltage | 1.06 | V | 'OK' 1679 | 5VSB | Voltage | 5.16 | V | 'OK' 1746 | 3.3VSB | Voltage | 3.37 | V | 'OK' 1813 | VCC_IO | Voltage | 0.95 | V | 'OK' 1880 | 1.8V_PCH | Voltage | 1.83 | V | 'OK' 1947 | 1.2V_BMC | Voltage | 1.22 | V | 'OK' 2014 | 1.05V_PCH | Voltage | 1.05 | V | 'OK' 2081 | 1.8V_PCH_GPPA | Voltage | 1.84 | V | 'OK' 2148 | Chassis Intru | Physical Security | N/A | N/A | 'OK' When the setting was still available I set the minimum speed of FANB to around 30-31%

I have Supermicro X11SCH-LN4F with a Noctua fan connected to FANB and noticed the fan control channel for FANAB is not available anymore in the plugin. Only the FAN1234 channel is showing up there. I am pretty shure there were 2 separate fan control channels for FAN1234 and FANAB before. I am not shure when the controls for FANAB have disappeared. According the the readings FANB is still running and reporting a valid speed. I saw that some else had the same problem in the old thread a few years ago and solved it by plugging the fan to FANA but this is not an option for me. Is there a a way to check if there is a problem with the control signals on this channel? I also noticed that this fan reported 0 rpm a few times in the last weeks which caused all fans to spin up to their maximum speed. I had this problem when I first set up my server and what I read about the low speed reporting seems to be normal at least for Noctua fans since they spin slower than other fans. I usually adjust the minimum speed of these fans and this has worked for me over the past years. So I don't know why this is happening again and why the fan controls are missing.

I have the exact same board with Noctua fans as well and noticed the same problem today. I am pretty shure there were 2 separate fan control channel for FAN1234 and FANAB before. I am not shure when the controls for FANAB have disappeared in the plugin. According the the readings FANB is still running but was hitting the lower limit 2 times in the last 2 hours. But this seems to be normal at least for Noctua fans and I usually then adjust the minimum fan speed. But it is the first time I am not able to do this for Chanel FANAB.

Since I still had problems with SMB login and my password was not accepted, I set it again via the users settings. That helped. I did the same with all other users on Unraid level. The root login was not affected.

I have tried to flash the usb drive again with the unraid flash creator but the process aborted before the end with a can not open device error. I then used another drive instead and the flashing process passed without errors. I replaced the contents of the config folder with those from the backup without the fsck and files with cryptic names. Seems to boot at least without errors. Since I can't use the new stick permanently for Unraid I will have to transfer the license two times. The 2nd time it should work as described in the docs by a mail to [email protected] or is this only done in very specific cases? BTW: Is it expected that an unclean shutdown was detected after replacing the failed usb drive?

Should I remove the fsck files from the config folder when rewriting the flash?

SMB also doesn't seem to accept my accounts anymore and these log entries appearing: Jul 15 16:21:50 smartserver smbd[28400]: [2023/07/15 16:21:50.699249, 0] ../../source3/smbd/msdfs.c:170(parse_dfs_path) Jul 15 16:21:50 smartserver smbd[28400]: parse_dfs_path: can't parse hostname from path smartserver._smb._tcp.local Jul 15 16:21:50 smartserver smbd[28400]: [2023/07/15 16:21:50.699309, 0] ../../source3/smbd/msdfs.c:180(parse_dfs_path) Jul 15 16:21:50 smartserver smbd[28400]: parse_dfs_path: trying to convert smartserver._smb._tcp.local to a local path Jul 15 16:21:55 smartserver smbd[28676]: [2023/07/15 16:21:55.411055, 0] ../../source3/smbd/msdfs.c:170(parse_dfs_path) Jul 15 16:21:55 smartserver smbd[28676]: parse_dfs_path: can't parse hostname from path smartserver._smb._tcp.local Jul 15 16:21:55 smartserver smbd[28676]: [2023/07/15 16:21:55.411110, 0] ../../source3/smbd/msdfs.c:180(parse_dfs_path) Jul 15 16:21:55 smartserver smbd[28676]: parse_dfs_path: trying to convert smartserver._smb._tcp.local to a local path EDIT: Seems to be the usb drive since I also get a "USB drive is not read-write" notification

Just update to 6.12.3 and had bunch of strange problems:

I just installed the 6.12.3 update from 6.12.2 but during the installation process I noticed that my license was downgraded to a trial. When I rebooted this was still the case and when I tried to reinstall the key via the url the log just said Downloading and the Installed but it still showed a trial license. Fortunately, the license was then suddenly active again after I waited a few minutes. I did everything like described in the update thread and updated all plugins and stopped the array before the update process. I also noticed these strange reoccurring log entries during the installation: Jul 15 15:31:03 smartserver kernel: buffer_io_error: 6 callbacks suppressed Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953920, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953921, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953922, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953923, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953924, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953925, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953926, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953927, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953920, async page read Jul 15 15:31:03 smartserver kernel: Buffer I/O error on dev dm-5, logical block 15627953921, async page read After the reboot I now get a log of these messages: kernel: FAT-fs (sda1): error, corrupted directory (invalid entries) Could it be due to my usb flash device not working properly anymore, as I have now also noticed many fsck files and a few with unreadable names on the flash? smartserver-diagnostics-20230715-1606.zip

I am not a plugin developer but there is a GitHub Repo for every language package which are all based on this one: https://github.com/unraid/lang-en_US Basically you just have to separate or duplicate all language specific content into one or more text files, which correspond to the format mentioned there. If I look at https://github.com/itimpi/parity.check.tuning/blob/439e7f7aff64beaec4cc8449a74b431579ca34fa/source/usr/local/emhttp/plugins/parity.check.tuning/Parity.check.tuning.page from the parity check tuning plugin probably every text string found in the translated text file will be replaced with the one from the currently active translation package. But this is something you would probably have to ask other developers.

Es gibt ein paar Dynamix Plugins, die noch nicht mit in der deutschen Übersetzung sind. An denen bin ich gerade dran. Aber Mover Tuning ist nicht dabei und müsste vom Author vermutlich noch entsprechend für die Lokalisierung angepasst werden. Mir ist auch aufgefallen, dass unter Apps immer noch viele englische Begriffe auftauchen, obwohl diese übersetzt sind. Das stimmt auch irgendetwas nicht.

Gibt es in der Schriftart, die u.a. für die Buttons in Großbuchstaben benutzt wird eigentlich kein ß? Bisher wird daraus immer ein SS, z.B. bei SCHLIESSEN. In der Übersetzung ist es richtig geschrieben.

I finally tried it today with 6.12.2 but unlike the post above me I still get an error message when stopping Docker: Jul 8 19:31:15 smartserver root: stopping dockerd ... Jul 8 19:31:17 smartserver root: umount: /var/lib/docker_bind: not mounted. Jul 8 19:31:17 smartserver docker: Error: RAM-Disk bind unmount failed while docker stops! Jul 8 19:31:17 smartserver docker: RAM-Disk removed Jul 8 19:31:17 smartserver emhttpd: shcmd (28898): umount /var/lib/docker The only difference is the default sync time of 30 minutes and instead of a ssd formatted in XFS I use BTRFS. No errors seem to occur during docker startup and the sync process.

Unfortunately a bit annoying that the primary text color also applies to the server name and the description above the menu bar. The secondary text color should rather apply for this, because the background color underneath is the same and can also be a different one than the one under the menu bar.