You are not logged in.
After installing the quite massive amounts of updates, I rebooted.
I could not log in, since my /home wasn't mounted because vlm had'nt created the special files needed for volume group devices in /dev.
Manually running
sudo lvm vgmknodes
creates them and /home is mountable again.
btw, still on 2.6.19-beyond. (atleast for a while longer)
Whats the problem, and is there a temporary fix for this? (eg. creating them manually from rc.local with the above command)
Offline
Sry this is just a "me to" post
If you find a solution, please post it, I will do the same.
P.s. I have /usr /var /home /opt on lvm
Kind regards, enrique
Offline
Hm, no succes so far. Chrooted in and downgraded lvm and coreutil packages, but that did not make any difference.
I was able to log in as root and do a lvm vgmknodes as suggested, but that also did not difference.
Kind regards, enrique
Offline
me is working on a fix atm with a guy from irc
Offline
Ok, cool, any idea if the problem is caused by coreutils or a bug in lvm? mayby lvm should have been statically linked with some lib and it is not?
Kind regards, enrique
Offline
me is working on a fix atm with a guy from irc
Sounds great. Let us now if you guys come up with somehing.
Offline
Same here after an update this morning, but vgmknodes worked for me.
However the problem does not seem to be limited to LVM, because now I can't mount my TrueCrypt drives (which also use the device mapper):
# truecrypt secret.tc /crypt
Enter password for 'secret.tc':
mount: special device /dev/mapper/truecrypt0 does not exist
truecrypt: Mount failed
Offline
Update your system to get the latest versions of device-mapper, udev, and klibc-udev, released today. They include tpowa's fix.
Offline
That solved the problem. Thanks tomk!
Offline
That sounds nice, I will do it as soon as I get home from work. Thanks for the quick fix!
Kind regards, enrique
Offline
Same here, will do when I get home from work. Thanks, that was fast
Offline
I had the same problem with my device mapper partitions - and the latest update fixed it. Thanks!
Offline