https://bugs.kde.org/show_bug.cgi?id=392787
--- Comment #7 from Andrius Štikonas <andr...@stikonas.eu> --- (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 > automount. I never directly edited fstab. > > I believe this is how it was when it would not boot. I simply commented it > out to get the system to boot. > /dev/mapper/luks-a56b638d-3b1a-451b-bb09-7cbc0263f787 > /run/media/user/DATA1 ext4 defaults 0 0 > > This is how it is now and will boot. > /dev/mapper/luks-a56b638d-3b1a-451b-bb09-7cbc0263f787 > /run/media/user/DATA1 ext4 noauto 0 0 But what I don't understand is how fstab entry appeared in the first place (because I would think the warning should be shown at some point then). You created a new LUKS encrypted partition. Surely there was no fstab entry before you created the partition. -- You are receiving this mail because: You are watching all bug changes.
