tardezyx

Ah thanks: root@godsbane:/mnt# ls -al total 64 drwxr-xr-x 17 root root 340 Nov 15 01:25 ./ drwxr-xr-x 20 root root 440 Nov 29 23:36 ../ drwxrwxrwx+ 1 nobody users 74 Nov 28 04:30 cache/ drwxrwxrwx+ 8 nobody users 123 Nov 15 01:35 disk1/ drwxrwxrwx+ 11 nobody users 181 Nov 15 01:35 disk2/ drwxrwxrwx+ 10 nobody users 165 Nov 15 01:35 disk3/ drwxrwxrwx+ 10 nobody users 165 Nov 15 01:35 disk4/ drwxrwxrwx+ 8 nobody users 119 Nov 15 01:35 disk5/ drwxrwxrwx+ 8 nobody users 130 Nov 15 01:35 disk6/ drwxrwxrwx+ 8 nobody users 127 Nov 15 01:35 disk7/ drwxrwxrwx+ 7 nobody users 107 Nov 15 01:35 disk8/ drwxrwxrwx+ 6 nobody users 84 Nov 15 01:35 disk9/ drwxrwxrwt 2 nobody users 40 Nov 15 01:21 disks/ drwxrwxrwt 2 nobody users 40 Nov 15 01:21 remotes/ drwxrwxrwx+ 1 nobody users 14 Nov 28 04:30 ssd-cache/ drwxrwxrwx+ 1 nobody users 123 Nov 28 04:30 user/ drwxrwxrwx+ 1 nobody users 123 Nov 15 01:35 user0/ I'm executing setfacl at the moment and will obverse if it happens again and will then check it. It could be that I tried to set some security settings from my workstation to get access back several weeks ago. I cannot remember exactly. Hopefully I do not have to execute setfacl regularly. It could also be that it only happens when I move/copy files into an Unraid folder which have special permissions (ACL) set and then they are inherited upwards somehow (whyever). By the way, I do not use Windows Explorer but the Total Commander accessing a rootshare (as mounted network drive) I've set on Unraid.

@trurl Are you sure, this is an SMB issue? When this issue occurs, I am still able to connect to all other shares/folders, read files, etc. There is also no prompt comming up for the locked shares/folders. So, the connection itself works. In my opinion, it is a permission/rights issue on the Unraid server.

No, private ones.

I'm starting to get a tit. I have rebuilt my Windows (with the same local user/PW as before). Now as soon as I create, modify or move any file from my Windows workstation to a share on the Unraid server or even generally create a new file on the Unraid server, I am denied access to the parent folder or even the top affected share of the Unraid server. I have to go to Tools -> New Permissions each time and select the affected share there and start the whole thing. I have already done this for all shares, but it happens again and again and it's quite annoying because you can't practically work that way. What is the reason for this?

I had already installed the temp plugin, nerdpack and pearl and clicked detect which now still shows me this: I am not sure about the correct sensors (if I remember correctly, I had once renamed those "CPU Temp" and "MB Temp" sensors a while back - i think, remembered wrongly 😄). In Fan Auto Control I have these options: I guess, I need to open the case and connect back & middle fans to one MB fan connector, as you said, and then just try & error which one of these three is the correct one. Is this correct?

Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `jc42': * Bus `SMBus I801 adapter at f040' Busdriver `i2c_i801', I2C address 0x18 Chip `jc42' (confidence: 6) * Bus `SMBus I801 adapter at f040' Busdriver `i2c_i801', I2C address 0x19 Chip `jc42' (confidence: 6) * Bus `SMBus I801 adapter at f040' Busdriver `i2c_i801', I2C address 0x1a Chip `jc42' (confidence: 6) * Bus `SMBus I801 adapter at f040' Busdriver `i2c_i801', I2C address 0x1b Chip `jc42' (confidence: 6) Driver `it87': * ISA bus, address 0xa30 Chip `ITE IT8728F Super IO Sensors' (confidence: 9) Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): Y Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK Now, how do I proceed?

What!? Is there a manual for how to correctly set this up?

