Upgraded to 7.0 stable from 6.12.14 without issue.

 

Most tedious part was reinstalling all the docker containers after switching to overlay2.

 

Might help others--when I deleted the existing docker folder, I didn't realize that would nuke my docker network. After a few reinstalls of containers I noticed they had no network assigned. Once I created the same docker network name, all the containers from that point on were assigned to the correct (previously-assigned) docker network.

 

Really impressed how smooth this went overall! Great job, unraid team!

Can confirm very smooth upgrade. 

I caved in from curiosity last week and installed 7 rc2 up from 6.12.10 (stayed away from the later versions when I saw complaints of network issues etc.), those installs went perfectly fine on both of my server instances.

 

Saw the final released and upgraded 2 days ago; similar experience perfectly smooth upgrade and install.

 

However, I did have a false positive SMART report on one of my HGST drives of it failing from low helium values. This came through via a Discord notification. However, upon inspecting the error I noticed it had completely gone away so I'm unsure what this little blip was. Nothing in the logs or the actual SMART reporting page. Drive is perfectly fine and is still at 100% helium value.

Updated from 6.1.2.14 , all good  no issues 

Upgraded my 3 Servers from .6.12.14 to 7.0.0 without any issues.   Even though during the first upgrade to 7, I was slightly worried but no issues.   I do have 1 question about the VM snapshot, where is the snapshot being saved and how can I see how big it is?

3 minutes ago, GeorgeJetson20 said:

Upgraded my 3 Servers from .6.12.14 to 7.0.0 without any issues.   Even though during the first upgrade to 7, I was slightly worried but no issues.   I do have 1 question about the VM snapshot, where is the snapshot being saved and how can I see how big it is?

Saved in the same folder as the image. It is an overlay file so will only have changes to the main image. Both are required for the VM to function if the VM is running and you look at the xml you will see the backing file.

 

If the VM is active it could also save ram contents. XML is also save in VM dir and nvram if uefi in the libvirt location.

Thanks for the info, didn't see that in the release notes

Any special concerns going from 6.9.2 to

this release?  I know, I’m very behind…

Successful update my HP Proliant Gen8 from 6.12.12 to 7.0.0

Thanks !

10 hours ago, 01111000 said:

Any special concerns going from 6.9.2 to

this release?  I know, I’m very behind…

Should be fine, make a flash backup before upgrading and would be good to read the release notes for all major releases, 6.10.0, 6.11.0, etc.

It's a smooth upgrade from 6.12.13 to 7.0.0, all good, thanks🥰

But do I need to click the "upgrade pool" button? What changes will occur after upgrading?

13 minutes ago, neoherozzz said:

But do I need to click the "upgrade pool" button?

You don't need to, and if you upgrade you cannot downgrade back to v6.12

 

13 minutes ago, neoherozzz said:

What changes will occur after upgrading?

It will enable the new zfs features that came out it openZFS 2.2, like block cloning for example.

29 minutes ago, JorgeB said:

You don't need to, and if you upgrade you cannot downgrade back to v6.12

 

It will enable the new zfs features that came out it openZFS 2.2, like block cloning for example.

 

I can't find information about what exactly version of OpenZFS is used in Unraid 7?

It is 2.2.7?

Completed the upgrade tonight, 6.12.14 -> 7.0.0, went really well, no issues.

 

I must admit I was gonna hold off for a little while more, just something I do for new major releases. I was reading the release notes for 7.0.0 and I noticed a bit in there about a potential fix for memory pressure causing the OS Files to be pushed from memory.

 

Tonight I was again having UI performance issues (on 6.12.14) that I have been tracking down for months now, that appeared to be memory related but memtest ran clear and available memory (HTOP) showed at least 6GB available (32GB total).

 

This evening I confirmed I was seeing constant reads from the flash drive at the same time as these issues, over 10 million reads reported in the UI, and seeing 20-30MB's, so decided to jump into the upgrade and give this potential solution a crack. Will report back if this seemingly has helped.

Obviously if memory is running out, then adding more is the real solution, but having the OS files always in memory seems fair, and I don't understand why HTOP shows available memory if its that full. Maybe the pressure threshold is lower than I expected?

2 minutes ago, jaclas said:

 

I can't find information about what exactly version of OpenZFS is used in Unraid 7?

It is 2.2.7?

@jaclas 
My system shows the below in the system logs, so I would say yes
 

