System broken after /lib glibc issue - filesystem check failed?

beachcoder · 2012-07-18 22:58:28

hi, I have now got by system a little bit back to boot after following the steps of https://bbs.archlinux.org/viewtopic.php … 1#p1127251.

Now I get this state and I don't know what to do now:

http://s13.postimage.org/xok6qmc06/IMG_ … 005209.jpg

Can anyone help me?

Last edited by beachcoder (2012-07-18 23:19:54)

beachcoder · 2012-07-18 22:59:39

I did an fsck on a dismounted /dev/sda1 but still get the same result.

cfr · 2012-07-19 00:36:57

You mean fsck can't repair the errors? Or that you've cleared those errors but still get dropped to a root shell?

Did you check what was in /lib before forcibly removing it? (If that's what you did - I'm not at all clear about what you did you get into trouble or what exactly you tried to get out of it.)

beachcoder · 2012-07-19 05:36:59

hi, yes thats right. fsck on /dev/sda1 reports no errors.
well I think that I'm unable to restore the original /lib directory. It is now a symlink to /usr/lib. One thing that may be wrong is my /lib64 link, I deleted it yesterday and now it also is a symlink to /usr/lib may this be the problem?

I can't figure out any other reason.
Or maybe am I doing the fsck call wrong? fsck tells me that it does a read-only check on /dev/mapper/root - and /dev/sda1, my boot partition is mounted as /media/usbhd-sda1 in the maintenance shell... this looks a little bit strange.

Last edited by beachcoder (2012-07-19 06:00:17)

beachcoder · 2012-07-19 06:30:31

Ok, I am now able to boot into my system after adding the option fastboot to the kernel command-line at grub.
Booting without this option will always bring me into the maintenance shell. With fastboot, everything seems to run normal, also with X.

Do you have an idea what this could mean? I get these messages every time before the filesystem checks are performed (please do also look at the image above).

[   33.806994] systemd-udevd[441]: failed to execute '/bin/grep' '/bin/grep -q ' /dev/sda3 ' /proc/self/mountinfo': No such file or directory
[   33.819267] systemd-udevd[445]: failed to execute '/bin/grep' '/bin/grep -q ' /dev/sdb1 ' /proc/self/mountinfo': No such file or directory
[   34.040799] systemd-udevd[463]: failed to execute '/bin/grep' '/bin/grep -q ' /dev/sda2 ' /proc/self/mountinfo': No such file or directory

It always halts with the message that /dev/sda1, my boot-partiition, could not be checked.

Any idea?

Allan · 2012-07-19 06:42:18

It means the symlink to /usr/bin/grep in /bin is no longer there...

Edit: make sure your systemd package is fully up to date.

beachcoder · 2012-07-19 09:03:21

Allan wrote:

It means the symlink to /usr/bin/grep in /bin is no longer there...
Edit: make sure your systemd package is fully up to date.

hello, I've reinstalled systemd now but the problem still exists. I think it has something to do with the check issue of the filesystems. booting the system still is impossible without fastboot option.

falconindy · 2012-07-19 12:46:49

A better question would be: why are you using grep in a udev rule?

Arch Linux

#1 2012-07-18 22:58:28

System broken after /lib glibc issue - filesystem check failed?

#2 2012-07-18 22:59:39

Re: System broken after /lib glibc issue - filesystem check failed?

#3 2012-07-19 00:36:57

Re: System broken after /lib glibc issue - filesystem check failed?

#4 2012-07-19 05:36:59

Re: System broken after /lib glibc issue - filesystem check failed?

#5 2012-07-19 06:30:31

Re: System broken after /lib glibc issue - filesystem check failed?

#6 2012-07-19 06:42:18

Re: System broken after /lib glibc issue - filesystem check failed?

#7 2012-07-19 09:03:21

Re: System broken after /lib glibc issue - filesystem check failed?

#8 2012-07-19 12:46:49

Re: System broken after /lib glibc issue - filesystem check failed?

Board footer