[solved] glibc issue destroyed my system

rangalo · 2012-07-30 09:43:57

Hello,

I followed the article here
http://www.archlinux.org/news/the-lib-d … a-symlink/

Didn't work for me.

Then I followed an advice in the glibc thread here

https://bbs.archlinux.org/viewtopic.php … 3#p1136253

and did following.

pacman -Rdd glibc

This has rendered my system useless. All of the commands are not found including pacman.

I don't want to reinstall arch. Is there any way to recover ?

Last edited by rangalo (2012-08-04 22:46:12)

Trilby · 2012-07-30 11:21:30

First, glibc didn't destroy your system. Perhaps you did.

Second, "Didn't work" is not very informative. Especially when there is a link to a wiki page to follow if the basic steps "didn't work" - it sounds like you only read part of the recommended steps. You should have followed that rather following a suggestion of the forum that doesn't even look like it worked for the person who suggested it.

Third, the spot you now find yourself in has been faced my many other users (who also didn't read the wiki entry). The thread that you must have only read part of (sensing a theme here) describes the options that remain available to you.

framas · 2012-07-30 11:39:59

Hi,
you can boot from archlinux cd usb stick, mount your root partition and install your glibc with the options -r, --root <path> and -b, --dbpath <path> pointing to your mounted root partition and your pacman db path in the root partition. Just take a look into the pacman manpage.
Then your system should work again.

rangalo · 2012-07-30 12:21:13

@Trilby,

I didn't say glibc destroyed it, but the issue related to it, which doesn't have a fix that works for all. If you want to know who typed the commands, I already wrote that I did it.

Didn't work means in the same way for many other users, also have complained in the 15 page long (and counting) thread. The second command doesn't upgrade the glibc. I thought the reason why it didn't work is not important in fixing the current problem, is it ?

And yes, the option and possible solution is also described somewhere in the thread where I read the fix, but unfortunately it is not so clear and after already making a mistake, I didn't want to further complicate the things by following the 'broken' thread. This is the reason I asked the questions clearly in a separate thread to get the clear and to the point answer.

@framas:
Thanks for the tip, I will try to follow the man pages and write back if I have some questions.

Last edited by rangalo (2012-07-30 12:22:56)

tomk · 2012-07-30 12:34:04

rangalo wrote:

Didn't work means in the same way for many other users, also have complained in the 15 page long (and counting) thread.

This is no better than your original "Didn't work". Nobody can help you without details.

The steps laid out here work - you just have to pay attention to what you're doing. You will notice that 'pacman -Rdd glibc' is not one of those steps, and to be brutally honest, your expectation that your system should work after you've done that means you should not be using Arch.

And before you say it - yes, I know I'm not helping with your current self-inflicted screw-up. This post is intended to improve your overall approach to Arch (doubtful, but I guess I'm an optimist).

2ManyDogs · 2012-07-30 12:37:34

rangalo wrote:

I didn't say glibc destroyed it

I think you edited the title of your thread. When I first looked at it, I'm pretty sure it said "glibc destroyed my system."

Didn't work means in the same way for many other users, also have complained in the 15 page long (and counting) thread. The second command doesn't upgrade the glibc. I thought the reason why it didn't work is not important in fixing the current problem, is it ?

The reason is not important (the reason is that you did something wrong), but any error messages you received and anything you did to try to fix it before posting is very important to anyone trying to help you.

And yes, the option and possible solution is also described somewhere in the thread where I read the fix, but unfortunately it is not so clear and after already making a mistake, I didn't want to further complicate the things by following the 'broken' thread. This is the reason I asked the questions clearly in a separate thread to get the clear and to the point answer.

Creating a new thread is not a good way to get a clear and to the point answer; it's a good way to get your thread closed for duplicating other threads.

Last edited by 2ManyDogs (2012-07-30 12:53:59)

rangalo · 2012-07-30 12:54:55

@Tomk
The intention in not writing the error message in post was that I didn't think it was important. If you think it is useful, I can paste that, but anyway you don't want to help fix the current issue. I have been using archlinux for last 2 and half years. I have posted minimum number of problems often got real good help. I don't need you or anybody else for that matter to improve my approach to anything leave aside arch. I would rather stay with the thread subject and not diverge.

