* [dm-crypt] Issue with crypttab
@ 2016-07-21 12:53 Jacques Berger
2016-07-21 13:25 ` Robert Nichols
2016-07-21 13:42 ` Michael Kjörling
0 siblings, 2 replies; 8+ messages in thread
From: Jacques Berger @ 2016-07-21 12:53 UTC (permalink / raw)
To: dm-crypt
[-- Attachment #1: Type: text/html, Size: 240 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dm-crypt] Issue with crypttab
2016-07-21 12:53 [dm-crypt] Issue with crypttab Jacques Berger
@ 2016-07-21 13:25 ` Robert Nichols
2016-07-21 13:42 ` Michael Kjörling
1 sibling, 0 replies; 8+ messages in thread
From: Robert Nichols @ 2016-07-21 13:25 UTC (permalink / raw)
To: dm-crypt
On 07/21/2016 07:53 AM, Jacques Berger wrote:
> Hi
>
> Is this the right place to report an issue with crypttab ?
Probably not. /etc/crypttab is processed by the initscripts in your
Linux distribution. cryptsetup does not use it directly.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dm-crypt] Issue with crypttab
2016-07-21 12:53 [dm-crypt] Issue with crypttab Jacques Berger
2016-07-21 13:25 ` Robert Nichols
@ 2016-07-21 13:42 ` Michael Kjörling
2016-07-23 1:56 ` Arbiel (gmx)
1 sibling, 1 reply; 8+ messages in thread
From: Michael Kjörling @ 2016-07-21 13:42 UTC (permalink / raw)
To: dm-crypt
On 21 Jul 2016 14:53 +0200, from jacques.berger@gmx.fr (Jacques Berger):
> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi</div>
Please resend your e-mail in a more readable format. I suggest plain
text.
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“People who think they know everything really annoy
those of us who know we don’t.” (Bjarne Stroustrup)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dm-crypt] Issue with crypttab
2016-07-21 13:42 ` Michael Kjörling
@ 2016-07-23 1:56 ` Arbiel (gmx)
2016-07-24 21:18 ` Arbiel (gmx)
0 siblings, 1 reply; 8+ messages in thread
From: Arbiel (gmx) @ 2016-07-23 1:56 UTC (permalink / raw)
To: Michael Kjörling, dm-crypt
[-- Attachment #1: Type: text/plain, Size: 4150 bytes --]
I understand the issue may be related to my distribution, however let me
please present the case, and you will maybe help me resolve the difficulty.
I'm presently trying to go from Ubuntu 14.04 (cryptsetup 1.6.1) to
Ubuntu 16.04 (cryptsetup 1.6.6) and the problem comes with Ubuntu 16.04.
I want to decrypt 3 logical volumes, victor-root_1604, victor-home and
victor-root_alt as my /etc/crypttab file show
|grep -v -e "noauto" /etc/crypttab | grep -v -e "^#" victor-root_1604
UUID=22847149-1399-491b-b166-007a50938c5f
/dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_1604:1
luks,keyscript=/lib/cryptsetup/scripts/passdev victor-home
UUID=37447a61-f946-4d38-a398-5a886c4e3f22
/dev/disk/by-uuid/e4fa73a6-92bc-4d1e-98b0-7b6d92661ae4:/.victor-home:1
luks,keyscript=/lib/cryptsetup/scripts/passdev victor-root_alt
UUID=bcc1027f-6078-449f-a26c-99706b5b59b4
/dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_alt:1
luks,keyscript=/lib/cryptsetup/scripts/passdev|
It turns out that /etc/crypttab is indeed read and used by
/etc/init.d/cryptdisks during the start-up of the system.
I extracted from the system logs the errors related to this decrypting,
with the following results
|journalctl -x -p 0..3 | grep -e "dev-disk-by.* a échoué" -- Subject:
L'unité (unit)
dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
a échoué -- L'unité (unit)
dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
a échoué -- L'unité (unit)
dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
a échoué -- L'unité (unit)
dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
a échoué -- L'unité (unit)
dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
a échoué -- L'unité (unit)
dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
a échoué -- L'unité (unit)
dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
a échoué -- L'unité (unit)
dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
a échoué, avec le résultat timeout.|
Sorry for the language, but translation goes that way :
- "a échoué" --> "failed"
- "avec le résultat" --> "with the result"
So, these lines say that the decrypting of victor-root_1604 failed once
and succeded on the second try, whereas the decrypting of the other two
logical volumes failed on the three tries. This situation does not arise
with Ubuntu 14.04.
Have someone an idea on what is going wrong ?
Thanks in advance for any help.
Le 21/07/2016 15:42, Michael Kjörling a écrit :
> On 21 Jul 2016 14:53 +0200, from jacques.berger@gmx.fr (Jacques Berger):
>> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi</div>
> Please resend your e-mail in a more readable format. I suggest plain
> text.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dm-crypt] Issue with crypttab
2016-07-23 1:56 ` Arbiel (gmx)
@ 2016-07-24 21:18 ` Arbiel (gmx)
2016-07-25 6:01 ` Arno Wagner
2016-07-25 6:09 ` Milan Broz
0 siblings, 2 replies; 8+ messages in thread
From: Arbiel (gmx) @ 2016-07-24 21:18 UTC (permalink / raw)
To: dm-crypt
[-- Attachment #1: Type: text/plain, Size: 4877 bytes --]
Hi
So, well. I understand this is not the right place to report bug on
cryptsetup, even if the manpage states that
REPORTING BUGS
Report bugs, including ones in the documentation, on the
cryptsetup
mailing list at <dm-crypt@saout.de>
Arbiel
Le 23/07/2016 03:56, Arbiel (gmx) a écrit :
> I understand the issue may be related to my distribution, however let me
> please present the case, and you will maybe help me resolve the difficulty.
>
> I'm presently trying to go from Ubuntu 14.04 (cryptsetup 1.6.1) to
> Ubuntu 16.04 (cryptsetup 1.6.6) and the problem comes with Ubuntu 16.04.
>
> I want to decrypt 3 logical volumes, victor-root_1604, victor-home and
> victor-root_alt as my /etc/crypttab file show
>
> |grep -v -e "noauto" /etc/crypttab | grep -v -e "^#" victor-root_1604
> UUID=22847149-1399-491b-b166-007a50938c5f
> /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_1604:1
> luks,keyscript=/lib/cryptsetup/scripts/passdev victor-home
> UUID=37447a61-f946-4d38-a398-5a886c4e3f22
> /dev/disk/by-uuid/e4fa73a6-92bc-4d1e-98b0-7b6d92661ae4:/.victor-home:1
> luks,keyscript=/lib/cryptsetup/scripts/passdev victor-root_alt
> UUID=bcc1027f-6078-449f-a26c-99706b5b59b4
> /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_alt:1
> luks,keyscript=/lib/cryptsetup/scripts/passdev|
>
>
> It turns out that /etc/crypttab is indeed read and used by
> /etc/init.d/cryptdisks during the start-up of the system.
> I extracted from the system logs the errors related to this decrypting,
> with the following results
>
> |journalctl -x -p 0..3 | grep -e "dev-disk-by.* a échoué" -- Subject:
> L'unité (unit)
> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
> a échoué -- L'unité (unit)
> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> a échoué -- L'unité (unit)
> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> a échoué -- L'unité (unit)
> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> a échoué -- L'unité (unit)
> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> a échoué -- L'unité (unit)
> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> a échoué -- L'unité (unit)
> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> a échoué -- L'unité (unit)
> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> a échoué, avec le résultat timeout.|
>
> Sorry for the language, but translation goes that way :
> - "a échoué" --> "failed"
> - "avec le résultat" --> "with the result"
>
> So, these lines say that the decrypting of victor-root_1604 failed once
> and succeded on the second try, whereas the decrypting of the other two
> logical volumes failed on the three tries. This situation does not arise
> with Ubuntu 14.04.
>
> Have someone an idea on what is going wrong ?
>
> Thanks in advance for any help.
>
>
> Le 21/07/2016 15:42, Michael Kjörling a écrit :
>> On 21 Jul 2016 14:53 +0200, from jacques.berger@gmx.fr (Jacques Berger):
>>> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi</div>
>> Please resend your e-mail in a more readable format. I suggest plain
>> text.
>>
>
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dm-crypt] Issue with crypttab
2016-07-24 21:18 ` Arbiel (gmx)
@ 2016-07-25 6:01 ` Arno Wagner
2016-07-26 12:40 ` Arbiel (gmx)
2016-07-25 6:09 ` Milan Broz
1 sibling, 1 reply; 8+ messages in thread
From: Arno Wagner @ 2016-07-25 6:01 UTC (permalink / raw)
To: dm-crypt
Hi Aribel,
this is the right place to report a bug with cryptsetup,
just not with crypttab. Crypttab is not part of
cryptsetup, just something the different distributions
build around cryptsetup on their own.
From your report, you are not reporting a bug with
cryptsetup, but one with crypptab and hence this is
the wrong place.
Regards,
Arno
On Sun, Jul 24, 2016 at 23:18:28 CEST, Arbiel (gmx) wrote:
> Hi
>
> So, well. I understand this is not the right place to report bug on
> cryptsetup, even if the manpage states that
>
> REPORTING BUGS
> Report bugs, including ones in the documentation, on the
> cryptsetup
> mailing list at <dm-crypt@saout.de>
>
> Arbiel
>
>
> Le 23/07/2016 03:56, Arbiel (gmx) a écrit :
> > I understand the issue may be related to my distribution, however let me
> > please present the case, and you will maybe help me resolve the difficulty.
> >
> > I'm presently trying to go from Ubuntu 14.04 (cryptsetup 1.6.1) to
> > Ubuntu 16.04 (cryptsetup 1.6.6) and the problem comes with Ubuntu 16.04.
> >
> > I want to decrypt 3 logical volumes, victor-root_1604, victor-home and
> > victor-root_alt as my /etc/crypttab file show
> >
> > |grep -v -e "noauto" /etc/crypttab | grep -v -e "^#" victor-root_1604
> > UUID=22847149-1399-491b-b166-007a50938c5f
> > /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_1604:1
> > luks,keyscript=/lib/cryptsetup/scripts/passdev victor-home
> > UUID=37447a61-f946-4d38-a398-5a886c4e3f22
> > /dev/disk/by-uuid/e4fa73a6-92bc-4d1e-98b0-7b6d92661ae4:/.victor-home:1
> > luks,keyscript=/lib/cryptsetup/scripts/passdev victor-root_alt
> > UUID=bcc1027f-6078-449f-a26c-99706b5b59b4
> > /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_alt:1
> > luks,keyscript=/lib/cryptsetup/scripts/passdev|
> >
> >
> > It turns out that /etc/crypttab is indeed read and used by
> > /etc/init.d/cryptdisks during the start-up of the system.
> > I extracted from the system logs the errors related to this decrypting,
> > with the following results
> >
> > |journalctl -x -p 0..3 | grep -e "dev-disk-by.* a échoué" -- Subject:
> > L'unité (unit)
> > dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
> > a échoué -- L'unité (unit)
> > dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
> > a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> > dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> > a échoué -- L'unité (unit)
> > dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> > a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> > dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> > a échoué -- L'unité (unit)
> > dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> > a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> > dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> > a échoué -- L'unité (unit)
> > dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> > a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> > dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> > a échoué -- L'unité (unit)
> > dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> > a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> > dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> > a échoué -- L'unité (unit)
> > dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
> > a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
> > dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> > a échoué -- L'unité (unit)
> > dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
> > a échoué, avec le résultat timeout.|
> >
> > Sorry for the language, but translation goes that way :
> > - "a échoué" --> "failed"
> > - "avec le résultat" --> "with the result"
> >
> > So, these lines say that the decrypting of victor-root_1604 failed once
> > and succeded on the second try, whereas the decrypting of the other two
> > logical volumes failed on the three tries. This situation does not arise
> > with Ubuntu 14.04.
> >
> > Have someone an idea on what is going wrong ?
> >
> > Thanks in advance for any help.
> >
> >
> > Le 21/07/2016 15:42, Michael Kjörling a écrit :
> >> On 21 Jul 2016 14:53 +0200, from jacques.berger@gmx.fr (Jacques Berger):
> >>> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi</div>
> >> Please resend your e-mail in a more readable format. I suggest plain
> >> text.
> >>
> >
> >
> >
> > _______________________________________________
> > dm-crypt mailing list
> > dm-crypt@saout.de
> > http://www.saout.de/mailman/listinfo/dm-crypt
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dm-crypt] Issue with crypttab
2016-07-24 21:18 ` Arbiel (gmx)
2016-07-25 6:01 ` Arno Wagner
@ 2016-07-25 6:09 ` Milan Broz
1 sibling, 0 replies; 8+ messages in thread
From: Milan Broz @ 2016-07-25 6:09 UTC (permalink / raw)
To: Arbiel (gmx), dm-crypt
On 07/24/2016 11:18 PM, Arbiel (gmx) wrote:
> Hi
>
> So, well. I understand this is not the right place to report bug on
> cryptsetup, even if the manpage states that
It is proper place but for cryptsetup itself, for the distro specific
problem it is better to use distro channels.
(But still some users can reply here.
Anyway, for Ubuntu just use https://bugs.launchpad.net/ bug tracker.)
For the crypttab problem - this really differs per distro, upstream
does not maintain crypttab at all.
From the log it could be more systemd-cryptsetup (it is parsing
crypttab and processing it).
Moreover cryptsetup version reported is quite old....
Milan
>
> REPORTING BUGS
> Report bugs, including ones in the documentation, on the
> cryptsetup
> mailing list at <dm-crypt@saout.de>
>
> Arbiel
>
>
> Le 23/07/2016 03:56, Arbiel (gmx) a écrit :
>> I understand the issue may be related to my distribution, however let me
>> please present the case, and you will maybe help me resolve the difficulty.
>>
>> I'm presently trying to go from Ubuntu 14.04 (cryptsetup 1.6.1) to
>> Ubuntu 16.04 (cryptsetup 1.6.6) and the problem comes with Ubuntu 16.04.
>>
>> I want to decrypt 3 logical volumes, victor-root_1604, victor-home and
>> victor-root_alt as my /etc/crypttab file show
>>
>> |grep -v -e "noauto" /etc/crypttab | grep -v -e "^#" victor-root_1604
>> UUID=22847149-1399-491b-b166-007a50938c5f
>> /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_1604:1
>> luks,keyscript=/lib/cryptsetup/scripts/passdev victor-home
>> UUID=37447a61-f946-4d38-a398-5a886c4e3f22
>> /dev/disk/by-uuid/e4fa73a6-92bc-4d1e-98b0-7b6d92661ae4:/.victor-home:1
>> luks,keyscript=/lib/cryptsetup/scripts/passdev victor-root_alt
>> UUID=bcc1027f-6078-449f-a26c-99706b5b59b4
>> /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_alt:1
>> luks,keyscript=/lib/cryptsetup/scripts/passdev|
>>
>>
>> It turns out that /etc/crypttab is indeed read and used by
>> /etc/init.d/cryptdisks during the start-up of the system.
>> I extracted from the system logs the errors related to this decrypting,
>> with the following results
>>
>> |journalctl -x -p 0..3 | grep -e "dev-disk-by.* a échoué" -- Subject:
>> L'unité (unit)
>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
>> a échoué -- L'unité (unit)
>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>> a échoué -- L'unité (unit)
>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>> a échoué -- L'unité (unit)
>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>> a échoué -- L'unité (unit)
>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>> a échoué -- L'unité (unit)
>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>> a échoué -- L'unité (unit)
>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>> a échoué -- L'unité (unit)
>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>> a échoué, avec le résultat timeout.|
>>
>> Sorry for the language, but translation goes that way :
>> - "a échoué" --> "failed"
>> - "avec le résultat" --> "with the result"
>>
>> So, these lines say that the decrypting of victor-root_1604 failed once
>> and succeded on the second try, whereas the decrypting of the other two
>> logical volumes failed on the three tries. This situation does not arise
>> with Ubuntu 14.04.
>>
>> Have someone an idea on what is going wrong ?
>>
>> Thanks in advance for any help.
>>
>>
>> Le 21/07/2016 15:42, Michael Kjörling a écrit :
>>> On 21 Jul 2016 14:53 +0200, from jacques.berger@gmx.fr (Jacques Berger):
>>>> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi</div>
>>> Please resend your e-mail in a more readable format. I suggest plain
>>> text.
>>>
>>
>>
>>
>> _______________________________________________
>> dm-crypt mailing list
>> dm-crypt@saout.de
>> http://www.saout.de/mailman/listinfo/dm-crypt
>
>
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dm-crypt] Issue with crypttab
2016-07-25 6:01 ` Arno Wagner
@ 2016-07-26 12:40 ` Arbiel (gmx)
0 siblings, 0 replies; 8+ messages in thread
From: Arbiel (gmx) @ 2016-07-26 12:40 UTC (permalink / raw)
To: dm-crypt
[-- Attachment #1: Type: text/plain, Size: 5873 bytes --]
Hi
Ok. I'm on my way to report the problem to the Ubuntu's development team.
Thank you, and sorry for the disturbance.
Arbiel
Le 25/07/2016 08:01, Arno Wagner a écrit :
> Hi Aribel,
>
> this is the right place to report a bug with cryptsetup,
> just not with crypttab. Crypttab is not part of
> cryptsetup, just something the different distributions
> build around cryptsetup on their own.
>
> >From your report, you are not reporting a bug with
> cryptsetup, but one with crypptab and hence this is
> the wrong place.
>
> Regards,
> Arno
>
> On Sun, Jul 24, 2016 at 23:18:28 CEST, Arbiel (gmx) wrote:
>> Hi
>>
>> So, well. I understand this is not the right place to report bug on
>> cryptsetup, even if the manpage states that
>>
>> REPORTING BUGS
>> Report bugs, including ones in the documentation, on the
>> cryptsetup
>> mailing list at <dm-crypt@saout.de>
>>
>> Arbiel
>>
>>
>> Le 23/07/2016 03:56, Arbiel (gmx) a écrit :
>>> I understand the issue may be related to my distribution, however let me
>>> please present the case, and you will maybe help me resolve the difficulty.
>>>
>>> I'm presently trying to go from Ubuntu 14.04 (cryptsetup 1.6.1) to
>>> Ubuntu 16.04 (cryptsetup 1.6.6) and the problem comes with Ubuntu 16.04.
>>>
>>> I want to decrypt 3 logical volumes, victor-root_1604, victor-home and
>>> victor-root_alt as my /etc/crypttab file show
>>>
>>> |grep -v -e "noauto" /etc/crypttab | grep -v -e "^#" victor-root_1604
>>> UUID=22847149-1399-491b-b166-007a50938c5f
>>> /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_1604:1
>>> luks,keyscript=/lib/cryptsetup/scripts/passdev victor-home
>>> UUID=37447a61-f946-4d38-a398-5a886c4e3f22
>>> /dev/disk/by-uuid/e4fa73a6-92bc-4d1e-98b0-7b6d92661ae4:/.victor-home:1
>>> luks,keyscript=/lib/cryptsetup/scripts/passdev victor-root_alt
>>> UUID=bcc1027f-6078-449f-a26c-99706b5b59b4
>>> /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_alt:1
>>> luks,keyscript=/lib/cryptsetup/scripts/passdev|
>>>
>>>
>>> It turns out that /etc/crypttab is indeed read and used by
>>> /etc/init.d/cryptdisks during the start-up of the system.
>>> I extracted from the system logs the errors related to this decrypting,
>>> with the following results
>>>
>>> |journalctl -x -p 0..3 | grep -e "dev-disk-by.* a échoué" -- Subject:
>>> L'unité (unit)
>>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
>>> a échoué -- L'unité (unit)
>>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_1604:1.device
>>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>>> a échoué -- L'unité (unit)
>>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>>> a échoué -- L'unité (unit)
>>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>>> a échoué -- L'unité (unit)
>>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>>> a échoué -- L'unité (unit)
>>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>>> a échoué -- L'unité (unit)
>>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.victor\x2droot_alt:1.device
>>> a échoué, avec le résultat timeout. -- Subject: L'unité (unit)
>>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>>> a échoué -- L'unité (unit)
>>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:-.victor\x2dhome:1.device
>>> a échoué, avec le résultat timeout.|
>>>
>>> Sorry for the language, but translation goes that way :
>>> - "a échoué" --> "failed"
>>> - "avec le résultat" --> "with the result"
>>>
>>> So, these lines say that the decrypting of victor-root_1604 failed once
>>> and succeded on the second try, whereas the decrypting of the other two
>>> logical volumes failed on the three tries. This situation does not arise
>>> with Ubuntu 14.04.
>>>
>>> Have someone an idea on what is going wrong ?
>>>
>>> Thanks in advance for any help.
>>>
>>>
>>> Le 21/07/2016 15:42, Michael Kjörling a écrit :
>>>> On 21 Jul 2016 14:53 +0200, from jacques.berger@gmx.fr (Jacques Berger):
>>>>> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi</div>
>>>> Please resend your e-mail in a more readable format. I suggest plain
>>>> text.
>>>>
>>>
>>>
>>> _______________________________________________
>>> dm-crypt mailing list
>>> dm-crypt@saout.de
>>> http://www.saout.de/mailman/listinfo/dm-crypt
>>
>
>
>> _______________________________________________
>> dm-crypt mailing list
>> dm-crypt@saout.de
>> http://www.saout.de/mailman/listinfo/dm-crypt
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2016-07-26 12:40 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-21 12:53 [dm-crypt] Issue with crypttab Jacques Berger
2016-07-21 13:25 ` Robert Nichols
2016-07-21 13:42 ` Michael Kjörling
2016-07-23 1:56 ` Arbiel (gmx)
2016-07-24 21:18 ` Arbiel (gmx)
2016-07-25 6:01 ` Arno Wagner
2016-07-26 12:40 ` Arbiel (gmx)
2016-07-25 6:09 ` Milan Broz
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.