Nope, you can switch through the PWM controllers and set (activate/deactivate) every one of them each on their own. It even shows in your unraid system log different autofan process IDs: Jun 6 23:34:30 godsbane autofan: autofan process ID 5315 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm1 -f /sys/devices/platform/it87.2608/hwmon/hwmon2/fan5_input Jun 6 23:34:30 godsbane autofan: autofan process ID 5350 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm3 -f /sys/devices/platform/it87.2608/hwmon/hwmon2/fan4_input Jun 6 23:34:35 godsbane autofan: Highest disk temp is 38C, adjusting fan speed from: FULL (100% @ 2265rpm) to: 189 (74% @ 1748rpm) Jun 6 23:34:35 godsbane autofan: Highest disk temp is 38C, adjusting fan speed from: FULL (100% @ 1708rpm) to: 189 (74% @ 1662rpm)

After deactivating the PWM controls in the plugin and re-activating with re-detecting (the 2 it has detected before), it seems to work now, again. It should be able to handle 3 controllers. Unfortunately, it detects only 2 here - so ye: I think I will leave the cpu fans set by BIOS only.

Hi, I have a Gigabyte GA-Z87X-UD3H inside a 24 HDD chassis with 3 middle, 2 back and 2 cpu fans. The fans are connected as follows: - CPU_FAN: cpu fans 1-2 - CPU_OPT: back fans 1-2 - SYS_FAN3: middle fans 1-3 When I installed Unraid several months ago, I tried to manually setup this to auto control the fans but it seemed not to detect everything correctly (not sure, atm) and I found out that the dynamix plugin is or was based on this manual setup but with several tweaks/bugfixes, I guessed. So, I have installed the plugin (without removing anything I did before with the manual setup) and wondered which sensors etc. are correct. So, I sat next to my open server and looked while checking the settings. - PWM Controller it8728 - pwm1: active, /sys/devices/platform/it87.2608/hwmon/hwmon2/fan5_input - PWM Controller it8728 - pwm2: inactive, none detected - PWM Controller it8728 - pwm3: active, /sys/devices/platform/it87.2608/hwmon/hwmon2/fan4_input So, it looked good, the disk temperatures were around 32-43° C. Now, I have received the several warnings by mail, the disk temperatures are up to 55° C (!!!) and after looking inside the server, there are 3 fans that are not active: - 1 of the cpu fans - 1 of the back fans - 1 of the middle fans This is especially strange as all of these fans are not connected solely but with a fan that works. So, what is wrong here? How can I check? The log says it adjusts the RPM: Jun 6 00:31:57 godsbane autofan: Highest disk temp is 41C, adjusting fan speed from: 202 (79% @ 1753rpm) to: 186 (72% @ 1626rpm) Jun 6 00:31:57 godsbane autofan: Highest disk temp is 41C, adjusting fan speed from: 202 (79% @ 0rpm) to: 186 (72% @ 0rpm) Jun 6 00:37:03 godsbane autofan: Highest disk temp is 42C, adjusting fan speed from: 186 (72% @ 1634rpm) to: 202 (79% @ 1748rpm) Jun 6 00:37:03 godsbane autofan: Highest disk temp is 42C, adjusting fan speed from: 186 (72% @ 0rpm) to: 202 (79% @ 0rpm) Jun 6 00:38:43 godsbane emhttpd: spinning down /dev/sdf Jun 6 00:40:55 godsbane emhttpd: read SMART /dev/sdf Jun 6 01:12:11 godsbane autofan: Highest disk temp is 41C, adjusting fan speed from: 202 (79% @ 0rpm) to: 186 (72% @ 0rpm) Jun 6 01:12:11 godsbane autofan: Highest disk temp is 41C, adjusting fan speed from: 202 (79% @ 1735rpm) to: 186 (72% @ 1630rpm) Jun 6 01:16:06 godsbane emhttpd: spinning down /dev/sdc Jun 6 01:19:44 godsbane emhttpd: read SMART /dev/sdc Jun 6 01:22:18 godsbane autofan: Highest disk temp is 42C, adjusting fan speed from: 186 (72% @ 0rpm) to: 202 (79% @ 0rpm) Jun 6 01:22:18 godsbane autofan: Highest disk temp is 42C, adjusting fan speed from: 186 (72% @ 1626rpm) to: 202 (79% @ 1748rpm) Jun 6 01:22:43 godsbane emhttpd: read SMART /dev/sdh Jun 6 01:23:10 godsbane emhttpd: read SMART /dev/sdj Jun 6 01:37:59 godsbane emhttpd: read SMART /dev/sdk Jun 6 01:53:12 godsbane emhttpd: spinning down /dev/sdj Jun 6 02:00:57 godsbane emhttpd: read SMART /dev/sdl Jun 6 02:01:09 godsbane emhttpd: read SMART /dev/sdj Jun 6 02:01:23 godsbane emhttpd: read SMART /dev/sdg Jun 6 02:02:28 godsbane autofan: Highest disk temp is 43C, adjusting fan speed from: 202 (79% @ 0rpm) to: 218 (85% @ 0rpm) Jun 6 02:02:28 godsbane autofan: Highest disk temp is 43C, adjusting fan speed from: 202 (79% @ 1739rpm) to: 218 (85% @ 1854rpm) Jun 6 02:03:27 godsbane emhttpd: shcmd (3179161): /usr/local/sbin/mover &> /dev/null & Jun 6 02:03:43 godsbane emhttpd: read SMART /dev/sdd Jun 6 02:03:43 godsbane emhttpd: read SMART /dev/sde Jun 6 02:05:40 godsbane emhttpd: read SMART /dev/sdm Jun 6 02:07:34 godsbane autofan: Highest disk temp is 44C, adjusting fan speed from: 218 (85% @ 0rpm) to: 234 (91% @ 0rpm) Jun 6 02:07:34 godsbane autofan: Highest disk temp is 44C, adjusting fan speed from: 218 (85% @ 1849rpm) to: 234 (91% @ 1950rpm) Jun 6 02:07:44 godsbane kernel: mdcmd (64): set md_write_method 1 Jun 6 02:07:44 godsbane kernel: Jun 6 02:12:39 godsbane autofan: Highest disk temp is 45C, adjusting fan speed from: 234 (91% @ 0rpm) to: FULL (100% @ 0rpm) Jun 6 02:12:39 godsbane autofan: Highest disk temp is 45C, adjusting fan speed from: 234 (91% @ 1973rpm) to: FULL (100% @ 2109rpm) Now, I manually activated PWM Controller it8728 - pwm2 without corresponding fan (as none is detected) and the log shows: Jun 6 11:19:19 godsbane ool www[32242]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start' Jun 6 11:19:19 godsbane autofan: autofan process ID 406 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm1 -f /sys/devices/platform/it87.2608/hwmon/hwmon2/fan5_input Jun 6 11:19:19 godsbane autofan: autofan process ID 443 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm2 -f /sys/class/hwmon/hwmon2/fan1_input Jun 6 11:19:19 godsbane autofan: autofan process ID 483 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm3 -f /sys/devices/platform/it87.2608/hwmon/hwmon2/fan4_input Jun 6 11:19:25 godsbane autofan: Highest disk temp is 53C, adjusting fan speed from: 70 (27% @ 0rpm) to: FULL (100% @ 0rpm) But this changed nothing - the 3 fans are still not working. By the way, all fans have been brought together. I will shutdown the server after the mover is done and will observe, if those fans are working when I reboot.

