Hi,
Quote#apt-cache policy cryptsetup
cryptsetup:
Installed: 2:1.4.3-1
Candidate: 2:1.4.3-1
Version table:
*** 2:1.4.3-1 0
500 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
I get some errors and i cannot open my encrypted partitions during boot process. I have to do it by hand (via cryptsetup luksOpen etc.).
Quote
Unlocking the disk /dev/disk/by-uuid/..... (blabla)
Enter passphrase: cryptsetup: relocation error: cryptsetup: symbol crypt_activate_by_keyfile_offset, version CRYPTSETUP_1.0 not defined in file libcryptsetup.so.4 with link time reference
jackyohh, as this is not reported by any other, and my luks /home also working:
Perhaps you got hit by the oneday bug of dpgk?
Does this help:
apt-get install -f
If this does not help try to reinstall. You can find you last N packages upgraded by
echo "$(N=9;cd /var/lib/dpkg/info;ls -t *.list|head -n $N|sed -e's/\:.*/ /' -e's/\.list$/ /'|tr -d '\n')"
neither apt-get -f install, nor reinstalling cryptsetup solve it. maybe it has something to do with it's called "Schlüsselableitung" in German - don't know the English expression for it.
i only type once my password (for one partition) and cryptsetup rebuild the internal key of this partition to unlock all other partitions/volumes.
@jacky, can you mount a crypted partition by hand later - after the boot process? (Hint: update-initramfs -u)
What does it show:
find /etc -iname '*.dpkg*'
Quote from: "ralul"@jacky, can you mount a crypted partition by hand later - after the boot process? (Hint: update-initramfs -u)
jup, like i said, no problem, only at boot i get this error.
Quote from: "ralul"
What does it show:
find /etc -iname '*.dpkg*'
# find /etc -iname '*.dpkg*'
/etc/ca-certificates.conf.dpkg-old
/etc/avserver.conf.dpkg-new
/etc/lvm/lvm.conf.dpkg-dist
/etc/login.defs.dpkg-old
/etc/init.d/ushare.dpkg-new
/etc/kde4/kdm/kdmrc.dpkg-dist
/etc/lirc_alt_serial/hardware.conf.dpkg-dist
/etc/lirc_alt_serial/lircd.conf.dpkg-dist
"only at boot i get this error. "
a) update-initramfs -u
b) try an older kernel
c) (re)install the newest kernel (DU should do)!
And check your /etc directory. "dpkg-new" files are perhaps critical! You should do for example:
diff /etc/avserver.conf /etc/avserver.conf.dpkg-new
and then edit aproprietly ....
a) check
b) check --> 3.1-6.towo.2-siduction-amd64
c) check --> 3.4-2.towo.1-siduction-amd64
nothing helped :/
avserver.conf is part of some media streamer, so it has nothing to do with cryptsetup. same with ushare.dpkg-new.
only thing that helped is downgrading to 1.4.1-3
perhaps something has changed in config file? ... or just a bug?? ... a bug in my package file??
here is my crypttab
# <target> <source> <key> <options>
440gb_crypt UUID=25492be2-ac15-4ebb-a449-9db4c308acd4 none luks
1tb_crypt UUID=dc2837dd-9988-4c33-ba20-fa64e2e8ddab 440gb_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived
2tb_crypt UUID=99e4037d-8d7c-4d12-9370-a3c0c75970dd 440gb_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived
Yes in changelog there was mentioned a change regarding "scripts"
SOLVED!!
there is a missing dependency! i have to install the new version of libcryptsetup4. (i only installed cryptsetup by hand)
apt-get install libcryptsetup4
maintainer should add this dependency!
thx for your help ralu!!
This dependency is not missing:
cryptsetup - cryptsetup-bin - libcryptsetup4
(Have you been hit by a buggy dpkg?)
Because of your first error message you should have looked at libcryptsetup.so.4
Quote from: "ralul"This dependency is not missing:
cryptsetup - cryptsetup-bin - libcryptsetup4
(Have you been hit by a buggy dpkg?)
very strange, your are right. don't know why it was not installed. buggy dpkg? ... hmm i don't know. i saw no error during installation.
Quote from: "ralul"
Because of your first error message you should have looked at libcryptsetup.so.4
yeah i looked for it at the end;) ... i didn't thought at it, because i believed that such file would be installed at the same time, or that it is already included in cryptsetup.
i believed rather in some internal error!
Every now and then my experience with problems:
Think twice looking at error messages and go for it all possible directions ...