I don't know if this is still required, but I always Stop all dockers, go to settings and disable Docker, and then upgrade.  Once upgraded, turn Docker  back on in settings.  Works well for me and I have not had any Docker issues regarding upgrades since.  Yes, Dockers must be updated prior as well.  I use the Update Assistant checks all of those things.  I also check for plugin updates prior and backup flash drive.

 

14 hours ago, itimpi said:

Your screenshots shows you have it set to show the current read/write activity speeds - not the count.    You can toggle it to count via the icon on the upper write of the Main tab.

 

Thanks! That was the trick.

Thanks to the maintainer for the work.

 

After updating and after first reboot there was no network - eth0 was disappeared. After second reboot everything was okay. 

I've updated two of my unRAID systems to 7.0.1. This time, though, I did not uninstall the RTL8125 Drivers plugin prior to the update. And the two systems came back up with 2.5GbE network access working. I'll try two more tonight to see if they also come back up with network access.

 

The next two unRAID systems I updated worked the same as the first two.

 

I updated two more systems, and they worked just like the first four.

Edited March 4, 20251 yr by aaronwt

I got this error after updating to 7.0.1 from 6.12.x i have never seen this error in the past

 

Mar 6 13:03:36 Unraid kernel: mce: [Hardware Error]: Machine check events logged 
Mar 6 13:03:36 Unraid kernel: mce: [Hardware Error]: CPU 23: Machine Check: 0 Bank 5: bea0000000000108 
Mar 6 13:03:36 Unraid kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffffa087075e MISC d012000100000000 SYND 4d000000 IPID 500b000000000 
Mar 6 13:03:36 Unraid kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1741262594 SOCKET 0 APIC 1d microcode 8701034

 

Any help please?

unraid-diagnostics-20250306-1620.zip

Edited March 6, 20251 yr by L0rdRaiden

27 minutes ago, L0rdRaiden said:

I got this error after updating to 7.0.1 from 6.12.x i have never seen this error in the past

 

Mar 6 13:03:36 Unraid kernel: mce: [Hardware Error]: Machine check events logged 
Mar 6 13:03:36 Unraid kernel: mce: [Hardware Error]: CPU 23: Machine Check: 0 Bank 5: bea0000000000108 
Mar 6 13:03:36 Unraid kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffffa087075e MISC d012000100000000 SYND 4d000000 IPID 500b000000000 
Mar 6 13:03:36 Unraid kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1741262594 SOCKET 0 APIC 1d microcode 8701034

 

Any help please?

unraid-diagnostics-20250306-1620.zip 153 kB · 0 downloads

Its from the microcode on the CPU being updated.  Safe to ignore

This is a new message that I keep seeing in the log every few minutes since I upgraded from 7.0.0 to 7.0.1 

 

Mar 8 11:20:30 Tower nginx: 2025/03/08 11:20:30 [error] 9719#9719: *472 limiting requests, excess: 20.369 by zone "authlimit", client: 192.168.1.27, server: , request: "PROPFIND /login HTTP/1.1", host: "192.168.1.200"  

 

Do I need to be concerned with this as I never saw this before

On 3/6/2025 at 4:52 PM, Squid said:

Its from the microcode on the CPU being updated.  Safe to ignore

I got an unexpected freeze/reboot could be because of this?

Successfully upgraded from 6.12.15 to 7.0.1.

There was a slight issue I faced during the upgrade, and that is due to the fact that I had manually amended the `/etc/rc.d/rc.docker` file prior to the upgrade. Do take note of this if you had also amended some system files like I did.

 

 

On 3/8/2025 at 1:53 PM, L0rdRaiden said:

I got an unexpected freeze/reboot could be because of this?

The mce appeared to me to come from the microcode update.  Unlikely it's related to any crash of your system

Just updated from 6.12.14 to 7.0.1. Before I did flash backup and stopped array. Everything went smooth. 

Getting consistent crashes every hour or so since upgrading from 7.0.0 to 7.0.1.

 

7.0.0 was rock solid, rolling back now.

You might want to post your diag file while on 7.0.1 if you are looking for help

Edited April 12, 20251 yr by optiman

@XCVB

8 minutes ago, optiman said:

You might want to post your diag file while on 7.0.1 if you are looking for help

Or if you just want to help us try to figure out why it wasn't working for you. It might not be fixed for you in future versions if we have no information about what happened for you.

Updated a couple of days ago from 7.0.0.  Everything went well.  The problem I had, that was introduced in 7.0.0, where several drives refused to spin down after 30 min (my default setting) is no more.  Not sure why it happened or why this update fixed it, but my thanks to the team. 

I read some had read/write speeds after going on 7.x.x. Is that something to worry about or?

 

https://www.reddit.com/r/unRAID/comments/1i56na7/help_unraid_v70_slow_write_speeds/

 

Thanks!

16 minutes ago, DanielPT said:

Is that something to worry about

No.

@optiman@trurl thanks very much to you both for the offer to help. Seems a reboot triggered some sort of hardware issue. 7.0.0, 7.0.1 and 7.1.0-rc1 all crash now. Currently still on 7.1.0.

 

I'll make a separate topic and tag you there.

3 minutes ago, XCVB said:

Currently still on 7.1.0.

Not released yet as of that post. What version are you on?

24 minutes ago, trurl said:

Not released yet as of that post. What version are you on?

7.1.0-rc1, I was lazy and dropped the "-rc1" 😀