[Unraid OS version 6.12.0-rc6 available]

4 hours ago, luzfcb said:

Hello, I'm learning how VPN works with Unraind and I would like to know if there's any way to undo any configuration I've done in VPN Manager in order to get it back to the default initial configuration.
I missed a delete button or something. If the button exists, I couldn't find it instinctively.

 

Toggle from BASIC to ADVANCED on the grey bar corresponding to the Tunnel you want to remove, a DELETE TUNNEL option will appear.

[Unraid OS version 6.12.0-rc5 available]

15 hours ago, scot said:

Third: ZFS is using logical drives as part of its assignment.  it is MUCH safer to use disk-by-id to assign drive info.  (so a device hw GUID vs /dev/sba) so then if you remove a drive and put it back it ALWAYS gets the correct information and it is easier to deal with failures etc. 

 

            sdf1    ONLINE       0     0     0
            sdg1    ONLINE       0     0     0
  VS:

ata-Hitachi_HDS722020ALA330_[..] ONLINE 0 0 0

ata-Hitachi_HDS722020ALA330_[..] ONLINE 0 0 0

Not played with ZFS on Unraid yet, but this doesn't sound right, Unraid has always used disk-by-id for assignments for the reasons stated.
Possibly some ambiguity caused by how the information is presented? 

[Unraid OS version 6.12.0-rc2 available]

3 hours ago, mattalat said:

Searched through all the comments and couldn't find an answer - also I apologize if this is a dumb question. What does the autotrim feature do? How is it different from scheduling trim?

Instead of garbage collection happening on a schedule, e.g. once a day, it happens as soon as possible.

[6.12 Dashboard formatting and buggy UI]

Seen the same with the UI, I'm fairly certain the cause is 3rd party plugins that need to be updated, in this case the plex streams plugin.

[unRAID 6.12-beta6 - Array Won't Start]

1 hour ago, xaositek said:

 

There is another branch beyond Stable and Next called Test.

Test only appears if you install a specific plugin that adds that development branch, or if you directly installed from the test branch (which it looks like you have - no previous installs).

[Samsung 980 temp wrong]

Its a Samsung hardware problem, you can either add the kernel arg to bandaid fix the problem, or update the nvme's firmware to fix at the source.

Both solutions are detailed in the linked thread.

[Samsung 980 temp wrong]

If your problem is incorrect temp reporting, which is specific to the newer samsung nvme devices like the 980, this thread from 6 months ago has a fix.

 

But are you sure you don't simply need to change the temp warning ranges for your nvme?

The default temp ranges are 45-55C for all storage devices in Unraid, which is too low for nvme and will definitely trigger warnings when under a reasonable load.

 

I usually change this for my nvme devices to 55-65C (which is still a bit below spec for most nvmes) and rarely get temp warnings. This change can be done by clicking on the device name (e.g. Cache, Cache 2), from the MAIN tab

[UPS alert notification severity level]

Changed Status to Solved

[UPS alert notification severity level]

While running 6.11.1 I noticed this change has been implemented

Thank you!

[Unraid OS version 6.11.0-rc1 available]

well I messed up that original reply somehow... sorry mods

 

46 minutes ago, tombunraider said:

I saw that v6.11.0-rc2 is released now, but there's currently no changelog or thread.

 

There is always a cumulative changelog available through the Unraid GUI
 

[[[6.10.3] Experienced 2 crashes since upgrade to 6.10.x]

I can see some iptable call traces. 

I saw similar after moving from a solid 6.9.2 to 6.10.x, where I was seeing random crashes during btrfs balance/scrubs.

Try stopping your docker services (setting > docker >  enable docker > no)  and setting Docker custom network type to ipvlan (from macvlan).

For me, that fixed those call traces that locked up my server.

[[6.10.2] Holding the (CTRL) key and clicking on things don't open them on a new tap in the browser.]

Less convenient, but right-click open link in new tab still works

 

You might also need to check your ad/popup blocker settings to ensure Unraid is still whitelisted, although the behavior has changed to make it not useful, CTRL click should still work.

[Documentation wrong/unclear regarding DNS rebinding - unraid.net OR myunraid.net]

Domain has moved to a new schema as of 6.10, see release notes below.

Documentation just hasn't caught up yet. @ljm42 

 

https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0

[[6.10.0] Unraid boot device not found]

Possible regression introduced in 6.10.1 for a user

 

[Never-ending notifications]

Refresh the page and it goes away permanently (after clicking close all).

It is a bug that I don't remember being present in rc8

[Unraid OS version 6.10.0-rc8 available]

Easy upgrade from rc7

[Unraid OS version 6.10.0-rc5 available]

I like the new font, scaling now seems inline with other fonts on the page

 

Dark mode = 6.9.2

 

Light mode = 6.10.0-rc7 with new font

[6.10 rc6 & 7 Sleep Mode issue]

I've not had any issues with sleep (just tested again on rc7), but I use WOL to bring the server back up and not the actual power button.

[Unraid OS version 6.10.0-rc7 available]

4 minutes ago, JorgeB said:

Having a second vfs object "fixed" the problem because apparently Unraid only loads the last one, so basically wasn't loading "vfs objects = btrfs", on a related note if I needed to set two or more vfs objects for one share how could I do that?

vfs objects = vfs_object_1 vfs_object_2

Pretty sure that's how you're meant to do it

[Unraid OS version 6.10.0-rc7 available]

No dramas today with upgrades rc5 -> rc6 -> rc7

[[6.10.0-rc5] - VM Manager service silently fails to stop]

Changed Status to Solved

[[6.10.0-rc5] - VM Manager service silently fails to stop]

Tested both with no VMs defined, and with 1 VM defined.

In both cases the issue is resolved in 6.10.0-rc6, thanks!

[[6.10.0-rc4] OpenSSL vulnerability (again) CVE-2022-0778]

Changed Status to Solved

[[6.10.0-rc4] OpenSSL vulnerability (again) CVE-2022-0778]

rc5 onwards has resolved this

root@tower:~# uname -r
5.15.37-Unraid

root@tower:~# openssl
OpenSSL> version
OpenSSL 1.1.1n  15 Mar 2022

 

[Unraid OS version 6.10.0-rc6 available]

One quirk compared to normal updates/restarts was that the GUI never recovered and needed a manual refresh, with nginx throwing a 503 error.  Not the end of the world, but I thought I'd mention it.

 

Other than that, flawless upgrade.