Saturday, June 12. 2010udev ate my laptop today?
I finally got punished today for using unstable without knowing enough about my system.
 Since I can't access my emails I'm hoping for help from planet-debian. Please excuse...So the last words of my machine: Loading, please wait... One or more specified logical volume(s) not found. Unable to find LVM volume mylvm/root_crypt One or more specified logical volume(s) not found. Unable to find LVM volume mylvm/swap_crypt File descriptor 3 (/conf/conf.d/cryptroot) leaked on lvm invocation. Parent PID 352: /bin/sh udevd-work[77]: kernel-provided name 'dm-0' and NAME= 'mapper/mylvm-swap' disagree, please use SYMLINK+= or change the kernel to provide the proper name Please, if you can help me, write a comment to this blogpost! (Thank you, Hanno for borrowing me your laptop!) update: It wasn't udev (this time). Sorry. The problem was, that I updated libdevmapper without also updating dmsetup. I could boot into an older kernel and solve this. A Bug against the LVM Debian package is already filled. Trackbacks
No Trackbacks
Comments
No clue about LVM volumes, but "(Thank you, Hanno for borrowing me your laptop!)" sounds funny =) will Hanno find out that he has lent you his laptop via this blog entry?
I get those messages from udev too, however my system still boots. I got lvm+crypt too.
Lately I have seen some weird delays from udev. Have you tried just waiting? What I get in boot is essentially [30 second delay] udevadm settle - timeout of 30 seconds reached (or something) [another 30 second delay] The same message again [10 second delay] The same message but with 10 seconds and then the system boots.
A while ago I had exactly the same problem.
Running an encrypted debian system via LVM. Udev killed my booting,too. I used the debian installer cd, booted into a rescue shell. After that: I opened my lvm by hand with cryptsetup luksOpen. Mounted the partions in the correct places (/home, /boot , /proc , /sys). Used dpkg -i on the old udev from my archive. The initrd was built successfully and I was able to boot again normal. After that, I followed some discussions about the topic and some days later there was an update for dmsetup, cryptsetup, lvm2 and so on. After that installing the latest udev gave me no more booting problems.
Like Sami, I get those messages even through the system boots just fine.
I see no delays, the system is up in about 20 seconds. I’m running testing with the 2.6.34-1 kernel from experimental. |
