cryptsetup: Failed to set a proper state for notification semaphore

synthead · 2010-11-07 09:19:05

[root@superkid ~]# cryptsetup -c aes-xts-plain -y -s 512 luksFormat /dev/sda9

WARNING!
========
This will overwrite data on /dev/sda9 irrevocably.

Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase:
Verify passphrase:
semid 1212419: semop failed for cookie 0xd4d80b5: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by cookie value 223183029 (0xd4d80b5) to initialize waiting for incoming notifications.

I'm brand new at encrypting partitions. What is going on here and how can I avoid this?

Lars Stokholm · 2010-11-13 16:53:56

Any news? I'm getting this too on an already encrypted partition.

Edit: Perhaps I should add that the partition was just fine up until today.

Last edited by Lars Stokholm (2010-11-13 20:25:37)

ssptfire · 2010-11-14 23:34:45

I had the same problem, and after hours of searching it came down to my stupidity. I hadn't enable sha512 modules, so it didn't know what '-s 512' meant. Enabled them with `modprobe sha512_generic` and reran the cryptsetup and it worked fine.

Hope this helps

mikesd · 2010-11-15 01:27:51

Lars Stokholm wrote:

Any news? I'm getting this too on an already encrypted partition.
Edit: Perhaps I should add that the partition was just fine up until today.

Same thing happens on one of my encrypted partitions. It didn't initially and I'm not sure when it started. Haven't had a chance to look into it yet.

Lars Stokholm · 2010-11-15 16:19:14

The device-mapper package was updated two weeks ago. Apparently it's now out-of-date. I would not be surprised if the next update fixes it. (It didn't - I tried.)

Last edited by Lars Stokholm (2010-11-15 18:21:32)

mikesd · 2010-12-11 12:22:59

This issue is now fixed for me. I'm guessing it was the device-mapper (2.02.76-1 -> 2.02.77-1) upgrade at the end of November that fixed it though I'm not 100% sure as I only have to mount that drive once a week or so.

twiggz · 2011-01-27 18:18:19

Got the same issue. Only happens when i open up luks partition on my external drive.

banshee28 · 2011-03-05 14:52:31

synthead wrote:

[root@superkid ~]# cryptsetup -c aes-xts-plain -y -s 512 luksFormat /dev/sda9

WARNING!
========
This will overwrite data on /dev/sda9 irrevocably.

Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase:
Verify passphrase:
semid 1212419: semop failed for cookie 0xd4d80b5: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by cookie value 223183029 (0xd4d80b5) to initialize waiting for incoming notifications.

I'm brand new at encrypting partitions. What is going on here and how can I avoid this?

I am having the exact same issue trying to setup a single dedicated 2T new HD. I used cfdisk to setup one large linux part, then running this command and its getting this error. I have tried modprobe sha512_generic, but that did not work. I have ALL pacman updates incl latest device-mapper.

I am trying to setup this ONE drive as a single large encrypted drive using a passkey from a file.

cryptsetup -c aes-xts-plain -y -s 512 luksFormat /dev/sdb1 /home/mypc/mykeyfile

WARNING!
========
This will overwrite data on /dev/sdb1 irrevocably.

Are you sure? (Type uppercase yes): YES
semid 425985: semop failed for cookie 0xd4da53c: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by cookie value 223192380 (0xd4da53c) to initialize waiting for incoming notifications.

I may start a new thread but this is pretty much the same issue I am having. Also I did the urandom to write random data to the entire drive for extra security as the wiki recommended. I am following this wiki: https://wiki.archlinux.org/index.php/Sy … troduction

Here is the fdisk for this drive:

 
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe8070000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63  3907029167  1953514552+  83  Linux

Last edited by banshee28 (2011-03-05 15:09:50)

banshee28 · 2011-03-05 22:28:14

Edit: Created new post... Thanks
https://bbs.archlinux.org/viewtopic.php … 03#p899803

synthead · 2011-06-06 20:09:54

Old thread, but ... bump. Still having the same error. This is on a USB drive, if it matters.

synthead · 2011-06-07 13:08:38

Could it be because of our kernel somehow? https://bugs.launchpad.net/ubuntu/+sour … bug/719388

Filed a bug report: https://bugs.archlinux.org/task/24614

Last edited by synthead (2011-06-07 13:16:01)

Arch Linux

#1 2010-11-07 09:19:05

cryptsetup: Failed to set a proper state for notification semaphore

#2 2010-11-13 16:53:56

Re: cryptsetup: Failed to set a proper state for notification semaphore

#3 2010-11-14 23:34:45

Re: cryptsetup: Failed to set a proper state for notification semaphore

#4 2010-11-15 01:27:51

Re: cryptsetup: Failed to set a proper state for notification semaphore

#5 2010-11-15 16:19:14

Re: cryptsetup: Failed to set a proper state for notification semaphore

#6 2010-12-11 12:22:59

Re: cryptsetup: Failed to set a proper state for notification semaphore

#7 2011-01-27 18:18:19

Re: cryptsetup: Failed to set a proper state for notification semaphore

#8 2011-03-05 14:52:31

Re: cryptsetup: Failed to set a proper state for notification semaphore

#9 2011-03-05 22:28:14

Re: cryptsetup: Failed to set a proper state for notification semaphore

#10 2011-06-06 20:09:54

Re: cryptsetup: Failed to set a proper state for notification semaphore

#11 2011-06-07 13:08:38

Re: cryptsetup: Failed to set a proper state for notification semaphore

Board footer