How to install missing packages in rescue mode

mohdsuboor23 · 10-28-2010, 08:23 AM

hi everyone my OS FC13 is missing some packages. iwant to reinstall that but my network cards are not enable so i want to do it in rescue mode.
could any one telme how to do that in rescue mode.i know i will reach till chroot /mnt/sysimage.
after that if i install any package then if i reboot my system will those packages will be availabe in real OS.IF NOT HOW SHOULD I INSTALL PACKAGES.PLZ HELP ME.

soppy · 10-28-2010, 08:57 AM

I'm assuming you're using Fedora 13. correct? Can you be anymore specific on what packages are missing or what the problem is? You might be able to pop in the Fedora 13 disk, run the installer from the disk in the LiveCD environment and Anaconda will give you an option to fix your system. However, if you can tell us what the problem is, we might be able to avoid doing so.

mohdsuboor23 · 10-30-2010, 04:45 AM

Quote:

Originally Posted by soppy

I'm assuming
you're using Fedora 13. correct? Can you be anymore specific on what packages are missing or what the problem is? You might be able to pop in the Fedora 13 disk, run the installer from the disk in the LiveCD environment and Anaconda will give you an option to fix your system. However, if you can tell us what the problem is, we might be able to avoid doing so.

I really thank you for ur reply.Actually our backup servers network cards are not activated.when im typing any command its giving the error /etc/sysconfig/network-scripts/ifup-eth:/ sbin/arping :/lib/ld-linux.so 2:bad ELF interpreter: No such file or directory.when im typing ifconfig no ip address is showing.no usb nor hard drives are getting mounted.so i checked that glibc.i686 package is missing.in /lib directory most of the files are missing.SO COULD U PLEASE TELME HOW TO SHOULD I MAKE MY SERVER RUNNING.WHT SHOULD I DO NOW THIS IS FC 13 64BIT OS.ANY HELP APPRECIATED PLZ HELPME.

unSpawn · 10-30-2010, 06:35 AM

As you have addressed your problem in three consecutive threads (and failed to timely post follow-up replies) I strongly suggest you cut your losses, ditch your repair efforts and just re-install Fedora from scratch. You now know from experience why backups are important, that you should not mess with some things (or mess with them in the way you did) and that this problem is not a problem with Linux or Fedora but with the wetware part of the equation. Losing your files may be a hard lesson but the upside of that is that (usually) important lessons like that only need to be learned once.

mohdsuboor23 · 10-31-2010, 01:21 AM

Quote:

Originally Posted by unSpawn

As you have addressed your problem in three consecutive threads (and failed to timely post follow-up replies) I strongly suggest you cut your losses, ditch your repair efforts and just re-install Fedora from scratch. You now know from experience why backups are important, that you should not mess with some things (or mess with them in the way you did) and that this problem is not a problem with Linux or Fedora but with the wetware part of the equation. Losing your files may be a hard lesson but the upside of that is that (usually) important lessons like that only need to be learned once.

Dear Moderator.I have posted on 3 different threads because all three all completely different issues.binary error is different from /lib-so file error so thats y i have put question on different threads.anyways thanks 4 ur support.im insisiting on repairing because data is replicating through DRBD.its bit difficult to reconfigure drbd.could u please telme if i format hda on which OS is there.will it make any effect on other harddrives such as hdb,hdc,hdd,hde.these all drives are replicating data drives from server1.
This community is very helpfull to people so please helpme as well.

unSpawn · 10-31-2010, 06:07 AM

Quote:

Originally Posted by mohdsuboor23

I have posted on 3 different threads because all three all completely different issues.

Are you really certain they are different?..

Quote:

Originally Posted by mohdsuboor23

im insisiting on repairing

So you are. Let's see:
0. Boot the "victim" with the Fedora 13 rescue CD, do not chroot to the mounted system to rescue, then generate a list of packages containing missing files by running something like 'rpm --dbpath /mnt/sysrescue/var/lib/rpm --root /mnt/sysrescue -qa --qf '%{NAME}-%{VERSION}.%{RELEASE}\n'|grep missing > /tmp/missing.log' (adjust point point names if necessary). Note this asserts you just deleted files, meaning the RPMDB on the "victim" is intact.
1. On another system that is connected to a network use the list of packages to retrieve the exact versions of the packages you need from the installer DVD or online repositories.
2. Expand each package with something like 'mkdir /tmp/restore; cd /tmp/restore; rpm2cpio /path/to/package.rpm|cpio -idmv'.
3. Copy contents of /tmp/restore to the "victim", check if all files and symbolic links are in place and if all SELinux contexts are as they should be (compare with a similar operational machine?) then see if it will reboot.

