Luks problem on startup: device-mapper: ioctl

orschiro · 2010-02-06 08:39:02

Hello guys,

since I made the big update I have several problems with my internal harddrive which is encrypted with luks.

On startup I get the following error after I type in the passphrase:

device-mapper: ioctl: unable to remove open device temporary-cryptsetup-949

device-mapper: remove ioctl: Device or resource busy

What does that mean and how could I fix it?

Best regards

flamelab · 2010-02-06 08:43:02

Is it related to this problem ? http://bbs.archlinux.org/viewtopic.php?id=90206

orschiro · 2010-02-06 09:04:44

Hello flamelab,

yeah it seems to be the same problem and it's also related to this one printing the following message at startup too.

:: Activating LVM2 Groups
  File-based locking initialisation failed

Very strange behaviour...

Last edited by orschiro (2010-02-06 09:08:46)

orschiro · 2010-02-08 19:38:25

Does nobody know why this problem occurs?

fac · 2010-02-09 19:44:58

I have just gotten the same problem as well. Try and take a look here: http://bugs.archlinux.org/task/16735

orschiro · 2010-02-10 06:04:55

Hello fac,

so basically you tried the versions from testing and it worked again flawlessly?

Natanji · 2010-02-10 10:53:07

Hello orschiro,
I think I have the exact same problem as you.
For me that message you posted is shown, but the crypto volumes themselves mount completely fine nevertheless. Is that also the case for you?

Last edited by Natanji (2010-02-10 10:53:30)

orschiro · 2010-02-10 11:32:49

Hello Natanji,

yes I can mount them too, but it's quite annoying to see this message everytime you are mounting an encrypted device.

Did you already try the packages from testing?

Regards

fac · 2010-02-10 16:20:41

No, the way i read it, it is just a question of waiting for a new version and then the warnings will go away.

I have the warnings, but my encrypted devices unlocks every time (up till now at least).

orschiro · 2010-02-10 22:29:07

Then I'm pacified that I'm not the only one who is getting those warnings. Let's await the updates and discuss again.

Regards

Natanji · 2010-02-11 20:44:26

With the new kernel update, these messages went away for me. I still get the "File-based locking initialisation failed" though, but that seems to be a different problem.

orschiro · 2010-02-12 04:38:51

Hmm I still get them, even with updated kernel and udev.

Natanji · 2010-02-12 19:43:06

Damn it, I also have them again. Must have overlooked it or something...

orschiro · 2010-02-20 14:58:33

Any changes due to the latest updates?

orschiro · 2010-02-27 09:25:58

All error messages seem to be gone with the new version of mkinitcpio except the following.

:: Activating LVM2 Groups
  File-based locking initialisation failed

Is this the same for you?

Natanji · 2010-03-03 11:52:14

Yes.

Arch Linux

#1 2010-02-06 08:39:02

Luks problem on startup: device-mapper: ioctl

#2 2010-02-06 08:43:02

Re: Luks problem on startup: device-mapper: ioctl

#3 2010-02-06 09:04:44

Re: Luks problem on startup: device-mapper: ioctl

#4 2010-02-08 19:38:25

Re: Luks problem on startup: device-mapper: ioctl

#5 2010-02-09 19:44:58

Re: Luks problem on startup: device-mapper: ioctl

#6 2010-02-10 06:04:55

Re: Luks problem on startup: device-mapper: ioctl

#7 2010-02-10 10:53:07

Re: Luks problem on startup: device-mapper: ioctl

#8 2010-02-10 11:32:49

Re: Luks problem on startup: device-mapper: ioctl

#9 2010-02-10 16:20:41

Re: Luks problem on startup: device-mapper: ioctl

#10 2010-02-10 22:29:07

Re: Luks problem on startup: device-mapper: ioctl

#11 2010-02-11 20:44:26

Re: Luks problem on startup: device-mapper: ioctl

#12 2010-02-12 04:38:51

Re: Luks problem on startup: device-mapper: ioctl

#13 2010-02-12 19:43:06

Re: Luks problem on startup: device-mapper: ioctl

#14 2010-02-20 14:58:33

Re: Luks problem on startup: device-mapper: ioctl

#15 2010-02-27 09:25:58

Re: Luks problem on startup: device-mapper: ioctl

#16 2010-03-03 11:52:14

Re: Luks problem on startup: device-mapper: ioctl

Board footer