I bought a WD My Book 4TB USB3 drive and deleted the NTFS partition it ships with. I then created a new GPT and added one LUKS/ext4 partition to it. I used gnome-disks for this, which uses udisks2 as far as I know. The partition was created and I was able to copy files to it.
When I connected the disk on the next day it showed up as unpartitioned space. I checked various CLI tools and was able to unlock the LUKS and mount the ext4 partition without a problem. Still, gnome-disks does not "see" the LUKS.
Using "udisksctl dump" I can see the device sdb but not the partitoion sdb1. However with "udevadm info --export-db" I see sdb1.
I will attach some logs and hope someone can make help solve the problem.
Created attachment 99965 [details]
Here is some relevant output. Please tell me if you need anything else.
My system has the following packages btw:
Created attachment 100057 [details]
Here's a screenshot to better show the problem.
I also found that udisksctl does not seem to "see" sdb1 (it sees sdb just fine):
$ udisksctl info -b /dev/sdb1
Error looking up object for device /dev/sdb1
In order to test this further I deleted the partition, created a new GPT and recreated the partition with the same size: no change.
However I discovered that the LUKS volume shows up and works fine on older Fedora releases (tested with F17), so it looks like the disk and partitioning is actually totally fine and there is some regression in gnome-disks/udisk/kernel?
I will try again tomorrow with a more recent release (F19) to narrow down the regression window.