@2ManyDogs: You cannot tell me that I am lying just for the sake of your stupid argument without any proof. I edited the post but, only to correct the links.

From the answer of @framas I can see that it is not a duplicate question. If somebody feels it is duplicate feel free to point to the correct and clear answer and close this one.

Last edited by rangalo (2012-07-30 12:57:21)

fsckd · 2012-07-30 14:11:51

moderator comment:
Guys, stop trying to assign blame. In this case it's bikeshedding.
rangalo, calm down and give us the error message. It will help us help you.

fsckd · 2012-07-30 14:13:32

rangalo wrote:

From the answer of @framas I can see that it is not a duplicate question. If somebody feels it is duplicate feel free to point to the correct and clear answer and close this one.

It's similar. Other people removed a part of glibc, the /lib directory. You removed all of glibc. The solution is the same. If you search the forums you'll see the many ways people solved it.

rangalo · 2012-07-30 14:21:00

@fsckd
current eror message: With any command including ls, packman

bash: <command>: <command> not found

Previously when I tried the solution described in the first link:

pacman -Syu --ignore glibc
then
pacman -Su
but the last command always gives me an error :
"error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
Errors occurred, no packages were upgraded."

When I tried:

cd /var/lib/pacman/local
egrep '^lib/' */files

I had following:

glibc-2.16.0-1/files:lib/
glibc-2.16.0-1/files:lib/ld-2.16.so
glibc-2.16.0-1/files:lib/ld-linux-x86-64.so.2
glibc-2.16.0-1/files:lib/libBrokenLocale-2.16.so
glibc-2.16.0-1/files:lib/libBrokenLocale.so.1
glibc-2.16.0-1/files:lib/libSegFault.so
glibc-2.16.0-1/files:lib/libanl-2.16.so
glibc-2.16.0-1/files:lib/libanl.so.1
glibc-2.16.0-1/files:lib/libc-2.16.so
glibc-2.16.0-1/files:lib/libc.so.6
glibc-2.16.0-1/files:lib/libcidn-2.16.so
glibc-2.16.0-1/files:lib/libcidn.so.1
glibc-2.16.0-1/files:lib/libcrypt-2.16.so
glibc-2.16.0-1/files:lib/libcrypt.so.1
glibc-2.16.0-1/files:lib/libdl-2.16.so
glibc-2.16.0-1/files:lib/libdl.so.2
glibc-2.16.0-1/files:lib/libm-2.16.so
glibc-2.16.0-1/files:lib/libm.so.6
glibc-2.16.0-1/files:lib/libmemusage.so
glibc-2.16.0-1/files:lib/libnsl-2.16.so
glibc-2.16.0-1/files:lib/libnsl.so.1
glibc-2.16.0-1/files:lib/libnss_compat-2.16.so
glibc-2.16.0-1/files:lib/libnss_compat.so.2
glibc-2.16.0-1/files:lib/libnss_db-2.16.so
glibc-2.16.0-1/files:lib/libnss_db.so.2
glibc-2.16.0-1/files:lib/libnss_dns-2.16.so
glibc-2.16.0-1/files:lib/libnss_dns.so.2
glibc-2.16.0-1/files:lib/libnss_files-2.16.so
glibc-2.16.0-1/files:lib/libnss_files.so.2
glibc-2.16.0-1/files:lib/libnss_hesiod-2.16.so
glibc-2.16.0-1/files:lib/libnss_hesiod.so.2
glibc-2.16.0-1/files:lib/libnss_nis-2.16.so
glibc-2.16.0-1/files:lib/libnss_nis.so.2
glibc-2.16.0-1/files:lib/libnss_nisplus-2.16.so
glibc-2.16.0-1/files:lib/libnss_nisplus.so.2
glibc-2.16.0-1/files:lib/libpcprofile.so
glibc-2.16.0-1/files:lib/libpthread-2.16.so
glibc-2.16.0-1/files:lib/libpthread.so.0
glibc-2.16.0-1/files:lib/libresolv-2.16.so
glibc-2.16.0-1/files:lib/libresolv.so.2
glibc-2.16.0-1/files:lib/librt-2.16.so
glibc-2.16.0-1/files:lib/librt.so.1
glibc-2.16.0-1/files:lib/libthread_db-1.0.so
glibc-2.16.0-1/files:lib/libthread_db.so.1
glibc-2.16.0-1/files:lib/libutil-2.16.so
glibc-2.16.0-1/files:lib/libutil.so.1