* If you can not use the network or attached external storage to your system to copy files over then if you have access to the "victim" machine you could remove the hard disk and attach it to a working machine. If the "victim" machine is in a remote location and no support is available to perform tasks for you then you are SOL (Severely Out of Luck, to put it politely) and my previous suggestion remains. Sure the system may be a b*tch to re-install and re-configure but if you left yourself without options then what can you do?..

mohdsuboor23 · 10-31-2010, 07:33 AM

Quote:

Originally Posted by unSpawn

Are you really certain they are different?..

So you are. Let's see:
0. Boot the "victim" with the Fedora 13 rescue CD, do not chroot to the mounted system to rescue, then generate a list of packages containing missing files by running something like 'rpm --dbpath /mnt/sysrescue/var/lib/rpm --root /mnt/sysrescue -qa --qf '%{NAME}-%{VERSION}.%{RELEASE}\n'|grep missing > /tmp/missing.log' (adjust point point names if necessary). Note this asserts you just deleted files, meaning the RPMDB on the "victim" is intact.
1. On another system that is connected to a network use the list of packages to retrieve the exact versions of the packages you need from the installer DVD or online repositories.
2. Expand each package with something like 'mkdir /tmp/restore; cd /tmp/restore; rpm2cpio /path/to/package.rpm|cpio -idmv'.
3. Copy contents of /tmp/restore to the "victim", check if all files and symbolic links are in place and if all SELinux contexts are as they should be (compare with a similar operational machine?) then see if it will reboot.

* If you can not use the network or attached external storage to your system to copy files over then if you have access to the "victim" machine you could remove the hard disk and attach it to a working machine. If the "victim" machine is in a remote location and no support is available to perform tasks for you then you are SOL (Severely Out of Luck, to put it politely) and my previous suggestion remains. Sure the system may be a b*tch to re-install and re-configure but if you left yourself without options then what can you do?..

i really thank you for ur unconditional support.actually there was a bug due to which my usbcdrom was not detecting the drives on fc12 but now i have inserted sata cdrom so its working now.
i have installed the missing packages but when i reboot its still missing some packages or throughing errors like
1 service network manager daemon failed error while loading shared-libraries:libnm-glib.so.2 cannot open shared object file:no such file or directory.
2. service HAL daemon failed error while loading shared-libraries:libdbus-glib.so.2 cannot open shared object file:no such file or directory.
3.service abrt daemon failed error cannot open shared object files.
SO COULD PLZ ANYONE TELME WHO TO OVERCOME FROM THIS.any help greatly appreciated.

unSpawn · 10-31-2010, 08:22 AM

If the libraries aren't in the cache (example: 'ldconfig -p|grep dbus-glib') then repeat your search for missing packages. (NetworkManager-glib*.rpm, dbus-glib*.rpm).

mohdsuboor23 · 10-31-2010, 09:06 AM

Quote:

Originally Posted by unSpawn

If the libraries aren't in the cache (example: 'ldconfig -p|grep dbus-glib') then repeat your search for missing packages. (NetworkManager-glib*.rpm, dbus-glib*.rpm).

Thanks 4 ur reply.could u please telme if i update my kernel will this solve the issue.i just to do update to all packages.could u plz telme any steps to update all the packages.i have checked all above packages seems to be present.This are my last effort to reinstall plz helpme.i want to do update all packages with yum command.waiting 4 ur reply

unSpawn · 10-31-2010, 10:34 AM

Quote:

Originally Posted by mohdsuboor23

could u please telme if i update my kernel will this solve the issue.

Updating the kernel doesn't solve library problems.

Quote:

Originally Posted by mohdsuboor23

i just to do update to all packages.

If your system is connected to the network and no essential parts have gone missing then running 'yum -y update' should update all packages.