Unraid OS version 6.12.4 available

[CiscoCoreX]

18 minutes ago, JorgeB said:

See the release notes, with v6.12.4 you don't need bridging to run VMs.

I'm gonna give 6.12.4 another shoot later. First time I run into some problems, i have posted in the bug reports. So I had to revert back to 6.12.3.

[nka]

On 9/9/2023 at 6:56 PM, meep said:

updated to 6.12.4 as 6.12.3 was hard crashing every few days. (6.12.2 before it lost me days tracking down some kind of plugin corruption).

Does 6.12.4 still crashing? I reverted back to 6.11.5 because 6.12.2 was freezing all the time.

[ConnerVT]

9 hours ago, JorgeB said:

See the release notes, with v6.12.4 you don't need bridging to run VMs.

 

Correct, you don't need bridging to run a VM.  But the question here is (which will help the person you replied to as well as myself):

 

With 6.12.4, macvlan, and no bridging, how do you access the VM from outside of the Unraid dash board? 

 

There does not seem to be an identifiable IP address which can be seen on the same subnet which the LAN network is configured (192.168.122.0/24 vs 192.168.1.0/24 for the LAN). 

[ljm42]

9 minutes ago, ConnerVT said:

Correct, you don't need bridging to run a VM.  But the question here is (which will help the person you replied to as well as myself):

 

With 6.12.4, macvlan, and no bridging, how do you access the VM from outside of the Unraid dash board? 

 

There does not seem to be an identifiable IP address which can be seen on the same subnet which the LAN network is configured (192.168.122.0/24 vs 192.168.1.0/24 for the LAN). 

 

As far as the VM is concerned, it works exactly the same whether it is on the bridge network or the macvtap network.

 

The VM template assigns the VM a mac address, and the VM can use that to get a DHCP address from the router, or the VM can assign itself a static IP. Unraid is not and has never been directly involved in the IP assignment for a VM.

 

As mentioned in the release notes, make sure the VM template is set to vhost0 and not br0.  And make sure Host access to custom networks is enabled (assuming you want that)

[ljm42]

6 hours ago, nka said:

Does 6.12.4 still crashing? I reverted back to 6.11.5 because 6.12.2 was freezing all the time.

 

Fixes for call traces and crashes related to macvlan are the main reason for this release. A config change is needed, you'll want to read the release notes for details.

[nka]

12 hours ago, ljm42 said:

 

Fixes for call traces and crashes related to macvlan are the main reason for this release. A config change is needed, you'll want to read the release notes for details.

Not sure mine were releated to macvlan, but I'll try again.

[meep]

On 9/10/2023 at 8:52 AM, JorgeB said:

This is not a common or known issue, you should start a new thread on the general support forum and post the diagnostics. 

 

On 9/10/2023 at 12:20 PM, Zonediver said:

 

Maybe a hardware-problem? Cache-SSD? New? Old?

Some more infos...

 

On 9/11/2023 at 5:52 PM, nka said:

Does 6.12.4 still crashing? I reverted back to 6.11.5 because 6.12.2 was freezing all the time.

 

Shares came back after a reboot, but significant issues persist.

 

I've made an issue thread. 6.12.4 is crashing much more frequently, than 6.12.3 was (hourly rather than daily). 
 

 

Edited September 13 by meep
clarification

[Ether Wrangler]

On 9/8/2023 at 5:26 PM, Ether Wrangler said:

 

I'm still getting what appear to be macvlan call traces after applying this.  The odd thing is, I set the network type to ipvlan in 6.12.3 and if I check the docker networks there isn't even a macvlan network.

 

NETWORK ID     NAME       DRIVER    SCOPE
68ad20afc8e2   bridge     bridge    local
a7904065acfc   host       host      local
85c9f1a91a4e   none       null      local
a66a6a6c0090   proxynet   bridge    local

 

tower-diagnostics-20230908-1718.zip 149.46 kB · 1 download

 

 

I think I finally got this fixed.  I'm still not sure why I was getting the traces with no macvlan docker networks, but I saw the comment about disabling bridging as its not needed anymore with the macvtap  device that will be created.  I turned off bridging on the NIC and have made it 2 days with no traces.  Before this I was getting multiple every day with hard locks of the OS at least every 2 days.

Edited September 13 by Ether Wrangler

[nka]

I just want to say that I've upgrade to 6.12.4 from 6.11.5 and it has been stable for me (6.12.2 was freezing every day, I do have 1 days and 6 hours now).

 

Processus was :

- Take note of all IP of Dockers using br0 (already have them, but just in case).

- Disable Dockers.

- Disable Network Bridge in Network Setting.

- Back to Dockers settings to change from macvlan to ipvlan.

- Enable Docker (and let them start).

- Update all br0 dockers to eth0 (or VLAN) and set old IP again.

- Disable Docker.

- Update to 6.12.4.

- Reboot.

- Enable Docker.

 

Thanks!

[ljm42]

5 hours ago, nka said:

I just want to say that I've upgrade to 6.12.4 from 6.11.5 and it has been stable for me (6.12.2 was freezing every day, I do have 1 days and 6 hours now).

 

Processus was :

- Take note of all IP of Dockers using br0 (already have them, but just in case).

- Disable Dockers.

- Disable Network Bridge in Network Setting.

- Back to Dockers settings to change from macvlan to ipvlan.

- Enable Docker (and let them start).

- Update all br0 dockers to eth0 (or VLAN) and set old IP again.

- Disable Docker.

- Update to 6.12.4.

- Reboot.

- Enable Docker.

 

Thanks!

 

Glad you are up and running! One thing I will say for anyone following along, I'd recommend updating to 6.12.4 first, before making any changes to the Docker config. The new settings have no effect on older releases so there is no added value in changing things before upgrading.

 

Also, if your goal is to use IPVLAN then don't disable bridging. When you disable bridging the system uses a macvtap network with macvlan, which was the main reason for the 6.12.4 release : ) 

[Rommel]

Updated today and I noticed that GPU Stats plugin use to detect my Arc A750 on 6.12.3, however on 6.12.4 it can only detect my Intel iGPU.

[CiscoCoreX]

1 hour ago, Rommel said:

Updated today and I noticed that GPU Stats plugin use to detect my Arc A750 on 6.12.3, however on 6.12.4 it can only detect my Intel iGPU.

Make sure you have booth GPU selected in the GPU Statistics.
 

 

In the Dashboard: