https://bugzilla.suse.com/show_bug.cgi?id=1225882 https://bugzilla.suse.com/show_bug.cgi?id=1225882#c3 Eugenio Paolantonio <eugenio.paolantonio@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(eugenio.paolanton |needinfo?(openexplore1455@p |io@suse.com) |roton.me) CC| |openexplore1455@proton.me --- Comment #3 from Eugenio Paolantonio <eugenio.paolantonio@suse.com> --- Sure, thanks for the bug report and log. The luks devices closure happen after the migration, so if you don't see any other dialog in between the password entry and the error, I think there might be something else wrong as well. Looking at the log, it looks like that the Legacy Aeon installation has been detected three times (while the installation process has been started ten times). Is that correct? I wonder if there is some race condition where the mapped unlocked device shows up too late, so it's not detected, and then for some reason something (btrfs?) keeps it busy. These two issues might be separate. Could you try executing in the terminal of the installer environment once the Welcome screen appears: sudo -i mount -o remount,rw / btrfs property set / ro false sed -i 's|probe_partitions $TIK_INSTALL_DEVICE|sleep 5;probe_partitions $TIK_INSTALL_DEVICE|' /usr/lib/tik/modules/pre/20-mig then, please report if the migration module can reliably detect the encrypted partition (and eventually, if it doesn't fail anymore when calling luksClose). Thanks! -- You are receiving this mail because: You are on the CC list for the bug.