[SOLVED] Boot fails after upgrading -current

The SARPi project forum. For anything and everything relating to Slackware ARM on a Raspberry Pi 1, 2, and 3. This forum is NOT a replacement or substitute for the Slackware (ARM) forums on Linux Questions website! Please try to seek help there first about any issues you may be experiencing, or question you might have, before posting on here.
User avatar
sam
Registered user
Registered user
Posts: 5
Joined: Sat Nov 28 2015 - 13:48:24

[SOLVED] Boot fails after upgrading -current

Postby sam » Sat Nov 28 2015 - 15:19:24

Hi,
on my RPi2 with Slackware ARM-current, I made the latest -current upgrade and now it can't boot anymore.

Here's what I have done:
I installed eudev, libgudev and aaa_elflibs manually using installpkg, uninstalled udev using removepkg and the rest I upgraded using slackpkg (as usual).
Then I refreshed my initrd.gz, because I'm using LVM on that system.
However, the boot fails and stops because it the LVM partitions cannot be mounted. Then I can use the command line for analyzing the issue.
Now, when I use vgscan, it says

Code: Select all

vgscan: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

and when I do readlink /usr/lib/libudev.so.0, it shows libudev.so, but that one does not exist in /usr/lib/, so the link is broken.

Now my question is:
How can I fix it?
I think I could boot from another SD card and chroot to the broken system. But what then?
Last edited by sam on Sat Nov 28 2015 - 17:56:29, edited 1 time in total.

User avatar
linicks
Registered user
Registered user
Posts: 126
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: Boot fails after upgrading -current

Postby linicks » Sat Nov 28 2015 - 16:58:14

Sounds like a broken symlink.

EDIT #2: STOP RIGHT THERE before you read the rest of this post.

I just checked the symlinks on my Pi2:

/lib/libudev.so.0 -> libudev.so.0.13.1
/usr/lib/libudev.so -> ../../lib/libudev.so.0.13.1

so read the rest, but do the above.

#######################################

See here (it's not English, but you will get the drift):

http://www.coyotus.com/viewtopic.php?id=1670

So maybe try:

Code: Select all

ln -s /usr/lib/libudev.so /usr/lib/libudev.so.0


Nick
P.S. I don't like using the -f (force) with ln command.

EDIT: BTW, if the system is so broken to stop you creating symlinks with 'ln', there is an emergency command 'sln' which is a statically built 'ln' that doesn't need any libs. That saved me a few times in my learning days of GNU/Linux many years ago. So, something like:

Code: Select all

sln /usr/lib/libudev.so /usr/lib/libudev.so.0
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
sam
Registered user
Registered user
Posts: 5
Joined: Sat Nov 28 2015 - 13:48:24

Re: Boot fails after upgrading -current

Postby sam » Sat Nov 28 2015 - 17:42:10

Hi Nick,
thanks for your answer.
It works! :)

I made:

Code: Select all

ln -s /lib/libudev.so.1 /usr/lib/libudev.so
vgscan --mknodes
vgchange -ay
mount /dev/lvg/root /mnt
exit
and then it continued booting.

Now my next question is:
How do I make the link permanent, so I don't need to type the commands above on every boot?

P.S. There is no sln command available in the command shell.

User avatar
sam
Registered user
Registered user
Posts: 5
Joined: Sat Nov 28 2015 - 13:48:24

Re: Boot fails after upgrading -current

Postby sam » Sat Nov 28 2015 - 17:54:23

Got it! :D
I ran

Code: Select all

mkinitrd -F
again and now it boots.

User avatar
linicks
Registered user
Registered user
Posts: 126
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: [SOLVED] Boot fails after upgrading -current

Postby linicks » Sat Nov 28 2015 - 18:30:18

Great stuff!

OK, I expect when in recovery shell mode you need to type the explicit path, i.e. :

/bin/sln

or:

/sbin/sln

Both exist, and should be provided by GNU libc package, which all Slackware has.

Nick
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
sam
Registered user
Registered user
Posts: 5
Joined: Sat Nov 28 2015 - 13:48:24

Re: [SOLVED] Boot fails after upgrading -current

Postby sam » Sat Nov 28 2015 - 18:46:12

Thx Nick.
Good to know. :ok:

Return to “SARPi Project - Slackware ARM on a Raspberry Pi”

Who is online

Users browsing this forum: CommonCrawl [Bot] and 0 guests