[SOLVED] Can't boot, libmount.so.1 not found

slamhound · 2018-01-25 20:50:40

I can't boot into arch anymore and am trying to figure out how to troubleshoot. I was updating today (I update regularly, so everything was mostly up to date) and everything seemed to go fine. As the system was updating, I did notice that thunar wouldn't open, and then chrome wouldn't open. When running them from command line, they both gave an error regarding libmount.so.1 not being found. I thought perhaps something happened during the updates and that I would need to reboot. But when I did, I got more errors about libmount.so.1 and was not able to boot at all. Here is the full error message after GRUB:

mount: error while loading shared libraries: libmount.so.1: cannot open shared object file: No such file or directory
mount: error while loading shared libraries: libmount.so.1: cannot open shared object file: No such file or directory
mount: error while loading shared libraries: libmount.so.1: cannot open shared object file: No such file or directory
mount: error while loading shared libraries: libmount.so.1: cannot open shared object file: No such file or directory
/init: line 13: can't open /proc/cmdline: no such file
:: running early hook [udev]
failed to parse kernel command line, ignoring: no such file or directory
starting version 236
:: running hook [udev]
:: Triggering uevents...
ERROR: device '' not found. Skipping fsck.
:: mounting '' on real rout
mount: error while loading shared libraries: libmount.so.1: cannot open shared file: No such file or directory
sh: can't access tty; job control turned off

It drops me to a prompt, but I can't even type anything there. Any thoughts on how to troubleshoot? Googling the error message about libmount.so.1 didn't lead to any helpful (or recent) posts.

Last edited by slamhound (2018-01-26 03:13:32)

lo1 · 2018-01-25 20:56:13

Seems to me a big mess. Are you able to chroot into the system using an usb drive/cd? If so, try to provide a pacman.log and we'll start from there.

seth · 2018-01-25 22:22:28

https://wiki.archlinux.org/index.php/Pa … an_upgrade

Also run "pacman --root /mnt -Qkk" to check the integrity of your installation. libmount is in the libutil-linux package, so you need to re-install that for sure.

slamhound · 2018-01-25 22:29:46

Thanks for the help. I was able to chroot in and look at the pacman log. I'm writing this from a different computer, so not entirely sure how to get the whole thing. But here are the things that look unusual:

Right after the line:

[ALPM] upgraded linux (4.14.14-1 -> 4.14.15-1)

I get this:

[ALPM-SCRIPLET] /tmp/alpm_oORLSo/.INSTALL: line 1: 25151 Segmentation fault       (core dumped) findmnt --fstab -uno SOURCE /boot &> /dev/null

Later, when building the image, I get the following two lines:

[ALPM-SCRIPLET]       -> Running build hook: [autodetect]
[ALPM-SCRIPLET]  ==> ERROR: failed to detect root filesystem

And I also get an error after running 'gtk-update-icon-cache.hook'...

[ALPM-SCRIPLET] /usr/share/libalpm/scripts/gtk-update-icon-cache: line 10: 31837 Segmentation fault      (core dumped) gtk-update-icon-cache -q "$f$

Thoughts on what to do next?

slamhound · 2018-01-25 23:01:56

[edit]: Okay, I understand the proc, sys, dev stuff now; I see that I was misreading the documentation (didn't notice that arch-chroot and chroot were different).

Thanks Seth...I tried that command, too, and although it looked like there were errors scrolling by, there were too many lines and so I couldn't scroll back in the buffer. Is there something in particular I should look for (and a way to look for it, given the number of lines that scroll by)?

And in the meantime, I am trying to figure out how to chroot in to actually use pacman, and I found some of the guides confusing.

Am I correct that after booting into USB, I should:

1) mount what was formerly root to /mnt
2) mount my separate boot partition to /mnt/boot

In different places, it is unclear about what to do next. The wiki page on chroot says to then:

# cd /location/of/new/root
# mount -t proc proc proc/
# mount --rbind /sys sys/
# mount --rbind /dev dev/

But other pages that talk about fixing broken systems with chroot don't have these instructions or describe them slightly differently. Is it enough to just do the first steps before actually trying to fix things, or I do I need to deal with proc, sys, and dev (and maybe even run)?

In any case, once I mount things correctly, should I just chroot into /mnt and then try to update the system?

Last edited by slamhound (2018-01-25 23:08:28)

seth · 2018-01-25 23:07:09

Just redirect the output into a file (or less)

1) mount what was formerly root to /mnt
2) mount my separate boot partition to /mnt/boot

The wiki page on chroot says to then:

Do NOT chroot - assuming the system is FUBAR, you have to fix it offline (ie. using the binaries and libs from the install medium, just telling pacman what path to operate on)

slamhound · 2018-01-25 23:21:43

