Mounting encrypted partition will not work

English Install/Boot/Login
1

After the huge Tumbleweed update on February 5, 2015 I am no longer able to mount my encrypted home partition. On the terminal I receive this error message:

linux-3l36:~ # systemctl status ‘systemd-cryptsetup@cr_ata\x2dMaxtor_6Y120M0_Y3NR2A0E\x2dpart1.service’ -l
systemd-cryptsetup@cr_ata\x2dMaxtor_6Y120M0_Y3NR2A0E\x2dpart1.service - Cryptography Setup for cr_ata-Maxtor_6Y120M0_Y3NR2A0E-part1
Loaded: loaded (/etc/crypttab)
Active: failed (Result: exit-code) since Sat 2015-02-07 12:20:39 CET; 2min 40s ago
Docs: man:systemd-cryptsetup@.service(8)
man:crypttab(5)
Process: 2537 ExecStart=/usr/lib/systemd/systemd-cryptsetup attach cr_ata-Maxtor_6Y120M0_Y3NR2A0E-part1 /dev/disk/by-id/ata-Maxtor_6Y120M0_Y3NR2A0E-part1 none none (code=exited, status=127)
Main PID: 2537 (code=exited, status=127)

Feb 07 12:20:39 linux-3l36 systemd[1]: systemd-cryptsetup@cr_ata\x2dMaxtor_6Y120M0_Y3NR2A0E\x2dpart1.service: main process exited, code=exited, status=127/n/a
Feb 07 12:20:39 linux-3l36 systemd[1]: Failed to start Cryptography Setup for cr_ata-Maxtor_6Y120M0_Y3NR2A0E-part1.
Feb 07 12:20:39 linux-3l36 systemd[1]: Unit systemd-cryptsetup@cr_ata\x2dMaxtor_6Y120M0_Y3NR2A0E\x2dpart1.service entered failed state.
Feb 07 12:20:39 linux-3l36 systemd-cryptsetup[2537]: /usr/lib/systemd/systemd-cryptsetup: relocation error: /usr/lib/libcryptsetup.so.4: symbol dm_task_get_info_with_deferred_remove, version Base not defined in file libdevmapper.so.1.03 with link time reference

What will I have to do to resolve this issue?

2

It is working fine here.

It looks as if something did not update correctly.

The most common causes of this are:

  • Using “zypper up” when you should be using “zypper dup”
  • A non-standard repo that is blocking a required update.

If you have been doing “zypper up” or using the update applet, then run


# zypper dup

and see if that fixes the problem. That is how you should be updating.

If that does not solve your problem, then post the output from:


# zypper lr --detail

(use code tags for posting that output).

3

Thank you!
Doing a zypper dup finally fixes this issue. The reason was, that Virtualbox (repo: http://download.virtualbox.org/virtualbox/rpm/opensuse/12.3/) requires an older version of device-mapper, that is incompatible with cryptosetup.

I have removed Virtualbox and everything is fine again. Hopefully Virtualbox will be upgraded soon to support a later version of device-mapper.

Just for my understanding: I thought, that zypper dup is only necessary when upgrading from e.g. 13.1 -> 13.2. Would you recommend to do zypper dup as well for every rolling release of Tumbleweed?

Thanks again.

4

Yes. Every update of Tumbleweed is, in effect, an upgrade. So “zypper dup” is the recommended method.

5

There is a version of Virtualbox in the tumbleweed repos. I do not know if it is the version you want, but I would guess it is at least the same as the version you had from the 12.3 repos.