FS#30919 - [initscripts] 2012.07.5-1 crypttab fails unlock partition during boot

Attached to Project: Arch Linux
Opened by siriusb (siriusb) - Monday, 30 July 2012, 10:26 GMT
Last edited by Tom Gundersen (tomegun) - Sunday, 12 August 2012, 12:30 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:
Boot process stops because couldn't mount a LUKS encrypted data partition after initscripts update.
More details: https://bbs.archlinux.org/viewtopic.php?id=146111

Additional info:

I have separate encrypted root and home partitions.

/etc/crypttab (oroiginal, not working):
myhome /dev/disk/by-uuid/something1 /path/to/keyfile1
mydata /dev/disk/by-uuid/something2 /path/to/keyfile2

Working crypttab (for me):
myhome /dev/disk/by-uuid/something1 /path/to/keyfile1
mydata /dev/sda3 /path/to/keyfile2

Steps to reproduce:
Upgrade to initscripts 2012.07.5-1
This task depends upon

Closed by  Tom Gundersen (tomegun)
Sunday, 12 August 2012, 12:30 GMT
Reason for closing:  Fixed
Comment by Nicky726 (Nicky726) - Monday, 06 August 2012, 11:39 GMT
I can confirm this. My crypttab contains single entry, original state with /dev/disk/by-uuid/... specified path no longer works with initscripts 2012.07.5-1. Changing the path specification to UUID=... as described in manpage does not work either, changing to /dev/sdb1 makes it work. I use keyfile as well.
Comment by Nicky726 (Nicky726) - Monday, 06 August 2012, 11:56 GMT
Initscripts 2012.08.1-1 from [testing] fix this for me.
Comment by siriusb (siriusb) - Sunday, 12 August 2012, 12:29 GMT
  • Field changed: Percent Complete (100% → 0%)
[2012-08-12 11:26] upgraded initscripts (2012.07.5-1 -> 2012.08.2-1)

Error message:
crypt_init() failed: Block device required

What changed:
/dev/disk/by-uuid/ syntax works on both lines, UUID= still fails
Comment by Tom Gundersen (tomegun) - Sunday, 12 August 2012, 12:30 GMT
This is a separate bug, which has been fixed in git.

Loading...