automount executable encrypted disk in Leap 15.3
Hail, A disk that was encrypted in Leap 15.2 was not automatically available after a new installation of 15.3. I can access the encrypted container dev/sd1 with cryptsetup -v luksOpen /dev/sda1 cr_sda1 (r,w only). I would like to know what the clean and 'proper' way is to have this disk mount at boot (with user r,w,x) within the Leap 15.3 framework. I have the contents backed up. Rick
On 12/12/2021 01.45, Rick Smegal wrote:
Hail, A disk that was encrypted in Leap 15.2 was not automatically available after a new installation of 15.3. I can access the encrypted container dev/sd1 with cryptsetup -v luksOpen /dev/sda1 cr_sda1 (r,w only). I would like to know what the clean and 'proper' way is to have this disk mount at boot (with user r,w,x) within the Leap 15.3 framework. I have the contents backed up.
Rick
You need to create proper entries in /etc/crypttab and fstab. Something like: cr_backup UUID=3804e2da... LABEL=Backup /backup btrfs compress 0 0 Mutandis mutandi, of course :-) -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (2)
-
Carlos E.R.
-
Rick Smegal