Something I would like to share, because it caused a bad headache for me. There are two external USB hard drives which I wanted to encrypt, one for not really essential data and one for backups. After following a German guide (there is an English version, which seems to be equivalent), one of the drives (brand new) got automounted, asking me for my passphrase, creating the device mapper node and mounting it as it should be. The other one worked by doing the manual steps on the command-line, but udev and Hal did not recognise it properly as LUKS-encrypted. So after some investigation I found the culprit in the cryptsetup udev rules, where the blkid program failed to identify the encrypted partition. After some head scratching, I stumbled upon a blog post by a util-linux hacker, which described the wipefs tool, introduced in util-linux 2.17. It wipes some faulty left-overs of mkfs, which confuses some programs like blkid. Now everything is fine for both external drives.
| < Zurück | Weiter > |
|---|
Kommentare
IMPORT{program}="/sbin/blkid -o udev -p $tempnode"
is the problem in /etc/udev/rules.d/64-device-mapper.rules