From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 26 Jul 2016 14:40:10 +0200 (CEST) Received: from [192.168.1.47] ([31.34.87.55]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0M0PdN-1bBJmW3Ppd-00ubPC for ; Tue, 26 Jul 2016 14:40:09 +0200 References: <20160721134252.GF27774@yeono.kjorling.se> <5792CED6.4070200@gmx.fr> <579530A4.4090609@gmx.fr> <20160725060122.GA20336@tansi.org> From: "Arbiel (gmx)" Message-ID: <57975A21.60000@gmx.fr> Date: Tue, 26 Jul 2016 14:40:01 +0200 MIME-Version: 1.0 In-Reply-To: <20160725060122.GA20336@tansi.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WbHRr95PIhPQkn862AP95KVCUhUcVT5LJ" Subject: Re: [dm-crypt] Issue with crypttab List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WbHRr95PIhPQkn862AP95KVCUhUcVT5LJ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 =C3=A9crit : > 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=20 > cryptsetup, but one with crypptab and hence this is=20 > 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 >> >> Arbiel >> >> >> Le 23/07/2016 03:56, Arbiel (gmx) a =C3=A9crit : >>> 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 diffi= culty. >>> >>> 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 an= d >>> victor-root_alt as my /etc/crypttab file show >>> >>> |grep -v -e "noauto" /etc/crypttab | grep -v -e "^#" victor-root_1604= >>> UUID=3D22847149-1399-491b-b166-007a50938c5f >>> /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_= 1604:1 >>> luks,keyscript=3D/lib/cryptsetup/scripts/passdev victor-home >>> UUID=3D37447a61-f946-4d38-a398-5a886c4e3f22 >>> /dev/disk/by-uuid/e4fa73a6-92bc-4d1e-98b0-7b6d92661ae4:/.victor-home:= 1 >>> luks,keyscript=3D/lib/cryptsetup/scripts/passdev victor-root_alt >>> UUID=3Dbcc1027f-6078-449f-a26c-99706b5b59b4 >>> /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.victor-root_= alt:1 >>> luks,keyscript=3D/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 decryptin= g, >>> with the following results >>> >>> |journalctl -x -p 0..3 | grep -e "dev-disk-by.* a =C3=83=C2=A9chou=C3= =83=C2=A9" -- Subject: >>> L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:= -.victor\x2droot_1604:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9 -- L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:= -.victor\x2droot_1604:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9, avec le r=C3=83=C2=A9sultat timeout. = -- Subject: L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:= -.victor\x2droot_alt:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9 -- L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:= -.victor\x2droot_alt:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9, avec le r=C3=83=C2=A9sultat timeout. = -- Subject: L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:= -.victor\x2dhome:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9 -- L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:= -.victor\x2dhome:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9, avec le r=C3=83=C2=A9sultat timeout. = -- Subject: L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:= -.victor\x2droot_alt:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9 -- L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:= -.victor\x2droot_alt:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9, avec le r=C3=83=C2=A9sultat timeout. = -- Subject: L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:= -.victor\x2dhome:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9 -- L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:= -.victor\x2dhome:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9, avec le r=C3=83=C2=A9sultat timeout. = -- Subject: L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:= -.victor\x2droot_alt:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9 -- L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:= -.victor\x2droot_alt:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9, avec le r=C3=83=C2=A9sultat timeout. = -- Subject: L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:= -.victor\x2dhome:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9 -- L'unit=C3=83=C2=A9 (unit) >>> dev-disk-by\x2duuid-e4fa73a6\x2d92bc\x2d4d1e\x2d98b0\x2d7b6d92661ae4:= -.victor\x2dhome:1.device >>> a =C3=83=C2=A9chou=C3=83=C2=A9, avec le r=C3=83=C2=A9sultat timeout.|= >>> >>> Sorry for the language, but translation goes that way : >>> - "a =C3=83=C2=A9chou=C3=83=C2=A9" --> "failed" >>> - "avec le r=C3=83=C2=A9sultat" --> "with the result" >>> >>> So, these lines say that the decrypting of victor-root_1604 failed on= ce >>> and succeded on the second try, whereas the decrypting of the other t= wo >>> logical volumes failed on the three tries. This situation does not ar= ise >>> 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=C3=83=C2=B6rling a =C3=83=C2=A9crit := >>>> On 21 Jul 2016 14:53 +0200, from jacques.berger@gmx.fr (Jacques Berg= er): >>>>>
Hi
>>>> 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 > --WbHRr95PIhPQkn862AP95KVCUhUcVT5LJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAleXWikACgkQG6j+1Sdg4KtkQQD9Fp3O7U9+823zKYcW6LIVur5t R1iTTZyo+2dsCFmfqQkA/RaaSaVyJAoAI21LLErpbFi/ElSFE4iPEObX7s6AiLaA =xKKU -----END PGP SIGNATURE----- --WbHRr95PIhPQkn862AP95KVCUhUcVT5LJ--