Hi,

 

After upgrading to Unraid 7.0.1, I encountered an issue in my Shares Tab where the message "There are no mountable array or pool disks – cannot add shares" is displayed.

 

The strange thing is that my Docker containers are still functioning properly—I can still access Plex movies, for example.

I am aware that it is not recommended to have only one parity drive. My Disk 1 failed, but I have not experienced any issues using this setup until now.

 

I was wondering if this could be the cause of the problem and whether adding a new Disk 1 might resolve it, or if I should address something else beforehand.

 

Thanks,
Ben

 

tower-diagnostics-20250312-1838.zip

Mar 12 15:26:02 Tower root: Fix Common Problems: Error: Invalid folder cache contained within /mnt

You probably have some container with a host volume specifying cache, but you don't actually have cache.

23 minutes ago, trurl said:

Mar 12 15:26:02 Tower root: Fix Common Problems: Error: Invalid folder cache contained within /mnt

You probably have some container with a host volume specifying cache, but you don't actually have cache.

Thanks for the reply. Indeed, Fix Common Problems detected this issue, which I have since fixed. However, after rebooting, the problem in the Shares Tab persists 

tower-diagnostics-20250312-1913.zip

What do you get from command line with this?

ls -lah /mnt

 

2 minutes ago, trurl said:

What do you get from command line with this?

ls -lah /mnt

 

I get this : 

That looks OK, maybe it's confused because you have no data disks assigned.

 

Why haven't you rebuilt disk1?

10 minutes ago, trurl said:

That looks OK, maybe it's confused because you have no data disks assigned.

 

Why haven't you rebuilt disk1?

I didn’t take the time to address it after receiving my warranty replacements from WD 😅. I’ve been debating how to separate important data with redundancy from data I don’t mind losing, especially now that we have ZFS pools in this update.
Do you think I should downgrade before rebuilding?

2 minutes ago, Ben9 said:

I’ve been debating how to separate important data with redundancy

I assume you know you currently have no redundancy

1 minute ago, trurl said:

I assume you know you currently have no redundancy

Yes, I have two new 8TB drives and was wondering if I should add a third (just for movies, for example) in a pool to avoid write I/O to the parity drive/array. Or would it be better to just buy an SSD as a cache and not worry about it?

 

I also considered using the array without parity for movies since it’s easily expandable while keeping a ZFS pool for important data with redundancy. However, I read that ZFS doesn’t allow drives to spin down, which makes me hesitant.

 

Anyway, this is a bit off-topic for this thread 😅, but thanks for looking into my issue!

11 minutes ago, Ben9 said:

Do you think I should downgrade before rebuilding?

I guess you could downgrade to see if this problem goes away. If so, then this seems like a bug for this edge case.

20 minutes ago, trurl said:

I guess you could downgrade to see if this problem goes away. If so, then this seems like a bug for this edge case.

Indeed, after downgrading, my Shares Tab is working again. I’ll proceed with rebuilding Disk 1.

I'm posting a bug report about this thread. What version are you on now that it is working?

9 minutes ago, trurl said:

I'm posting a bug report about this thread. What version are you on now that it is working?

Version 6.12.10, thanks 

On 3/12/2025 at 9:10 PM, Ben9 said:

Version 6.12.10, thanks 

Just an update—I can confirm that after rebuilding Disk 1 and updating to version 7.0.1, my shares are working properly. Thanks!

Yep, it's a bug with 7.0.x, it should be fixed soon.

 

17 hours ago, trurl said:

 

Awesome!