From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Mon, 4 May 2015 21:05:33 +0200 (CEST) Received: by wizk4 with SMTP id k4so132857727wiz.1 for ; Mon, 04 May 2015 12:05:32 -0700 (PDT) Message-ID: <5547C2F7.3000305@gmail.com> Date: Mon, 04 May 2015 21:05:27 +0200 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] cryptsetup 1.6.2 hands on "waiting for zero" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mrukant Popat Cc: dm-crypt On 05/04/2015 08:56 PM, Mrukant Popat wrote: > Dear All, > > I am using cryptsetup 1.6.2 on a freescale imx6 processor. However when I run "cryptsetup -v --debug luksFormat /dev/sdb1" it hangs. Below is the output. ... > > # Udev cookie 0xd4d2ea2 (semid 0) decremented to 1 > > # Udev cookie 0xd4d2ea2 (semid 0) waiting for zero In fact this has nothing to do with cryptsetup itself, it is device-mapper library internals. Usually it means misconfiguration of libdevmapper installation or wrong or missing device-mapper udev rules. Do you compile it yourself? What distro is it? Milan