[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #11 from Andrius Štikonas --- (In reply to Chris from comment #10) > here is a video of what i did. > https://vimeo.com/263656284 > F1ndM3! Thanks, I see. Don't think this mount point adding "feature" was intended to

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #10 from Chris --- here is a video of what i did. https://vimeo.com/263656284 F1ndM3! -- You are receiving this mail because: You are watching all bug changes.

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #9 from Andrius Štikonas --- (In reply to Chris from comment #8) > I think it appeared when i used partition manager to set a mount point. I > did get the fstab warning, but adding a second drive, even if encrypted, >

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #8 from Chris --- I think it appeared when i used partition manager to set a mount point. I did get the fstab warning, but adding a second drive, even if encrypted, should not cause the system to fail to boot.

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #7 from Andrius Štikonas --- (In reply to Chris from comment #6) > After adding the LUKS drive and editing the mount point. I had an > additional entry like this. I actually used partition manager to add the no >

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #6 from Chris --- After adding the LUKS drive and editing the mount point. I had an additional entry like this. I actually used partition manager to add the no automount. I never directly edited fstab. I

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #5 from Andrius Štikonas --- (In reply to Chris from comment #4) > Created attachment 111868 [details] > EditMountpoint > > I had edited it. That is what i meant in "Updated the mount point to > something easier to

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #4 from Chris --- Created attachment 111868 --> https://bugs.kde.org/attachment.cgi?id=111868=edit EditMountpoint I had edited it. That is what i meant in "Updated the mount point to something easier to read

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #3 from Andrius Štikonas --- I'll at some point have to try to experiment to reproduce this issue. By tthe way how did you add mount point to fstab? At the moment Partition Manager can not yet add mount points, only

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #2 from Chris --- When creating the luks drive and setting the password. tell the user if automount is set, they will be prompted for the password during boot. Configure Partition manager to force the password

[partitionmanager] [Bug 392787] Creating LUKS encrypted drive on secondary drives causes system to not boot.

https://bugs.kde.org/show_bug.cgi?id=392787 --- Comment #1 from Andrius Štikonas --- Any suggestions what would have helped you to avoid the problem? Maybe a warning dialog when mountpoint of LUKS partition is changed? Obviously it would still be good to have the feature to