Unraid OS version 6.12.4 available

[caplam]

i had unclean shutdown problems. I solved them by setting longer timing for vm and docker shutdown. If i remember correctly it was in 6.12.1 but not entirely sure.

Lastly in 6.12.3 i had no problem (but few reboots).

Attached is my diags. I think the server didn't reboot since the upgrade.

godzilla-diagnostics-20230905-1124.zip

[etsi]

After upgrade I had to change dockers with network type from bridge to host, otherwise it replaced with an 172.* ip address. Dockers with custom ip didn't change. Ipvlan is only for those with two network cards in bridge?

[ljm42]

@TheDon thanks for the diagnostics, but I moved your post to its own thread since it looks like it will take more back and forth than makes sense in a release thread:

 

 

[eggman9713]

Just a thing I noted when installing this update. When I was ready to update I clicked on the Update Now link in the banner on the main page rather than going to Tools > Update OS. That bypassed the required acknowledgement of the release notes that you had implemented recently. Probably should fix that.

[A05csta]

8 hours ago, caplam said:

i had unclean shutdown problems. I solved them by setting longer timing for vm and docker shutdown. If i remember correctly it was in 6.12.1 but not entirely sure.

Lastly in 6.12.3 i had no problem (but few reboots).

Attached is my diags. I think the server didn't reboot since the upgrade.

godzilla-diagnostics-20230905-1124.zip 254.06 kB · 0 downloads

I just upgraded and also got the Unclean shutdown message.

 

Details:

I always stop my docker containers first.  Then I stop the array.  The array did stop cleanly.

After the reboot, I got the Unclean shutdown message, however, the parity check did not start, and the parity says "valid".

[JorgeB]

6 minutes ago, A05csta said:

After the reboot, I got the Unclean shutdown message, however, the parity check did not start,

That possibly indicates a false message from the plugin, Unraid doesn't generate unclean shutdown notifications, it just starts a parity check.

[A05csta]

1 hour ago, JorgeB said:

That possibly indicates a false message from the plugin, Unraid doesn't generate unclean shutdown notifications, it just starts a parity check.

Thanks for pointing me in that direction.  I just found the Parity Check Tuning forum and this is a known issue, being worked on.

[ljm42]

2 hours ago, eggman9713 said:

Just a thing I noted when installing this update. When I was ready to update I clicked on the Update Now link in the banner on the main page rather than going to Tools > Update OS. That bypassed the required acknowledgement of the release notes that you had implemented recently. Probably should fix that.

 

Yeah, adding it to Tools > Update OS is just the first step. We'll deal with the banner in the future.

[ConnerVT]

Finally pulled the trigger, and updated from 6.10.3 to 6.12.4.  Everything went smoothly, but I had backed up, documented and shut down everything before updating.

 

All of my services/dockers are running without needing any adjustments, and all else looks good.  Thanks to everyone on the team for not accepting Good enough as an answer, and for finding solutions to the issues that the Unraid user base identified.

[craigr]

10 hours ago, ConnerVT said:

Finally pulled the trigger, and updated from 6.10.3 to 6.12.4.  Everything went smoothly, but I had backed up, documented and shut down everything before updating.

 

All of my services/dockers are running without needing any adjustments, and all else looks good.  Thanks to everyone on the team for not accepting Good enough as an answer, and for finding solutions to the issues that the Unraid user base identified.

 

Did you power down or do a restart?  Just wondering if your system crashed or if you even tempted fate?

[Jaxah]

I just went to upgrade today from 6.11.5 to 6.12.4, but as my usb drive was only a 1gb when I installed it many moons ago, I got an error:
 

Quote

boot device shows 222715904 free but upgrade needs 441156311

 

So, I guess it's time to upgrade the usb drive to something larger, but if I remember correctly, the install of unraid is tied to the usb drive - can someone point me to the docs or steps for upgrading your usb drive?

 

[JorgeB]

3 minutes ago, Jaxah said:

can someone point me to the docs or steps for upgrading your usb drive?

https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#why-replace-your-usb-flash-boot-device

[itimpi]

13 minutes ago, Jaxah said:

I just went to upgrade today from 6.11.5 to 6.12.4, but as my usb drive was only a 1gb when I installed it many moons ago, I got an error:
 

 

So, I guess it's time to upgrade the usb drive to something larger, but if I remember correctly, the install of unraid is tied to the usb drive - can someone point me to the docs or steps for upgrading your usb drive?

 

 

I think that you could also use the Manual upgrade method (although it is getting a bit tight with a 1GB flash drive).

[ConnerVT]

6 hours ago, craigr said:

16 hours ago, ConnerVT said:

Finally pulled the trigger, and updated from 6.10.3 to 6.12.4.  Everything went smoothly, but I had backed up, documented and shut down everything before updating.

 

All of my services/dockers are running without needing any adjustments, and all else looks good.  Thanks to everyone on the team for not accepting Good enough as an answer, and for finding solutions to the issues that the Unraid user base identified.

 

Did you power down or do a restart?  Just wondering if your system crashed or if you even tempted fate?

 

I did a reboot in this case.  It was my original server (now the backup NAS) that was where I was always having this issue.  I figured I would try a reboot on the main server when I updated, to see if it behaved or not  (Spoiler Alert - It behaved).  That server was at over 7 months uptime, doesn't get stopped very often.

[sjoerd]

Hey  Team,

 

Thanks for the new release - Update got applied without issues (never having issues upgrading to stable releases)

 

I was hoping on the "take snapshot" feature on the VMS page. I miss this so much. I tried to create them using the terminal but failed

[Ether Wrangler]

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

[-C-]

On 9/5/2023 at 8:25 PM, ljm42 said:

 

Yeah, adding it to Tools > Update OS is just the first step. We'll deal with the banner in the future.

What about linking the banner to Tools > Update OS, at least as an interim solution?

[meep]

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).

 

Now all my shares have disappeared, meaning more hours of debugging  and faffing around.

 

What's happened unRAID? I've used it for years and it's been rock solid. Now nothing but issues and problems and hassle????

 

 

[JorgeB]

8 hours ago, meep said:

Now all my shares have disappeared,

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

[Zonediver]

12 hours ago, meep said:

What's happened unRAID? I've used it for years and it's been rock solid. Now nothing but issues and problems and hassle????

 

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

Some more infos...

Edited September 10 by Zonediver

[wgstarks]

Macvlan call traces continue in 6.12.4. Started a bug report here.

Edited September 10 by wgstarks
typo

[JorgeB]

16 hours ago, wgstarks said:

Macvlan call traces continue in 6.12.4.

Those can still happen if you still use macvlan with bridging, either use ipvlan, or if you really require macvlan disable bridging, see the release notes.

[wgstarks]

1 hour ago, JorgeB said:

Those can still happen if you still use macvlan with bridging, either use ipvlan, or if you really require macvlan disable bridging, see the release notes.

Thanks. Yes, that was pointed out in the bug report thread.

[CiscoCoreX]

5 hours ago, JorgeB said:

Those can still happen if you still use macvlan with bridging, either use ipvlan, or if you really require macvlan disable bridging, see the release notes.

This going to be a problem for me. I'm running VM's on my unraid with Network Source: br0. So I can give every VM a static ip address.  So I can RDP to my Windows 10 VM. So how do I gonna resolve this with bridging disable?

 

My win 10 vm:

Edited September 11 by CiscoCoreX

[JorgeB]

18 minutes ago, CiscoCoreX said:

This going to be a problem for me. I'm running VM's on my unraid with Network Source: br0

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