6.12.3

Crossposting from the update announcement post:

Quote

 

"After upgrading, the two cache drives wouldn't mount and one drive would say "mounting" but never would.  The other cache drive wouldn't reattach to the cache pool.  In a jetlagged panic, I formatted the second drive.  Realized that was a dumb move since I didn't know the root cause, so I took a step back.  Now the system is saying that there's corruption on the drive that won't mount, but it will let me add that formatted drive back into the pool (not that it helps me at all, lol.)

 

Has anyone seen this?  Anything I google just leads me back to some ZFS issues, but this appeared after the update so not sure if it's related somehow.  Gonna do a memtest right now just in case.  Memtest passed."

 

 

@JorgeB replied:

Quote

Very unlikely that this is upgrade related, the zfs pool is online so you need to manually export it first:

zpool export cache_zfs

Then start the array, go to the pool and click "clear" then "scrub", if there any errors after the scrub please start a new thread in the general support forum and post new diagnostics.

Running that command doesn't do anything, just hangs.  Cache drive still says mounting... When I boot without the array started and mounted, the command comes back with "Cache_Zfs not found" or something similar.

Also have tried "zpool import -o readonly=on cache_zfs" but get the error message "Ummountable: Unsupported or no file system"

Any next steps are appreciated! I might be out of my depth with this one.

thairaid-diagnostics-20230928-1507.zip

Post output of:

zpool import

 

 pool: cache_zfs
     id: 16704231958696166049
  state: DEGRADED
status: One or more devices contains corrupted data.
 action: The pool can be imported despite missing or damaged devices.  The
        fault tolerance of the pool may be compromised if imported.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
 config:

        cache_zfs   DEGRADED
          mirror-0  DEGRADED
            sdj1    ONLINE
            sdk1    UNAVAIL

Do you know what happened to the missing device?