Since the YaST Partitioner became capable of defining encrypted partitions, I have been able to migrate my existing data partitions by choosing Do not format device, Encrypt device and Mount device options in the partition editor pane; but now in Leap 15.3, unless I select Format device it will not enable Mounting Options so that I can specify a mount point. Needless to say, I do not want to reformat my data partitions!
I have tried selecting Format device to enable Mounting Options, then selecting Mount device and setting the Mount Point to /home/username, then changing back to Do not format device, but when I do that the partitioner clears the mounting options, setting it back to Do not mount device.
This worked fine in previous releases. How can I recover access to my user data?
I assume you did a new installation of 15.3, because just upgrading would not have changed anything in your fstab and crypttab and then there would not be any need to create those entries anew.
I am not running 15.3, thus I can not check or confirm this. But your description sounds as if you have investigated thoroughly and then this is a regression that you shoud make a bug report for. Thus when nobody posts here otherwise, please make one.
Correct. I have several partitions that I have migrated during upgrade (via reinstall) since about V12.2 or V12.3. There was a time also when one could manually configure this by editing /etc/fstab and /etc/crypttab, but now something like systemd has gotten its fingers into the process, and I can’t see how to do that any more.
“upgrade (via reinstall)” is not really what we call “upgrade”. It is a reinstall… In my post above I tried to tell the a real Upgrade (either using the media or on-line zypper dup) would not have touched fstab and crypttab.
I am not sure that udev has something to do with this. I am also not sure that you can not solve the access by editing them. When you have backups of those as they where in 15.2, you could try adding the entries you need to the present files.
And as said earlier, a bug report against the YaST Partitioner module for having this regression could be a way to walk and at least get more information or even a patch.
I am also not sure that you can not solve the access by editing them.
I think that I can; I was confused because fstab and crypttab are using UUIDs instead of device names now.
And as said earlier, a bug report against the YaST Partitioner module for having this regression could be a way to walk and at least get more information or even a patch.