You are not logged in.
hello folks,
i just made a pacman -Syu, which also updated mdadm and cryptsetup (not the kernel). but after a reboot, the system didn't boot any more. after #'ing the cryptsetup-relevant lines in /etc/crypttab and /etc/fstab, the system booted again. after a check, i get those messages:
~ $ cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdd1[0] sde1[1]
390707641 blocks super 1.2 [2/2] [UU]
md0 : active raid1 sdb1[0] sdc1[1]
1465134841 blocks super 1.2 [2/2] [UU]
unused devices: <none>
~ $ sudo cryptsetup luksOpen /dev/md0 data
Passwort:
Geben Sie den Passsatz für /dev/md0 ein:
semid 65537: semop failed for cookie 0xd4d2ffb: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by cookie value 223162363 (0xd4d2ffb) to initialize waiting for incoming notifications.
what happened and how to fix it?
i didn't change anything. so it shouldn't be anything about modules or whatever.
EDIT: okay, it's not aboud the raid, but about the cryptsetup version. see below.
Last edited by _abraxas (2011-01-28 11:18:34)
Offline
Got the same problem here: It fails with
semid 1048580: semop failed for cookie 0xd4d3177: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by cookie value 223162743 (0xd4d3177) to initialize waiting for incoming notifications.
when i try to do
cryptsetup -c aes-xts-plain -s 512 luksFormat /dev/md0
Last edited by raylz (2011-01-07 18:46:38)
Offline
Ive created a bug report on: https://bugs.archlinux.org/task/22351 since this obviously has been a bug some weeks ago: https://bbs.archlinux.org/viewtopic.php?id=108003
Offline
thank you. i have also seen the other thread, but since it used to work for me until the update, i am not quite sure whether it is the same issue...lets see...
EDIT: okay, downgrading to cryptsetup-1.1.3-1-x86_64 solved the problem. maybe its another implementation in 1.2.0.1?
Last edited by _abraxas (2011-01-07 20:30:12)
Offline
BTW:
dbus and hal cannot be the problem: i am starting cryptsetup before starting dbus and hal.
Offline
SOLVED!
It works again with the new version of the device-mapper: 2.02.81 (no unknown semaphore state anymore).
But also the crypttab syntax has changed. After removing the options in crypttab, cryptsetup 1.2.0-1 works again.
Old crypttab file:
# NAME SOURCE DEVICE PASSWORD OPTIONS
#home /dev/sda4 ASK -c aes-xts-plain -s 512
#data /dev/md0 ASK -c aes-xts-plain -s 512
New crypttab file:
# NAME SOURCE DEVICE PASSWORD OPTIONS
home /dev/sda4 ASK
data /dev/md0 ASK
Have a look at https://bugs.archlinux.org/task/22351
Offline