So, I removed the glibc-2.16.0-1 with the command:

pacman -Rdd glibc

And now the first error message. The system is currently unusable.

@fsckd Thanks for the intervention and help.

rangalo · 2012-07-30 14:23:49

fsckd wrote:

It's similar. Other people removed a part of glibc, the /lib directory. You removed all of glibc. The solution is the same. If you search the forums you'll see the many ways people solved it.

Could you point me to one of the solutions. If possible showing commands. Because in the long thread it is really confusing, some times they say with live cd and sometimes doing something with the grub prompt.

Barrucadu · 2012-07-30 15:18:50

Have you considered doing the same solution as most other people in that thread?

Boot a livecd. Mount your partitions. Upgrade everything but glibc. Upgrade (well, reinstall in your case) glibc.

rangalo · 2012-07-30 15:44:33

@Barrucadu,
Thiis is what I want to try now. Please confirm the steps if they will work and correct if something is wrong.

1. Boot with the live cd.

2. Mount partitions:

mount /dev/sda5 /mnt/oldroot
mount /dev/sda5 /mnt/oldhome

3. chroot to oldroot (do I need this ?)

OR

3. use pacman with options suggested by @framas here

https://bbs.archlinux.org/viewtopic.php … 6#p1138926

3a. pacman <some magic options> -Syyu
3b. pacman <the same magic options as above>  -Su glibc

4. reboot the normal system.

Last edited by rangalo (2012-07-30 15:45:34)

framas · 2012-07-30 21:06:39

@rangalo
Maybe I had forgot to say that I accidently did the same as you and broke my system ;-)
With my solution I got back a running system.

rangalo · 2012-08-04 22:45:50

Hi,

Thanks all for help.

I am writing this from my recovered Arch now.

I followed exactly the steps mentioned here

https://bbs.archlinux.org/viewtopic.php … 1#p1139021

After that I rebooted and was in a state where nothing was working and was dropped to rootfs no keyboard no filesystem.

Then followed the advice here
https://bbs.archlinux.org/viewtopic.php … 4#p1140944

Everything OK now.

Following steps as commands, if some one has the same issue.

1. boot with live cd/usb

2. mount filesystem.

mkdir /mnt/oldroot
mount /dev/<rootpartition> /mnt/oldroot

3. mount /proc, /dev and /sys

mount -o bind /proc /mnt/oldroot/proc
mount -o bind /dev /mnt/oldroot/dev
mount -o bind /sys  /mnt/oldroot/sys

4. chroot to the oldroot

chroot /mnt/oldroot

5. run

mkinitcpio -p linux

6. reboot to the original system

Arch Linux

#1 2012-07-30 09:43:57

[solved] glibc issue destroyed my system

#2 2012-07-30 11:21:30

Re: [solved] glibc issue destroyed my system

#3 2012-07-30 11:39:59

Re: [solved] glibc issue destroyed my system

#4 2012-07-30 12:21:13

Re: [solved] glibc issue destroyed my system

#5 2012-07-30 12:34:04

Re: [solved] glibc issue destroyed my system

#6 2012-07-30 12:37:34

Re: [solved] glibc issue destroyed my system

#7 2012-07-30 12:54:55

Re: [solved] glibc issue destroyed my system

#8 2012-07-30 14:11:51

Re: [solved] glibc issue destroyed my system

#9 2012-07-30 14:13:32

Re: [solved] glibc issue destroyed my system

#10 2012-07-30 14:21:00

Re: [solved] glibc issue destroyed my system

#11 2012-07-30 14:23:49

Re: [solved] glibc issue destroyed my system

#12 2012-07-30 15:18:50

Re: [solved] glibc issue destroyed my system

#13 2012-07-30 15:44:33

Re: [solved] glibc issue destroyed my system

#14 2012-07-30 21:06:39

Re: [solved] glibc issue destroyed my system

#15 2012-08-04 22:45:50

Re: [solved] glibc issue destroyed my system

Board footer