Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #157050 > unrolled thread

systemd and encrypted partition (was: grub and encrypted partition problem)

Back to article view | Back to linux.debian.user

Contents

  systemd and encrypted partition (was: grub and encrypted partition problem) Hans <hans.ullrich@loop.de> - 2015-08-29 17:40 +0200
    Re: systemd and encrypted partition (was: grub and encrypted  partition problem) Matthew Moore <a91738246@gmail.com> - 2015-08-29 20:20 +0200
      Re: systemd and encrypted partition (was: grub and encrypted  partition problem) Matthew Moore <a91738246@gmail.com> - 2015-08-29 21:20 +0200

#157050 — systemd and encrypted partition (was: grub and encrypted partition problem)

[Multipart message — attachments visible in raw view] — view raw

Hello list,
I am having still the problem that my encrypted partition are not opened
at boot and thus cannot be mounted.
I believe, it might be a problem with systemd, but i am not experienced with 
systemd, to have a clue, where to look.
IMO this is the related error message of systemd:
Aug 29 16:18:16 protheus2 systemd-default-display-manager-
generator[200]: */lib/systemd/system/kdm.service is not a systemd unit, we 
disable th* 
*rpcbind.target: Dependency Before=rpcbind.target dropped* 
*[/run/systemd/generator/systemd-cryptsetup@home.service:13] Failed to 
add required mount for, ignoring: * 
*open-vm-tools.service: Cannot add dependency job, ignoring: Unit open-
vm-tools.service failed to load: N* 
*display-manager.service: Cannot add dependency job, ignoring: Unit 
display-manager.service is masked.* 
*display-manager.service: Cannot add dependency job, ignoring: Unit 
display-manager.service is masked.* 

Also I get an error message by creating a new initrd:
update-initramfs -u -k all 

I looked, if /dev/sda8 is in /etc/uswusp.conf, but as it is correct, /dev/sda5 
is named in it (which is swap).
It would be nice, if someone could give me a clue, how to initialise the crypt 
related configurations.
Thank you very much.
Best regards
Hans

[toc] | [next] | [standalone]

#157058 — Re: systemd and encrypted partition (was: grub and encrypted partition problem)

On 2015-08-29 05:12:46 PM, Hans wrote:
> Hello list,
> I am having still the problem that my encrypted partition are not opened
> at boot and thus cannot be mounted.
> I believe, it might be a problem with systemd, but i am not experienced with 
> systemd, to have a clue, where to look.
> IMO this is the related error message of systemd:
> Aug 29 16:18:16 protheus2 systemd-default-display-manager-
> generator[200]: */lib/systemd/system/kdm.service is not a systemd unit, we 
> disable th* 
> *rpcbind.target: Dependency Before=rpcbind.target dropped* 
> *[/run/systemd/generator/systemd-cryptsetup@home.service:13] Failed to 
> add required mount for, ignoring: * 
> *open-vm-tools.service: Cannot add dependency job, ignoring: Unit open-
> vm-tools.service failed to load: N* 
> *display-manager.service: Cannot add dependency job, ignoring: Unit 
> display-manager.service is masked.* 
> *display-manager.service: Cannot add dependency job, ignoring: Unit 
> display-manager.service is masked.* 

I'm also not a systemd expert, but 'failed to add required mount' seems
suggestive.

> Also I get an error message by creating a new initrd:
> update-initramfs -u -k all 

What is the error message? 

> I looked, if /dev/sda8 is in /etc/uswusp.conf, but as it is correct, /dev/sda5 
> is named in it (which is swap).
> It would be nice, if someone could give me a clue, how to initialise the crypt 
> related configurations.

How did you set up your partitions? Do you use cryptsetup? Did you fill
out the relevant entries in /etc/cryptab? What happens if you run
cryptdists_start?

MM

[toc] | [prev] | [next] | [standalone]

#157064 — Re: systemd and encrypted partition (was: grub and encrypted partition problem)

On 2015-08-29 08:23:25 PM, Hans wrote:
> > > It would be nice, if someone could give me a clue, how to initialise the
> > > crypt related configurations.
> > 
> > How did you set up your partitions? Do you use cryptsetup? Did you fill
> > out the relevant entries in /etc/cryptab? What happens if you run
> > cryptdists_start?
> 
> Yes, I did this command (which I used on all my other computers as well):
> 
> cryptsetup -c aes-lrw-benbi -y -s 384 luksFormat /dev/sdaX
> 
> then I opened it with "cryptsetup luksOpen /dev/sdaX myname" and at last I 
> formatted it with "mkfs.ext4 /dev/mapper/myname".
> 
> In /etc/crypttab I got he correct entry
> 
> myname UUID=UUID_of_/dev/mapper/mynameblabla  none luks,retry=1,cipher=aes-
> lrb-benbi:sha256

The UUID should be the UUID of the encrypted device (/dev/sdaX above),
not the decrypted device (/dev/mapper/myname).

Does running the command cryptdisks_start work? AFAIK that is what gets
called during startup, so you can check your configuration without
rebooting.

Hope this helps,
MM

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web