[Unraid OS version 6.10.0-rc1 available]

12 minutes ago, Sander0542 said:

Do I need to remove this plugin before or after upgrading to Unraid 6.10?

It doesn't matter, both scenarios work.

 

12 minutes ago, Sander0542 said:

I am hoping to keep my configuration during this transition.

WireGuard keeps on working as before with your current settings

[Browser locks up when viewing docker tab in unraid]

In Unraid 6.10 a change is made in docker container monitoring, which may help when a larger number of containers is used. You may want to test the new version when it becomes available.

 

[[6.9.2] Regression in "Incorrect (Annoying) Notifications About Disk Utilization" that was fixed in 6.9.0/6.91]

Further corrections are done on Unraid version 6.10, please test once available.

 

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

On 6/23/2021 at 12:23 AM, codefaux said:

but my logs include VLAN 0 references.

Perfectly normal when you enable VLANs for an interface.

VLAN 0 refers to the untagged communication.

[[6.9.2] SMART controller type: allow more than one disk]

I thought you were talking about individual disks.

 

With RAID the pool of disks is presented to Unraid as a single disk and it isn't possible to set disks individually.

 

[[6.9.1] Setting warning/critical temperature in SMART settings not possible]

The next version will have this fixed.

 

[[6.9.2] SMART controller type: Adaptec "disk index" range of 0...7 too short]

This will be fixed in the next version.

[[6.9.2] SMART controller type: allow more than one disk]

Individual disk settings are available when clicking on the device name on the Main page.

 

There is a bug in the settings savings, which will be corrected in the next version.

 

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

On 6/9/2021 at 6:55 PM, ryanhaver said:

 

I went this route and even created user defined bridge networks on a completely different NIC and still had the same issues. I suspect you'll see the issue resurface in a week or so, as this is exactly what happened to me. I have not tested using VLANs, but moved any containers needing their own IPs off of Unraid and haven't had issues for months.

 

When you use a different NIC, make sure that both bonding and bridging is OFF for this interface.

The docker custom network will be directly attached to the interface (e.g. eth1) and not the linux bridge function (br1).

 

[6.9.2 VM section webUI glitch]

The display of disk information is state aware.

This means when you open the display info, it stays open each time when you re-visit the VM page.

Simply close it again to keep it hidden.

 

Not a bug or glitch!

 

[[6.9.2] Fix for Unassigned Devices temperature notifications]

I should have been clearer.

This issue is solved in upcoming version 6.10

 

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

For Unraid version 6.10 I have replaced the Docker macvlan driver for the Docker ipvlan driver.

 

IPvlan is a new twist on the tried and true network virtualization technique. The Linux implementations are extremely lightweight because rather than using the traditional Linux bridge for isolation, they are associated to a Linux Ethernet interface or sub-interface to enforce separation between networks and connectivity to the physical network.

 

The end-user doesn't have to do anything special. At startup legacy networks are automatically removed and replaced by the new network approach. Please test once 6.10 becomes available. Internal testing looks very good so far.

 

[[6.9.2] Fix for Unassigned Devices temperature notifications]

Regular disks and unassigned disks are called separately in the monitor script

// check array devices
foreach ($disks as $disk) {
..
// process disk temperature notifications
  check_temp($disk,$text,$info);
..
}

// check unassigned devices
foreach ($devs as $dev) {
..
// process disk temperature notifications
  check_temp($dev,$text,$info);
..
}

 

[[6.7x +]Dashboard memory leak]

Until now every Unraid 6.x version relied on traditional polling of the server to update the GUI in real-time.

 

On the Dashboard there are multiple fields which are getting updated regularly. It is the task of the browser to initiate each time a poll request to obtain the new information and update the GUI accordingly.

Polling puts load on both the browser and server, and may consume more memory over time (depending on the browser).

 

Starting with Unraid version 6.10 the traditional polling mechanism is replaced by a websocket event driven model using Nchan.

 

An event driven model has a number of key advantages.

- It allows the server to send information when changes take place (better efficiency)

- Multiple clients can be served at the same time without huge impact on the server load (better scalability)

- A client only needs to act when new information is received (better responsiveness)

 

The event driven model also solves the issue of stale sessions when people open multiple browsers (on different computers) and forget to close them after usage. This resulted in csrf token mismatches when the server was restarted.

 

So far all testing with the event driven model looks very promising and a solid improvement!

 

[[6.9.2] can't save SMART notification Settings]

Thanks for reporting. This is fixed in the next release.

 

[[6.9.2] GUI Docker page layout error in advanced view when container repository name is very long]

Thanks for reporting. This is corrected in the next release.

 

[[6.x.x] rsyslog filters do not affect local syslog]

I've made the correction and moved the ruleset definition before the include.

 

Note

To make this work, the user has to delete the files /config/rsyslog.conf and /config/rsyslog.cfg from the USB device.

Reboot the server and reconfigure the syslog service in the GUI again.

 

[[6.9.2] Regression in "Incorrect (Annoying) Notifications About Disk Utilization" that was fixed in 6.9.0/6.91]

12 hours ago, interwebtech said:

Also I still don't have a "smart-one.cfg" in my /config folder. Be cool if someone could figure out what changed with 6.9.2 that brought all this back

 

It is correct that smart-one.cfg is not created when individual disk utilization levels are adjusted. Starting from 6.9 these levels are now stored in disk.cfg. Other variables, such as temperature levels, are still stored in smart-one.cfg.

 

I made an update to the (background) monitoring script to prevent false positives. In my testing this all looks okay.

 

[[6.9.1] Setting warning/critical temperature in SMART settings not possible]

Don't see that behavior, all disks are correctly saved.

 

[fresh 6.9.0 RC2 wont boot past "/bzroot...ok", fresh 6.8.3 boots fine]

You better open a new topic under General Support.

 

Usually this is the result of some incompatibility of your system with regards to USB2/USB3 and/or UEFI/legacy.

 

In addition, makes sure you run the latest BIOS version of your motherboard

[During rebuild the upgrade version / reboot after upgrade banners appear]

It is allowed to interrupt a running check and reboot, no harm done.

 

If it is wise to do, is another question

 

[[6.9.2] Regression in "Incorrect (Annoying) Notifications About Disk Utilization" that was fixed in 6.9.0/6.91]

53 minutes ago, interwebtech said:

Did as you suggested. The smart-one.cfg file does not reappear once applied. Is that a concern?

 

smart-one.cfg should be created as soon as you make a change for an individual disk.

In the new format smart-one.cfg should have the disk identifier as the section header. E.g

[KINGSTON_SA2000M81000G_50026B7683B40AB5]
hotTemp="50"
maxTemp="60"

 

This is working fine for me on 6.9.2 (only outstanding issue is when the identifier has a 'dot'  in the name)

 

[[6.9.2] Regression in "Incorrect (Annoying) Notifications About Disk Utilization" that was fixed in 6.9.0/6.91]

Delete the file smart-one.cfg and re-apply the settings.

[6.9.2 - Stale file handle on SMB shares]

When creating bug reports, please follow the guidelines

[[6.9.2] Regression in "Incorrect (Annoying) Notifications About Disk Utilization" that was fixed in 6.9.0/6.91]

28 minutes ago, interwebtech said:

Be able to MUTE these maybe on individual disk level.

 

Already possible. Just set a value of zero for warning and/or alert level.