This is a security and bug fix release. It includes all the patches that were made available for 7.0.0. 

 

This resolves a security issue when the Tailscale integration is enabled on a container running in Host mode and then shared with other users. 

 

Please see the release notes for all the details.

 

This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic under General Support. Be sure to include your diagnostics.zip.

 

Upgrade steps for this release

1. As always, prior to upgrading, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

2. Read the release notes.

3. Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular.
4. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type:

   umount /var/lib/docker

   The array should now stop successfully

5. If you have a recent release or Unraid Connect installed
   1. Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post
6. If you are on an earlier version
   1. Go to Tools -> Update OS and switch to the "Stable" branch if needed. If the update doesn't show, click "Check for Updates"
7. Wait for the update to download and install
8. If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. 
9. Reboot

 

This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic under General Support. Be sure to include your diagnostics.zip.
 

Thanks to everyone involved for the effort 🙂 

boot device shows 458711040 free but upgrade needs 720810792
plugin: run failed: '/bin/bash' returned 1
Executing hook script: post_plugin_checks

 

Perhapts the Update should have noted the USB Freespace Requirement before i eargerly clicked on the Update Button? Now here's to me trying to figure out how to replace the USB Drive. :)

mover
  - mover was not moving shares with spaces in the name from array to pool
  - mover was not handling hard links properly

 

Seen this in the release notes. Wasn't aware of any mover issues. Is the problem fixed or do we have to do something? Unraid hasn't given me any errors so I'm assuming I'm not affected by it.

7.0.0 to 7.0.1 upgraded, no issues to report.

 

Great job team!

Quote

Docker: hide the update status for containers managed by 3rd parties

 

I'm curious about what this means and what actions we will need to take to keep up to date on our Dockers?   Also, aren't virtually all of the dockers in Community Apps managed by 3rd parties i.e. not Lime Tech?

7 minutes ago, Griz said:

 

I'm curious about what this means and what actions we will need to take to keep up to date on our Dockers?   Also, aren't virtually all of the dockers in Community Apps managed by 3rd parties i.e. not Lime Tech?

If you are using containers from the CA App you are not affected by this change.

 

This only affect users who are running containers managed by anything else than dockerMan (which Unraid uses to under the hood manage Docker containers) so to speak the Docker Compose plugin, Portainer or any other 3rd party Docker managing solution.

13 minutes ago, Griz said:

 

I'm curious about what this means and what actions we will need to take to keep up to date on our Dockers?   Also, aren't virtually all of the dockers in Community Apps managed by 3rd parties i.e. not Lime Tech?

Whats more the reason for this change is that 3rd party container managers (which is what this refers to rather than 3rd party containers) dont integrate with unRAIDs container status tracking thus the update status was virtually always wrong.

Thanks, I understand what ya'll are saying about "why", but I'm still not sure what this change means to me    It will probably become clear when I try 7.0.1. 

 

I do have one docker (NextPVR) that I installed by dropping a template into /config/plugins/dockerMan/templates-user then clicking "Add Container" on the UnRaid Docker page...  Not using any of the "managers" mentioned.   

 

Edit: Upon reflection, I am guessing that means I am still using dockerMan and will not notice any change even though NextPVR is not in CA.

Edited February 26, 20251 yr by Griz

1 minute ago, Griz said:

but I'm still not sure what this change means to me

If you‘ve deployed your containers through the CA App or even deployed a container which is not in CA through the Unraid WebUI (which you did) then nothing is changing because Unraid is still managing the containers.

1 hour ago, tuxbass said:

Is the problem fixed or do we have to do something?

It's fixed, those issues were with 7.0.0

Just now, JorgeB said:

It's fixed, those issues were with 7.0.0

What about some users reporting mover failure creating dupes? Non-issue and users should ignore those comments?

Just now, tuxbass said:

What about some users reporting mover failure creating dupes?

Not aware of that issue, if someone is seeing it, they should create a bug report.

2 minutes ago, JorgeB said:

Not aware of that issue, if someone is seeing it, they should create a bug report.

That's good to hear. I was referring to this report: 

 

58 minutes ago, tuxbass said:

That's good to hear. I was referring to this report: 

That one is resolved as mentioned:

 

2 hours ago, tuxbass said:

mover was not handling hard links properly

 

Resolved as in further mover runs are OK. But should users look out for broken links and fix 'em manually?

1 minute ago, tuxbass said:

But should users look out for broken links and fix 'em manually?

It won't fix any previously broken links, but that should basically only affect users who are using most free as the allocation mode, since the issue only happened when the mover tried to send a file and its hardlink(s) to different array disks, anyone using highwater with and most free most likely wasn't affected, but still good to check.

2 minutes ago, JorgeB said:

anyone using highwater with and most free most likely wasn't affected, but still good to check.

Good to know. Any idea as to why release notes made no mention of it nor why this issue isn't documented under 7.0.0 known issues?

Reddit reccomended using tools such as Czkawka to search for duplicates. Are there any (semi-)official steps users should take to see whether they are affected and how to fix the problems? It's still a bit puzzling that unraid makes zero attempt at informing users about this.

Great work!  Upgraded last night and all is well.

Quote

 

 

After upgrade not showing any disk read/writes

3 minutes ago, fre4ki said:

After upgrade not showing any disk read/writes

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.

 

I would like to move from 6.12.15 directly to 7.0.1.

 

I don't have ZFS Pools (only xfs file- and btrfs nvme cache pool), neither do i have a realtek nic.

 

Shouldn't be a problem, does it?

 

Thanks in advance!

2 minutes ago, UsAs said:

Shouldn't be a problem

Make sure you have a flash backup and read the release notes.

5 minutes ago, trurl said:

Make sure you have a flash backup and read the release notes.

And your plugins are up-to-date

Everything worked like a charme, thanks for your help!