Hide Forgot
Description of problem: Lenovo X300-Notebook with encrupted / and swap-Partition. Beginning from second(?) Kernel-Update the system does not schot down properly. It takes about 5 minutes to shut down and an error message cryptsetup Failed to deactivate: Device or resource is to be shown. Did run Fedora beginning from F13 on the same machine and this never happened before. Strange enough, the same does not happen on a desktop system with the same setting. Maybe the ATA driver is part of the problem? Version-Release number of selected component (if applicable): kernel-3.1.5-6.fc16.x86_64
Forgot to say, that this happened after using vpnc sessions. If no vpnc was started, system reboot/halt are as expected. Very wired.
Played a bit around. Even without using vpnc I'll get a longer delay and twice the "cryptsetup Failed to deactivate: Device or resource" error message.
To collect useful information for debugging please do the following: - Save the following script as /lib/systemd/system-shutdown/debug.sh: #!/bin/sh mount -o remount,rw / dmesg > /dmesg.txt mount -o remount,ro / Make sure it's executable (chmod +x ...). - Next time you boot, add the following parameters to the kernel command line in GRUB: log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg - Before you shutdown, make sure SELinux is not in enforcing mode. You can use: setenforce 0 - Do the shutdown. - If you have reproduced the bug during the shutdown, attach the resulting file /dmesg.txt to this Bugzilla.
Unfortunately this helps not so much, dmesg.txt is empty. However I've attached some dmesg.txt created otherwise.
Created attachment 550189 [details] dmesg.txt.old.bz2
Created attachment 550190 [details] dmesg.txt.older.bz2
Are you sure SELinux was not in enforcing mode? I can't think of any other reason for the file to come out empty.
Created attachment 550549 [details] dmesg.txt.bz2 2012-01-03
Next try; now rebooting/halt goes relatively fast; and this time dmesg.txt is not empty, see attachement above (2012-01-03).
Created attachment 551830 [details] dmesg-2012_01_10.txt.bz2
If the root file system is encrypted we cannot destruct it. That's obvious, no? What did you expect?
Same machine, same setting but Fedora 17: the problem does not exist anymore. So we should close this bug.