Just upgraded to version 7.0.0 and my array does not start and I get this error message:

 

It was working just fine before the upgrade. What could possibly be wrong? How can I fix it?

diagnostics-20250110-0026.zip

Cache cfg is wrong, it's a single device but using the raid1 profile, previous release didn't check that, you can just reimport the pool to fix it:

 

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

 

i have the same error, i have no "remove pool" button

 

 

Edited January 10, 20251 yr by neo404

8 minutes ago, neo404 said:

i have the same error but im not sure if we are facing the same issue,

If it's the same error you can do that, should resolve the issue, and if it doesn't, it won't do any damage.

 

If it doesn't work, then post the diagnostics.

hi jorgeb,

 

thanks for trying to help, attached is my diagnostics log

tower-diagnostics-20250110-1712.zip

31 minutes ago, neo404 said:

attached is my diagnostics log

Looks like the same issues, do the steps above, it should resolve it.

but i had 2x nvmes in raid1 for cache`?

ok it worked, thanks for your assistance!

I too got this start up error after updating to Unraid V7.0.0 from V6.12.14.I followed the instructions steps given in the post above but after removing the pool name "cache" and re-adding it, there was no devices to assign to it. All I got were blanks. unassigned. Trying to restart the shares gave the same error.

So what I did out of pure luck and chance was this:

I removed the pool named "cache" and did not add it back.

Then I just clicked "Start" arrays and it started!

So anyone else running into this issue after updating to V7.0.0 can give that a try.

After it restarted it recognized and reassigned all my drives and shares.

Hope this helps someone!

Edited January 12, 20251 yr by wyee

13 hours ago, wyee said:

I too got this start up error after updating to Unraid V7.0.0 from V6.12.14

There are two different errors, see here:

https://forums.unraid.net/topic/184435-unraid-os-version-700-available/?do=findComment&comment=1508012

 

On 1/12/2025 at 2:45 PM, wyee said:

I too got this start up error after updating to Unraid V7.0.0 from V6.12.14.I followed the instructions steps given in the post above but after removing the pool name "cache" and re-adding it, there was no devices to assign to it. All I got were blanks. unassigned. Trying to restart the shares gave the same error.

So what I did out of pure luck and chance was this:

I removed the pool named "cache" and did not add it back.

Then I just clicked "Start" arrays and it started!

So anyone else running into this issue after updating to V7.0.0 can give that a try.

After it restarted it recognized and reassigned all my drives and shares.

Hope this helps someone!

Just had the same issue and this fixed mine as well. Thanks.