[artix-general] [s6] system not decrypting/mounting (lvm on luks) a non root volume at boot

[Javier]

On 4/21/20 4:40 PM, Dudemanguy via artix-general wrote:
> On 4/21/20 1:08 PM, Javier via artix-general wrote:
>> So it's still missing to prompt for the password, and instead it's indicating nothing to read from input...
> 
> Thanks for being my guinea pig so far. It's honestly really appreciated! What happens if you try to manually start the service with s6-rc (s6-rc -u change cryptsetup) after everything else is finished starting up? If that doesn't work, does it still work if you manually execute the script?

No problem, I'm interested on it getting to work, :)

It looks like s6 believes cryptsetup started successfully, so trying to start it up again does nothing.  But if you get it down, and then up again, it just works:

% sudo s6-rc -u change cryptsetup
%
% sudo s6-rc -d change cryptsetup
Device cryp-ext-main is not active.
% sudo s6-rc -u change cryptsetup
Unlocking cryp-ext-main
Enter passphrase for /dev/disk/by-uuid/6a7d2c8d-113f-4551-8529-25961c1f7dd8:
% ls /dev/ext-main/
data@
% lsblk -f
NAME                 FSTYPE      FSVER    LABEL    UUID                                   FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1               vfat        FAT32    uefi     8E53-8EBA                               510.7M     0% /uefi
├─sda2               ext4        1.0      boot     91873189-b48a-41b4-860a-367985fa0020    256.1M    41% /boot
└─sda3               crypto_LUKS 2                 1c43ec30-ce0b-4111-a852-79899aa965f1
  └─cryp-lm-0
      └─lm--0-root                                                                           136.2G    32% /
      sdb 
      └─sdb1               crypto_LUKS 2                 6a7d2c8d-113f-4551-8529-25961c1f7dd8
        └─cryp-ext-main    LVM2_member LVM2 001          iYRsRB-M2Fl-RsKB-83s9-LV3l-oZPe-Qz31qd
            └─ext--main-data ext4        1.0      ext-data 204b5531-53ec-4f8b-bebd-1411be4e111e
% sudo mount -t ext4 -o commit=60 UUID=204b5531-53ec-4f8b-bebd-1411be4e111e /ext                                                                                              
% lsblk -f
NAME                 FSTYPE      FSVER    LABEL    UUID                                   FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                                      
├─sda1               vfat        FAT32    uefi     8E53-8EBA                               510.7M     0% /uefi
├─sda2               ext4        1.0      boot     91873189-b48a-41b4-860a-367985fa0020    256.1M    41% /boot
└─sda3               crypto_LUKS 2                 1c43ec30-ce0b-4111-a852-79899aa965f1                  
  └─cryp-lm-0                                                                                            
    └─lm--0-root                                                                           136.2G    32% /
sdb                                                                                                      
└─sdb1               crypto_LUKS 2                 6a7d2c8d-113f-4551-8529-25961c1f7dd8                  
  └─cryp-ext-main    LVM2_member LVM2 001          iYRsRB-M2Fl-RsKB-83s9-LV3l-oZPe-Qz31qd                
    └─ext--main-data ext4        1.0      ext-data 204b5531-53ec-4f8b-bebd-1411be4e111e    141.2G    64% /ext

So starting cryptsetup up manually does work as you suspected.  It does prompt and request me for the password, and successfully decrypts the partition.  Just missing that behavior at boot, :)

-- 
Javier

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.artixlinux.org/archives/artix-general/attachments/20200422/5145c290/attachment-0001.sig>