nullata

Hello Unraid, 1. Problem: After upgrading to Unraid version 7.0.0, the system stopped mounting a ZFS raidz2 pool consisting of 4 drives and an SSD cache drive during the array startup from the UI. The pool is functional and can be mounted manually via the command line, but Unraid displays the error: "Unmountable: wrong or no file system." To mount & validate the pool manually via CLI: zpool import <myPoolName> zpool get all <myPoolName> Then navigate to the pool mountpoint e.g. "/mnt/user/myPoolName" and validate that files are available and Read/Write operations are possible. 2. Problem workaround (CLI) - remove the cache drive: zpool import <myPoolName> zpool remove <myPoolName> <driveName> Then restart the array/server and post-restart the pool is mounted as normal. e.g. zpool import docstash zpool remove docstash sde Then restart as mentioned above. If the cache drive is re-added then the 'Unmountable: unsupported or no file system' problem appears again and the pool becomes unmountable according to the Unraid UI, otherwise its fine. 3. Note: Up until version 7.0.0 this was never a problem. I understand that ZFS cache drives are not officially supported by Unraid for whatever reason. The original setup has been working for me since ZFS was initially introduced. I believe this problem is derived from strict pattern matching in the Unraid backend, or at least this seems to be the most logical cause. Again, I understand that Unraid does not officially support cache drives for pools, but again, its 2025 and the free alternatives to Unraid have had this feature available for a very long time. I don't understand why even advanced users are not allowed to make elementary changes like this. In version 6.12 this was not a problem. Can we pls allow this in 2025? Cheers