Hey team,

 

Upgraded to 6.12.1 and this one ZFS drive didn't mount. If I have it mount is locks the system from loading the rest of the array. Right now I have my disk to not auto start until I get word with how to proceed.

 

• Drive that's hanging up is cache-medium

 

viper-diagnostics-20230623-1058.zip

Edited June 23, 20233 yr by viper81

Pool corruption can be the result of a RAM issue, it would be a good idea to run a couple of memtest passes before proceeding, then you can try importing the pool in read-only mode:

zpool import -o readonly=on cache-medium

If it works backup and re-create the pool

Thanks so much this is now solved. I was able to use your command and then start the array. Used Krusader to copy the files. Now I will clear the drive and re-create the pool. Thank you so much again!

Still recommend running memtest, zfs pool corrupting out of the blue is not normal, and if there's an underlying issue it may happen again.

Sorry forgot to add I have no memory issues so far. Once backed up I have been running for the past hour or so. I'm going to leave for 24hrs if possible but so far no errors/fails.

 

What I think happened "cache-medium" only stores my VM's and ISO's. I upgraded to 6-12.1 with the VM running and shutdown and think it corrupted it.

 

NOTE: I changed this cache drive to ZFS the day 6.12 launched. Backed it up and formatted to the new format. This drive on ZFS file system type has been working great until the upgrade to 6.12.1 this AM.

Edited June 23, 20233 yr by viper81

OK, unlikely that the upgrade directly caused anything, since zfs is the same release, but it had to do a pool import/export, and there's a chance it would find an previous/existing problem.