You are not logged in.
Pages: 1
Topic closed
Hi,
After updating I can't boot my arch linux because lvm volumes can't be found.
"/sbin/lvm: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory"
There is only a libudev.so.1 in /usr/lib/
Someone getting the same error message?
Last edited by bananagogo (2012-06-03 14:24:34)
Offline
Hi,
I have the same error since I update my system yesterday. We probably forgot to run "mkinitcpio -p linux" to rebuild an initramfs after updating udev to systemd.
I found no solution at this time.
Offline
Thank you for this hint.
Fixed it booting a live system and chroot into my system.
mkinitcpio -p linux there fixed the problem.
Offline
Could you explain to me how that works? I dont get it. Where do I have to run this? How can I mount encrypted device? Do I need to have the same kernel version?
Last edited by nickik (2012-06-14 19:08:33)
Offline
Read the wiki page on chroot...
Offline
What I don't understand is this, do I have to make a change to the unencrypted /boot or to something that is encrypted. If it has to do with the encrypted part, how do I mount that. If not do I have to chroot into the boot (that is mounted).
I don't understand even understand what the actual problem is, thus I dont understand what I have to use chroot for.
Offline
If you don't understand what the problem is, I can't really help you.
If you are experiencing the same error as the OP, then the fix in this thread may be of assistance to you.
You boot from the Live image, unencrypt your encrypted filesystem(s), mount them, chroot into your b0rked environment and then fix it by rebuilding your intiramfs.
To unencrypt your LUKs container(s), you use:
cryptsetup luksOpen /dev/sdx containername
In any event, this thread is marked a solved. If you encounter issues trying to fix your issue, open a new thread with explicit details about your errors and what you have tried as a fix.
Offline
Cheers worked for me as well.
Offline
worked for me as well. I wrote the process for myself. so I am putting it here in case someone needs help. I can expand on it if necessary.
1. boot into install cd
2. unlock encrypted drive
- modprobe dm-crypt
- modprobe dm-mod
- cryptsetup luksOpen /dev/sdx container
(these can be found on /boot/grub/menu.lst file).
enter password
- will open the /dev/sdx drive
3. if lvm
- vgscan
- get the name of the vg
- vgchange -a y {name of vg}
- lvscan should display all lv on device
4. mount root
- mkdir /mnt/arch
- need to know root fs type
- may need to run fs check before mounting
- mount -t fstype /dev/{lvroot_path} /mnt/arch
5. chroot (from change root wiki)
cd /mnt/arch
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
if seperate partitions for boot usr var, mount them
eg:
mount /dev/<device-or-partition-name> boot/
if network:
cp -L /etc/resolv.conf etc/resolv.conf
chroot . /bin/bash
6. mkinitcpio -p linux
7. reboot
Offline
aias described it correctly. If you only have an Ubuntu 11.10 at hand, you need to apt-get lvm2. otherwise, the vg-tools are not available.
Offline
Why is this problem still not fixed? I just updated a very outdated computer (last update sometime october '11) and have the same problem again. even worse this time is that I don't have any live cd at hand and only a very slow internet connection.
Last edited by rochus (2012-07-12 19:10:06)
Offline
The howto of aias is working well up to the point of starting mkinitcpio.
This fails with message:
==> ERROR: unable to locate module directory for kernel '3.0-ARCH'
So the new kernel on the system is 3.4, but live cd is coming along with kernel 3.0.
Any idea to continue?
update:
mkinitcpio -k <kernelversion> -p linux
resolves the problem
<kernelversion> can be found at. /lib/modules
regards
thefrog
Last edited by thefrog (2012-07-14 10:12:23)
Offline
Did you forget to mount your boot partition to the chroot's boot? (i.e. /mnt/arch/boot) I had some problem with mkinitcpio as well but figured that an unmounted boot was the problem.
Offline
I've just came across this issue, one simple solution that helped me:
sudo ln -sf /usr/lib/libudev.so.1 /usr/lib/libudev.so.0
Just make symbolic link to the file that is already there.
Offline
Please don't necrobump old topics, especially just to post awful advice. If /usr/lib/libudev.so.1 was the same as /usr/lib/libudev.so.0, then it wouldn't have a different name. Learn what soname bumps are, and why they happen.
Packages which provide /usr/lib/libudev.so.0 are available on the AUR, use one of those if you need it.
Closing.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1
Topic closed