I had a working zpool with 4 nvme's in z1. If I remember correctly, I did create the zpool via CLI in order to set a custom ashift. It imported into the GUI just fine and has been working.

 

Did the upgrade to 6.12.14. Now the GUI still shows the pool configuration but states that the disks are unmountable.

 

via bash: zpool list and zfs list show nothing. it's as if my pool never existed.

 

Any advice on recovery?

Please post the diagnostics.

3 hours ago, JorgeB said:

Please post the diagnostics.tower-diagnostics-20250106-1611.zip

 

I don't see anything specific in the syslogs that would destroy the zpool 'speedteam'. All I can see if working, then today upon upgrade the zpool doesn't exist system wide anymore.

Edited January 6, 20251 yr by Unoid

I'm going to just nuke the zpool. 

I was able to get the zpool status in a available state, disks [0-2] were unavail while 3n1 was available (parity disk), I ran 
sgdisk -o -a 8 -n 1:1M:0 /dev/nvme0n1  

also on 1 and 2. Then zpool import would work. However mounting in unraid would still fail.

 

I think the ugprade somehow broke the GPT info on some disks which is very concerning if true.

 

At this point I'm going to re-create the zpool and restore data.

 

jorge, if you see what happened from the diagnostic, that's great to know.  otherwise disregard. btw I hate zfs on nvme in unraid.

I ran sgdisk on 3n1, and rebooted, the pool now mounts. 

 

No clue what happened...

IMHO very unlikely it was related to the update, possibly the reboot caused this issue. I've seen it before, where partitions are lost/damage after rebooting with some devices without an apparent reason.

Thanks for always helping JorgeB, 

 

It's scary having to re-wipe the GPT of each disk in a zpool from a normal reboot.