kernel: ZFS: Loaded module v2.2.7-1, ZFS pool version 5000, ZFS filesystem version 5

 

4 minutes ago, jaclas said:

I can't find information about what exactly version of OpenZFS is used in Unraid 7?

In the release notes right at the very bottom.

zfs: version 2.2.7_6.6.68_Unraid

 

Same here, just upgraded Saturday, everything seems to be fine.

 

The only issue I got was with the nvme pool used for Dokcer/img. Just have to delete / recreate this one, and the array finally starts.

Completed the upgrade to 7.0.0 from 6.12.14, went well, so far no issues. Thanks!

Upgrading from 6.12.10 to 7. 12700K | Asus Pro WS W680-ACE IPMI | 4060

I'm watching the upgrade through the IPMI and this part keeps looping. 30~ minutes so far.

Would someone be able to point me in the correct direction? Thanks!

23 minutes ago, kevin.atlee said:

Upgrading from 6.12.10 to 7. 12700K | Asus Pro WS W680-ACE IPMI | 4060

I'm watching the upgrade through the IPMI and this part keeps looping. 30~ minutes so far.

Would someone be able to point me in the correct direction? Thanks!

Please create a new thread in the general support forum, but I would start by recreating the flash drive:

 

First backup the current one, then recreate it using the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files.

On 1/10/2025 at 9:10 AM, JorgeB said:

A few users are seeing a "Wrong Pool State, invalid expansion" or "Wrong pool State. Too many wrong or missing devices" error after upgrading, they are caused by different reasons.

 

For "Wrong Pool State, invalid expansion", this usually means that the pool had an incorrect cfg file, but v6.12 didn't check or care about it, you can easily resolve the issue by just letting v7 re-import the pool, to do that:

 

• on main, click on that pool and then "Remove Pool"
• back on main, create a new pool with the same name and number of slots
• assign the pool device(s), leave the filesystem set to auto
• start the array to import the pool

 

For "Wrong pool State. Too many wrong or missing devices", Unraid v7 no longer supports pools without any assigned devices, you just need to click on the pool and then "Remove Pool", or set the pool slots to 0.

 

 

I did the upgrade to 7.0.0 (from 6.12.14) and it seemed to go well. I got the message 'Wrong pool State. Too many wrong or missing devices', but fixed it as described by using the 'Remove Pool' function (because I do not have a separate drive for a 'cache' pool, only have an 'Array' drive). The server runs smooth without any issues, however after a couple of hours the user interface is no longer available. Also the Docker containers no longer work (e.g. my Home Assistant is no longer available, and the Zigbee2MQTT devices also not). I need to do a hard reset of the server (by holding the Power Button until it is powered off). After I boot again, the server runs smooth, but again after a couple of hours I get the same issue. I don't know how to find the cause, I scrolled to the 'syslog-previous' (see attached), but cannot find the cause. Can someone help to solve / identify the issue? I didn't have any issues with 6.12.14 so it seemed to be related to the upgrade to 7.0.0. Thank you for your help.

syslog-previous.txt

6 minutes ago, pedro1989 said:

Can someone help to solve / identify the issue? I didn't have any issues with 6.12.14 so it seemed to be related to the upgrade to 7.0.0. Thank you for your help.

Please start a new thread in the general support forum and post the complete diagnostics.

I am not seeing a way to upgrade my ZFS pool and cache (not array). I have two NVMe mirrored and two SATA SSD mirrored using the 6.12.x version of ZFS, but when I search for upgrade this is what I find. I cannot select any disks.

 

So I'm not sure what the steps are to upgrade my ZFS version.

7 minutes ago, talonserver said:

I am not seeing a way to upgrade my ZFS pool and cache (not array). I have two NVMe mirrored and two SATA SSD mirrored using the 6.12.x version of ZFS, but when I search for upgrade this is what I find. I cannot select any disks.

 

So I'm not sure what the steps are to upgrade my ZFS version.

 

in terminal what is the output of 

zpool status

 

if it can be updated it will say so there... IF yes. then run the command manual...
 

zpool upgrade <poolname>

Replace pool name with info of pool to be upgraded...

 

it may have already been upgraded or unneeded...

Thanks, I can do it that way I guess, but the FAQ mentioned a button. It would be helpful to know where that is or at least what it looks like as I prefer to do these sorts of things per the manual.

 

ie "A button will appear letting you upgrade a pool to support the new ZFS features"

3 minutes ago, talonserver said:

It would be helpful to know where that is

Click the pool name.