Misleading "cryptsetup: WARNING: invalid line in /etc/crypttab - "
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| cryptsetup (Debian) |
Fix Released
|
Unknown
|
||
| cryptsetup (Ubuntu) |
Low
|
Surbhi Palande | ||
| Lucid |
Low
|
Unassigned | ||
| Maverick |
Low
|
Surbhi Palande |
Bug Description
Binary package hint: cryptsetup
When there's no line for the cryptsetup root device, a misleading warning is issued during update-initramfs:
cryptsetup: WARNING: invalid line in /etc/crypttab -
I'm attaching a patch that handles this better, by outputting
cryptsetup: WARNING: Missing line in /etc/crypttab for $target
in this case.
I've ran into this when manually doing the "mdadm-
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelMo
Package: cryptsetup 2:1.0.6-7ubuntu5 [modified: usr/share/
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
Uname: Linux 2.6.28-8-generic i686
Daniel Hahler (blueyed) wrote : | #2 |
Daniel Hahler (blueyed) wrote : | #4 |
TESTCASE:
0a. /dev/md1 being my root device
0b. /etc/crypttab refers to the rootdevice as "sroot", not "md1"
1. cryptsetup luksOpen /dev/md1 md1
2. update-initramfs -c -k $(uname -a)
Changed in cryptsetup: | |
status: | Incomplete → Triaged |
Daniel Hahler (blueyed) wrote : | #5 |
It should be "uname -r" in step 2 above, of course.
Jonathan Kolberg (bulldog98) wrote : | #6 |
For me the same thing happens in lucid (I only get the linenumber where the error occurs) For me this line is an empty line, could that be the reason of the bug?
AmenophisIII (amenophisiii) wrote : | #7 |
please include the patch. cryptroot is already hard enough to debug, because its quite fragile (read: crappy :)
would have saved me some time today.
Daniel Hahler (blueyed) wrote : | #8 |
I would be happy to refresh this patch, if this would increase its acceptance.
Changed in cryptsetup (Ubuntu): | |
importance: | Low → Medium |
Robbie Williamson (robbiew) wrote : | #9 |
Has anyone confirmed this bug exists in Maverick?
Changed in cryptsetup (Ubuntu Lucid): | |
milestone: | none → ubuntu-10.04.2 |
importance: | Undecided → Low |
Changed in cryptsetup (Ubuntu Maverick): | |
importance: | Medium → Low |
status: | Triaged → Incomplete |
Carsten Andrich (carsten-andrich) wrote : | #10 |
I just stumbled upon this one, trying to install the maverick amd64 desktop beta, so I can confirm that it does exist in Maverick.
Changed in cryptsetup (Ubuntu Maverick): | |
status: | Incomplete → Triaged |
Robbie Williamson (robbiew) wrote : | #11 |
Surbhi, can you take a look at this one? Seems like something we could easily slide into Maverick.
Changed in cryptsetup (Ubuntu Maverick): | |
assignee: | nobody → Surbhi Palande (csurbhi) |
milestone: | none → ubuntu-10.10 |
Changed in cryptsetup (Ubuntu Maverick): | |
milestone: | ubuntu-10.10 → maverick-updates |
Changed in cryptsetup (Ubuntu Maverick): | |
status: | Triaged → In Progress |
Changed in cryptsetup (Ubuntu Maverick): | |
status: | In Progress → Fix Committed |
Accepted cryptsetup into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https:/
tags: | added: verification-needed |
Martin Pitt (pitti) wrote : | #13 |
Any testers of the macerick-proposed package? As this has been in -proposed for a long time already, I'll remove the proposed package soon if there is no feedback. Thank you!
Also, this needs to be fixed in Natty _first_ before it can go to -updates.
Changed in cryptsetup (Ubuntu Maverick): | |
milestone: | maverick-updates → none |
Changed in cryptsetup (Ubuntu): | |
milestone: | maverick-updates → none |
Changed in cryptsetup (Ubuntu Lucid): | |
milestone: | ubuntu-10.04.2 → none |
Rolf Leggewie (r0lf) wrote : | #14 |
@Carsten, can you please verify the package from -proposed fixes the issue?
description: | updated |
Daniel Hahler (blueyed) wrote : | #15 |
I've submitted the patch upstream to Debian, so that it will hopefully come into Ubuntu this way:
http://
Changed in cryptsetup (Debian): | |
status: | Unknown → New |
Changed in cryptsetup (Debian): | |
status: | New → Fix Committed |
Changed in cryptsetup (Debian): | |
status: | Fix Committed → Fix Released |
Jean-Louis Dupond (dupondje) wrote : | #16 |
The fix (that was already added in the debian package) is merged into Ubuntu since Precise.
Changed in cryptsetup (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in cryptsetup (Ubuntu Lucid): | |
status: | New → Triaged |
Changed in cryptsetup (Ubuntu Maverick): | |
status: | Fix Committed → Won't Fix |
David Schoen (neerolyte) wrote : | #17 |
This seems to still break in Quantal (12.10) when upgrading from 12.04.
I was getting the "cryptsetup: WARNING: invalid line in /etc/crypttab - " errors when running update-initramfs (under a live CD because the machine was completely unbootable).
After following advice from http://
Rolf Leggewie (r0lf) wrote : | #18 |
lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".
Changed in cryptsetup (Ubuntu Lucid): | |
status: | Triaged → Won't Fix |
Roel Van de Paar (roel11) wrote : | #19 |
This seems still flaky even in 17.04.
# cat /etc/crypttab
nvme0n1p3_crypt UUID="20eada6e-
# update-initramfs -k 4.10.0-24-generic -c -b /boot
update-initramfs: Generating /boot/initrd.
cryptsetup: WARNING: Invalid source device UUID="20eada6e-
cryptsetup: WARNING: Invalid source device UUID="20eada6e-
W: mdadm: /etc/mdadm/
# vi /etc/crypttab
# cat /etc/crypttab
nvme0n1p3_crypt UUID=20eada6e-
# update-initramfs -k 4.10.0-24-generic -c -b /boot
update-initramfs: Generating /boot/initrd.
W: mdadm: /etc/mdadm/
In other words, when the UUID is quoted (") it fails. However, the quoted UUID is exactly what at least one of the other tools in Ubuntu must use because there was a second line in that file originally (I removed it to make the example/testcase above clearer) for another drive and that one uses quotes.
Please review and QA this area properly. Thank you.
no longer affects: | cryptsetup |
Roel Van de Paar (roel11) wrote : | #20 |
How do I add zesty?
Roel Van de Paar (roel11) wrote : | #21 |
"at least one of the other tools in Ubuntu" - that is unless I added it, which is a possibility too. Still, that secondary drive works fine (assuming that /etc/crypttab is used to unlock it, which I cannot confirm due to lack of knowledge in that area)
Michael McCallum (stickycode) wrote : | #22 |
I'm seeing this on 17.04 as well
Ø sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.
cryptsetup: WARNING: invalid line in /etc/crypttab for myvolume -
cryptsetup: WARNING: invalid line in /etc/crypttab for myvolume -
manually mounted the volume on boot with the wrong name
Tomas (xhudik) wrote : | #23 |
ubuntu 18.04, the same:
update-initramfs -c -k all
update-initramfs: Generating /boot/initrd.
cryptsetup: WARNING: invalid line in /etc/crypttab for luks-9013e4bc-
update-initramfs: Generating /boot/initrd.
cryptsetup: WARNING: invalid line in /etc/crypttab for luks-9013e4bc-
Thanks for the bug report and patch. Would you be able to create a step-by-step testcase, so that we can test your problem here?