> * cryptswap: the precheck for '/dev/sda5' failed: - The device
/dev/sda5 contains a filesystem type crypto_LUKS.
Ok, so this seems self-explanatory to me. The cryptsetup package has
safety checks to avoid accidentally overwriting a real filesystem when
creating a swap partition, and for whatever reason your existing
/dev/sda5 is failing that check - i.e., whatever data is on that
partition, it was not put there using your current crypttab
'/dev/urandom' line.
This is an added safety feature in cryptsetup, added to address bug
#474258. Try zeroing out /dev/sda5, to see if that fixes the problem
for you?
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037703
Title:
Not possible to mount cryptsetup luks partitions at boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1037703/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
