ecryptfs-mount-private fails with "Error locking counter"

Does this still happen even after a reboot?

My hard disk has failed - impossible to say whether the two issues are related, but I wouldn't be surprised.

adding the line below to my fstab fixed the problem.

tmpfs /dev/shm tmpfs defaults 0 0

I have this same problem,but it cannot help. Can anything help me with it?

I cannnot boot ubuntu from HDD, so I chroot from LiveCD and login. I typed ecryptfs-mount-private. I dont know where is the problem. Help me.

Hmm, possibly a problem with upstart not getting /dev/shm mounted
quickly enough?

Anyone else experiencing this problem, do you have /dev/shm mounted?

Yes, I have this line in fstab:
tmpfs /dev/shm tmpfs defaults 0 0

Thank you, Jonah.

I came across this bug after an upgrade from 9.10 -> 10.4. Adding

tmpfs /dev/shm tmpfs defaults 0 0

to my fstab and mounting tmpfs solved the problem.

Hmm, okay, so the bug here isn't in eCryptfs, but in whatever is supposed to add "tmpfs /dev/shm tmpfs defaults 0 0" to /etc/fstab. Maybe basefiles?

The suggested line to add to /etc/fstab DOES NOT work for me.
I have the same error "error locking counter"

I'm doing some tests in ubuntu 12.04 booting into recovery mode:
 - I boot into recovery mode
 - I choose a root prompt
 - then I remount all in rw mode
 - then I try to access my private data by executing:
      su norber
      ecryptfs-mount-private

but this last step fails with the message "error locking counter"
and after trying again with the suggested line added to /etc/fstab ... the same error.

I think there is a big problem if one can't access his private data in the recovery mode.
I know there is a way to readonly access the private data by the command 'ecryptfs-recover-private' , but I'm interested in mounting my home propertly (I mean in its place and in rw mode) when I run into recovery mode.

Any other suggestion?

In Ubuntu 14.04, I get this error when using a live session to run ecryptfs-mount-private as my user after I chroot into the target environment. Adding the suggested line doesn't solve the issue for me either.