bonienl

For the record. These are the current stable releases offered from the web site.

With Unraid 6.6 these are hardcoded thresholds of 70% (orange) and 90% (red). With Unraid 6.7 these thresholds are tight to the general disk utilization thresholds, which can be changed by the user

The GUI supports MTU size setting on a physical interface, which is automatically propagated to the associated VLAN interfaces. I have never tried it, but it should be possible to assign each VLAN its own MTU size using CLI. The restriction is that a VLAN MTU size can never be bigger than the MTU size of the physical interface.

I can confirm I am seeing the same issue [rc4] when transferring a big file (14 GB). Initially only parity and the selected disk show read/write activity, but after a while other disks in the array start to show read activity. These are not constantly the same disks but at the end of the transfer all disks in the array are spun up due to this behavior.

When you create a VLAN, it basically is a different network and your router/firewall needs to be set up correctly to let this network talk to your original network and the Internet.

Excellent job LSIO guys. Installed the new version without a hitch. Very pleased with your work 🙂

VLANs follow the MTU size set for the physical interface. It is not possible to assign different MTU sizes per VLAN on the same interface.

There is no GUI support for that. You'll need to add this through CLI.

Pedantic indeed 😉 Changed to NO

New syslog information is always appended to an existing log file. Log files are never overwritten or deleted.

The IPMI plugin would need to add support for the dashboard display. if ($('#mb-temp').length) { var temp = $('span#temp').text(); var unit = temp.indexOf('C')>0 ? 'C' : 'F'; temp = temp.split(unit); if (temp[0]) $('#cpu-temp').html('Temperature: '+temp[0]+unit); if (temp[1]) $('#mb-temp').html('Temperature: '+temp[1]+unit); } The above code extract comes from the System Temp plugin. It checks the presence of the field 'mb-temp' and puts the temperature readings in the fields 'cpu-temp' and 'mb-temp' which get displayed on the dashboard page.

Starting with RC4 the correct permissions/ownership are set on newly created files. Log files created with a previous version, you need to change manually (or delete).

This file defines the physical interfaces present in the system. Use Settings -> Network Settings to configure these interfaces. Docker interfaces are configured under Settings -> Docker. You need to stop the Docker service to make changes. These are my Docker network assignments (I use both IPv4 and IPv6). Any physical interface which has an IP address defined under Network Settings (such as eth0 or br0), will have automatic docker network assignments. You can define physical interfaces without IP address (IPv4 address assignment = None), this allows to add manual docker network assignments to an interface.

Settings survive a reboot. E.g. when flash mirroring is enabled, it will log everything to flash from the moment you start the server and syslog is activated. My settings show Unraid to act as central syslog repository (Local syslog server = Enabled) and log files are stored in the folder (share) syslog, which is set as a cache only share. I have other devices in my network sending syslog information to Unraid, while Unraid sends syslog to itself too (Remote syslog server = <unraid ip address>) Under Tools -> System Log you can view the syslog files from the different devices.