@Zonediver Another question: remote access does change to green for some seconds and then its red again. Public port 32400 is forwarded to internal server port 32400 - and opened by the firewall. Do you also know what this issue is? Update: solved. My router config was somehow destroyed (no open ports, at all)... loaded a backup and it works now.

Works like a charm. Thanks a lot!

Aloha, I wasted half the day trying to get Plex to work. I use the hotio plex docker on my unraid server. WebGui works and I can see my test movie there. Then I tried to connect to this server - from nvidia shield tv pro with plex app: it shows a yellow triangle next to my plex server's name - from my workstation with win10 plex app: same triangle and it says "server not available" Network setup: - unraid: 10.0.2.15 - shield: 10.0.3.11 (in a different vlan) - workstation: 10.0.2.10 What's wrong?

Does SWAG automatically update the IP of the server at duckdns.org? If not, what is the purpose of the duckdns token in the SWAG docker settings?

I am sure it is written anywhere in the last 58 pages but where can I find a complete list of what exactly is or can be tested and how? In short: a manual. Especially, I am wondering about the exclusion list and the extented disk test as well as the on page 2 or 3 mentioned duplicate file check test. While I think an overall healthy configuration check would be useful, I do not find it very healthy if the content of my 150 TB array would be regularly scanned completely. But I am not sure if that is the case... so what this plugin really does and wich things can be disabled.