Okay, thanks for the help. I'm still not sure I'm getting the right output, and I'm definitely not sure what to look for. If I redirect the output to a file, the file doesn't include all the warnings (there are lots of entries, just not the lines labeled "warning". If I use "less" I can see the warnings, and there are many with (Modification time mismatch) or (Size mismatch), some (Symlink path mismatch) and some (Permissions mismatch). But these warnings are for many packages that were not just updated and haven't been in a while (as far as I can tell). So what should I be looking for?

loqs · 2018-01-25 23:40:51

You need to redirect both stderr and stdout

# pacman --root /mnt -Qkk &> output.txt

Then see the tip box in the section List_of_applications#Pastebin_clients to upload it from the console and post the link generated.

slamhound · 2018-01-26 00:03:08

Great, thanks so much. Here is the output: https://ptpb.pw/gn68

Again, I'm not sure which of the warnings are problematic and what I should do based on what is listed. Any advice about next steps is appreciated!

loqs · 2018-01-26 00:40:59

libutil-linux: 17 total files, 0 altered files

Did you reinstall libutil-linux?

awesome-scratchpad-git: no mtree file
deb2targz: no mtree file
emacs-color-theme: no mtree file
emacs-zenburn-git: no mtree file
fitbitd-git: no mtree file
geoclue-git: no mtree file
gtk-rezlooks-engine: no mtree file
gtk-theme-elegant-gtk: no mtree file
gtk2-theme-fawn: no mtree file
guisu: no mtree file
obdevicemenu: no mtree file
obsetlayout: no mtree file
openbox-fawn-theme: no mtree file
pianobar-git: no mtree file
pychrom: no mtree file
pytyle: no mtree file
squeezelite-git: no mtree file
squeezeslave: no mtree file
: no mtree file
xcompmgr-git: no mtree file
zeitgeist-datasources: no mtree file

These packages do not appear to have been created by a recent version of makepkg (meaning a version from the last few years) or it is just coincidence they are missing the mtree.
All the warnings related to R files pass but it should not be the cause of the current issue.
edit:
grammar missing are

Last edited by loqs (2018-01-26 00:41:39)

slamhound · 2018-01-26 00:51:14

Thanks...no, I haven't tried reinstalling anything yet. I still wasn't sure from what has been said before whether I should be reinstalling any packages with chroot or without chroot using the instructions here: https://wiki.archlinux.org/index.php/Pa … an_upgrade (from Seth's comments). For the latter, I did try getting everything ready to install packages this way, but got an error when I ran this command:

mount -t {proc,sysfs} /dev/sdaX {/mnt/proc, /mnt/sys}

(it said parsing error after '}'). I wasn't sure whether mounting proc and sys is necessary to install packages this way.

Also, whichever option I use, should I just install libutil-linux, or try to update the whole system, as the original pacman log seemed to suggest something failed while installing linux?

After more googling, it seems that a lot of people solved similar problems by chrooting from USB and then simply updating. But I'm not sure whether there is something about my situation that makes that a bad idea.

Anyway, still want to know whether (a) I should install packages or update using chroot or (b) without using chroot using the method in the link above, and if this latter option, whether I should mount proc and sys (and how to do so given the error running that command).

Oh, and yes, I think those are some really old packages that I don't think I use anymore and could get rid of.

Last edited by slamhound (2018-01-26 00:51:46)

slamhound · 2018-01-26 03:14:47

Okay, just decided to go ahead and chroot in and update the system. Reinstalled a few packages, too, where it looked like there had been errors, too, just in case. Tried rebooting and everything seems to have worked. So this looks solved; thanks for the help!

Arch Linux

#1 2018-01-25 20:50:40

[SOLVED] Can't boot, libmount.so.1 not found

#2 2018-01-25 20:56:13

Re: [SOLVED] Can't boot, libmount.so.1 not found

#3 2018-01-25 22:22:28

Re: [SOLVED] Can't boot, libmount.so.1 not found

#4 2018-01-25 22:29:46

Re: [SOLVED] Can't boot, libmount.so.1 not found

#5 2018-01-25 23:01:56

Re: [SOLVED] Can't boot, libmount.so.1 not found

#6 2018-01-25 23:07:09

Re: [SOLVED] Can't boot, libmount.so.1 not found

#7 2018-01-25 23:21:43

Re: [SOLVED] Can't boot, libmount.so.1 not found

#8 2018-01-25 23:40:51

Re: [SOLVED] Can't boot, libmount.so.1 not found

#9 2018-01-26 00:03:08

Re: [SOLVED] Can't boot, libmount.so.1 not found

#10 2018-01-26 00:40:59

Re: [SOLVED] Can't boot, libmount.so.1 not found

#11 2018-01-26 00:51:14

Re: [SOLVED] Can't boot, libmount.so.1 not found

#12 2018-01-26 03:14:47

Re: [SOLVED] Can't boot, libmount.so.1 not found

Board footer