Hello,

 

I attempted to upgrade to 7.0.0rc1 to find out that spares weren't supported. I reverted back and began to follow the steps of:

 

1. Import the array

2. Remove the spare

3. Export the array

4. Remove the array from the GUI

5. Add the array from the GUI

 

After doing all of this it does not import the array after starting it. If I go to the CLI after starting the array and then importing it via CLI, I can access my data once again. However, what I've noticed is it still says "Unmountable: no file system" and I'm unable to add a subpool to bring back in my cache vdev. 

 

When recreating the array, do I count the cache vdev into the total number of slots? For example, I have 12 HDDs and 1 nvme (cache). Would I create the array with 13 slots vs 12? Otherwise, I'm not sure how to bring that cache vdev back into the fold. Any help is greatly appreciated.

 

Please post the diagnostics and the output from zpool import (after exporting the pool)

31 minutes ago, JorgeB said:

Please post the diagnostics and the output from zpool import (after exporting the pool)

Hey Jorge,

So export the pool via CLI and import via CLI? Or export via CLI, remove the pool and then add the pool?

Export via CLI, Unraid cannot import an already imported pool.

 

zpool export main_array

 

14 minutes ago, JorgeB said:

Export via CLI, Unraid cannot import an already imported pool.

 

zpool export main_array

 

Correct, I just wanted clarification if you wanted me to import via CLI or attempt from GUI again after removing the array after exporting.

Edited December 13, 20241 yr by impenetrable-aviator2287

export the pool and 

1 hour ago, JorgeB said:

post the diagnostics and the output from zpool import

 

5 minutes ago, JorgeB said:

export the pool and 

 

root@Fileserver:~# zpool status
  pool: main_array
 state: ONLINE
config:

        NAME        STATE     READ WRITE CKSUM
        main_array  ONLINE       0     0     0
          raidz2-0  ONLINE       0     0     0
            sdb1    ONLINE       0     0     0
            sdc1    ONLINE       0     0     0
            sdd1    ONLINE       0     0     0
            sde1    ONLINE       0     0     0
            sdk1    ONLINE       0     0     0
            sdl1    ONLINE       0     0     0
            sdm1    ONLINE       0     0     0
            sdn1    ONLINE       0     0     0
            sdo1    ONLINE       0     0     0
            sdp1    ONLINE       0     0     0
            sdq1    ONLINE       0     0     0
            sdr1    ONLINE       0     0     0
        cache
          nvme0n1   ONLINE       0     0     0

errors: No known data errors
root@Fileserver:~# zpool export main_array
root@Fileserver:~# zpool import main_array
root@Fileserver:~# 
 

fileserver-diagnostics-20241213-1100.zip

That not what I asked, though it will do, but you must leave the pool exported, you cannot import it using the CLI, export it again

After the pool is exported, and back on the GUI, click on the pool, then "remove pool", back on main add a new pool with the same name and 13 slots, assign all the pool devices together, including the cache vdev (nvme0n1), don't create any subpools or change de filesystem for the pool, leave it in auto, then start the array and it should import the pool, but post a screenshot from main before array start to confirm it's all correct.

2 minutes ago, JorgeB said:

That not what I asked, though it will do, but you must leave the pool exported, you cannot import it using the CLI, export it again

Here is without importing it via CLI after starting the array. However, I can't access my shares until I import and restart the array.

fileserver-diagnostics-20241213-1106.zip

Just now, JorgeB said:

After the pool is exported, and back on the GUI, click on the pool, then "remove pool", back on main add a new pool with the same name and 13 slots, assign all the pool devices together, including the cache vdev (nvme0n1), don't create any subpools or change de filesystem for the pool, leave it in auto, then start the array and it should import the pool.

Ok, I'll run through this. I was asking if that's what I needed to do initially with the 13 disks vs 12. I'll give you an update shortly.

@JorgeBThank you sir! That did the trick. That's what I was confused about when you said to remove the pool, recreate and don't create subpools. So including the subpools into the total number of disks was the answer I was searching for. Thanks again! 

 

Now that we know the spares never worked, if a disk were to fail, I'm assuming I'd just assign that spare manually where the failed disk is? 

10 minutes ago, impenetrable-aviator2287 said:

if a disk were to fail, I'm assuming I'd just assign that spare manually where the failed disk is? 

Correct.