New answers tagged

3

Yes, it's the same master key. After all, you only have one copy of your data on disk, which is encrypted one way only, so as far as the data itself is concerned there is only ever one key. If you used different master keys you'd see different "random" data for each key slot, which is not very useful. It's possible to change the master key but it involves ...


1

It looks as though the journal has become corrupt, doing some searches over the past few days, this seems to not be uncommon on devices that use LUKS. You could try running an fsck on the device, acknowledging that any data on the device may not be accessible after - you may like to use dd to make a copy of the drive before this. A common resolution ...


0

Note that latest git version (will be released as 2.2) of KDE Partition Manager can do those steps. It still needs more testing, but so far it seems to work.


2

It looks like that the hook lvm2 run after the hook encrypt during Arch Linux's Initial RAM filesystem phase is not able to activate thinly provisioned logical volumes. With the same storage configuration as depicted in my question except for normal logical volumes instead of thinly provisioned ones the volume group containing these can be activated without ...


0

I often get errors like this for no apparent reason and often simply unmounting and remounting fixes it. You can do this with the following commands. unmount - I know it never mounted in the first place, and will likely throw an error, but I would run to ensure a clean state for running luksClose sudo umount "/media/userone/New Volume" lukClose sudo ...


1

Assuming you meant container files... The downside of such containers is that their survival depends on the outer filesystem. Files that large usually end up using several fragments; if you ever lose the outer filesystem to any kind of corruption, you won't be able to recover the containers either, even if the raw data of those containers is still intact. ...


1

With the help above from Alexander Batischev, and some very useful information from Reddit user cookie_enthusiast on the /r/linuxquestions page on Reddit, I managed to get this working. It turns out that GRUB2 works well with UUIDs, and not so well with device names. With this knowledge in mind, we need the following 4 UUIDs at hand, before we can ...



Top 50 recent answers are included