Fail in upgrading glibc RPM package

Fail in upgrading glibc RPM package

Post by Fung Wai Keun » Wed, 06 Sep 2000 19:09:08



Hi all,

Help!  My Pc is running RedHat 5.2.  I downloaded the updated glibc RPM
package for upgrade, but I got the following error.


glibc                       ###unpacking of archive failed on file
/lib/libc-2.0.7.so: cpio: copy
glibc-debug
##################################################
glibc-devel
##################################################
/bin/sh: error in loading shared libraries
libc.so.6: cannot open shared object file: No such file or directory
execution of glibc-devel-2.0.7-29.2 script failed, exit status 127
glibc-profile
##################################################

After that, I think my libc.so.6 has been corrupted.  I can't do
anything with the system, even ls.  What can I do now to
restore the my libc.so.6.

Please help.

Thanks in advance.

--

Regards,
Wai Keung, Fung

Department of Automation and Computer Aided Engineering,
The Chinese University of Hong Kong,
Shatin, N.T.,
Hong Kong

Tel: (852)26098056      Fax: (852)26036002

 
 
 

Fail in upgrading glibc RPM package

Post by Fung Wai Keun » Wed, 06 Sep 2000 19:24:38


Hi all,

after deleting the glibc-2.0.7-29.2.i386.rpm package (the upgrade rpm), I
try to reinstall it but fail with the following error


installing package glibc-2.0.7-29.2 needs 5Mb on the / filesystem

What does it mean?


: Hi all,

: Help!  My Pc is running RedHat 5.2.  I downloaded the updated glibc RPM
: package for upgrade, but I got the following error.


: glibc                       ###unpacking of archive failed on file
: /lib/libc-2.0.7.so: cpio: copy
: glibc-debug
: ##################################################
: glibc-devel
: ##################################################
: /bin/sh: error in loading shared libraries
: libc.so.6: cannot open shared object file: No such file or directory
: execution of glibc-devel-2.0.7-29.2 script failed, exit status 127
: glibc-profile
: ##################################################

: After that, I think my libc.so.6 has been corrupted.  I can't do
: anything with the system, even ls.  What can I do now to
: restore the my libc.so.6.

: Please help.

: Thanks in advance.

: --

: Regards,
: Wai Keung, Fung

: Department of Automation and Computer Aided Engineering,
: The Chinese University of Hong Kong,
: Shatin, N.T.,
: Hong Kong

: Tel: (852)26098056    Fax: (852)26036002

--

Regards,
Wai Keung, Fung

Department of Automation and Computer Aided Engineering,
The Chinese University of Hong Kong,
Shatin, N.T.,
Hong Kong

Tel: (852)26098056      Fax: (852)26036002


 
 
 

Fail in upgrading glibc RPM package

Post by Allin Cottrel » Thu, 07 Sep 2000 11:01:43



> after deleting the glibc-2.0.7-29.2.i386.rpm package (the upgrade rpm), I
> try to reinstall it but fail with the following error


> installing package glibc-2.0.7-29.2 needs 5Mb on the / filesystem

> What does it mean?

It means you need at least 5 megabytes of free space on your hard
disk to install this rpm, and you don't have this.  You'd better
delete some inessential stuff since you're not going anywhere
without glibc.

Allin Cottrell

 
 
 

Fail in upgrading glibc RPM package

Post by Fung Wai Keun » Thu, 07 Sep 2000 13:29:42


Hi all,

:> after deleting the glibc-2.0.7-29.2.i386.rpm package (the upgrade rpm), I
:> try to reinstall it but fail with the following error
:>

:> installing package glibc-2.0.7-29.2 needs 5Mb on the / filesystem
:>
:> What does it mean?

: It means you need at least 5 megabytes of free space on your hard
: disk to install this rpm, and you don't have this.  You'd better
: delete some inessential stuff since you're not going anywhere
: without glibc.

In rescue mode, I cannot delete any file.  I have the updated glibc-*
packages in my /tmp directory.  How do I re-install the glibc-* packages
so that my PC can boot up nromally?

Thanks in advance.

: Allin Cottrell

--

Regards,
Wai Keung, Fung

Department of Automation and Computer Aided Engineering,
The Chinese University of Hong Kong,
Shatin, N.T.,
Hong Kong

Tel: (852)26098056      Fax: (852)26036002

 
 
 

Fail in upgrading glibc RPM package

Post by Peter T. Breue » Thu, 07 Sep 2000 15:00:47



: :> installing package glibc-2.0.7-29.2 needs 5Mb on the / filesystem

: : It means you need at least 5 megabytes of free space on your hard
: : disk to install this rpm, and you don't have this.  You'd better
: : delete some inessential stuff since you're not going anywhere
: : without glibc.

: In rescue mode, I cannot delete any file.  I have the updated glibc-*
: packages in my /tmp directory.  How do I re-install the glibc-* packages
: so that my PC can boot up nromally?

Learn to delete files while in rescue mode? What is the basis of your
inability? A readonly filesystem? Remount it readwrite!

Why do you want to reinstall glibc, btw?  You must already have glibc
even to be able to enter rescue mode, so surely all you want to do is
remove the mess you added.  No? Is that what you are asking about?

And do you really want glibc 2.0? That implies that you are on an old
redhat system, I believe (that is the prerelease glibc2).

Personally I would do a delicate operation like replacing libc by hand,
not using rpms. It's simple enough. But the simplest method does
require space to have, temporarily, two libc's on /.

Peter

 
 
 

Fail in upgrading glibc RPM package

Post by Fung Wai Keun » Thu, 07 Sep 2000 16:05:28


Hi all,


: Learn to delete files while in rescue mode? What is the basis of your
: inability? A readonly filesystem? Remount it readwrite!
: Why do you want to reinstall glibc, btw?  You must already have glibc
: even to be able to enter rescue mode, so surely all you want to do is
: remove the mess you added.  No? Is that what you are asking about?

I boot the PC up with the boot disk and rescue disk.  Is it possible to
just copy the libc located in the ramdisk to my HD /lib?

: And do you really want glibc 2.0? That implies that you are on an old
: redhat system, I believe (that is the prerelease glibc2).

: Personally I would do a delicate operation like replacing libc by hand,
: not using rpms. It's simple enough. But the simplest method does
: require space to have, temporarily, two libc's on /.

: Peter

--

Regards,
Wai Keung, Fung

Department of Automation and Computer Aided Engineering,
The Chinese University of Hong Kong,
Shatin, N.T.,
Hong Kong

Tel: (852)26098056      Fax: (852)26036002

 
 
 

Fail in upgrading glibc RPM package

Post by Peter T. Breue » Thu, 07 Sep 2000 17:15:30



: Hi all,


: : Learn to delete files while in rescue mode? What is the basis of your
: : inability? A readonly filesystem? Remount it readwrite!
: : Why do you want to reinstall glibc, btw?  You must already have glibc
: : even to be able to enter rescue mode, so surely all you want to do is
: : remove the mess you added.  No? Is that what you are asking about?

: I boot the PC up with the boot disk and rescue disk.  Is it possible to
: just copy the libc located in the ramdisk to my HD /lib?

Sure. But why would you want to! I imagine that the libc in the initrd
is highly modified and unsuitable for use on an installed system. Why
not just extract the libc from a rpm or tgz and put it in place?

You haven't said what is stopping you deleting files on the
harddisk while running from the rescue bootdisk. I suggested what
it might be above, but you didn't comment. Can you clarify, please?

: : Personally I would do a delicate operation like replacing libc by hand,
: : not using rpms. It's simple enough. But the simplest method does
: : require space to have, temporarily, two libc's on /.

Peter

 
 
 

Fail in upgrading glibc RPM package

Post by Fung Wai Keun » Fri, 08 Sep 2000 16:52:56


Hi,

: Sure. But why would you want to! I imagine that the libc in the initrd
: is highly modified and unsuitable for use on an installed system. Why
: not just extract the libc from a rpm or tgz and put it in place?

I have a problem in copying useful libc into the PC.  I only have floppy
installed in my PC, no CDROM and any other I/O peripheral device
connected.  However, floppy is not supported in the rescue mode and no
/dev/fd0 is created in /dev.  How to copy the required files into my PC?

: You haven't said what is stopping you deleting files on the
: harddisk while running from the rescue bootdisk. I suggested what
: it might be above, but you didn't comment. Can you clarify, please?

After mounting the filesystems with read-write access, the problem is
solved.

--

Regards,
Wai Keung, Fung

Department of Automation and Computer Aided Engineering,
The Chinese University of Hong Kong,
Shatin, N.T.,
Hong Kong

Tel: (852)26098056      Fax: (852)26036002

 
 
 

Fail in upgrading glibc RPM package

Post by Peter T. Breue » Fri, 08 Sep 2000 17:36:08



: : Sure. But why would you want to! I imagine that the libc in the initrd
: : is highly modified and unsuitable for use on an installed system. Why
: : not just extract the libc from a rpm or tgz and put it in place?

: I have a problem in copying useful libc into the PC.  I only have floppy
: installed in my PC, no CDROM and any other I/O peripheral device
: connected.  However, floppy is not supported in the rescue mode and no

Yes, floppy is supported! You booted from it (or are running on a ramfs
loaded from it) so you know that!

: /dev/fd0 is created in /dev.  How to copy the required files into my PC?

It probably appears when you need it, if you are using devfs.

If not, the answer is: use a different rescue disk or dump it in the dos
partition using a dos boot disk.

Peter

 
 
 

Fail in upgrading glibc RPM package

Post by Fung Wai Keun » Fri, 08 Sep 2000 19:30:57


Hi,

: : I have a problem in copying useful libc into the PC.  I only have floppy
: : installed in my PC, no CDROM and any other I/O peripheral device
: : connected.  However, floppy is not supported in the rescue mode and no

: Yes, floppy is supported! You booted from it (or are running on a ramfs
: loaded from it) so you know that!

I can't mount my floppy!!  Even the file /dev/fd0 doesn't exist.  After I
creat it with mknod and mount floppy, I get

bash# mount /mnt/floppy
EXT2-fs: 02:00: couldn't mount because of unsupported optional features.
mount: wrong fs type, bad option, bad superblock on /dev/fd0,
        or too many mounted file system.

But, I can find an /dev/fd0 entry in /etc/fstab.

: : /dev/fd0 is created in /dev.  How to copy the required files into my PC?

: It probably appears when you need it, if you are using devfs.

What is devfs?

: If not, the answer is: use a different rescue disk or dump it in the dos
: partition using a dos boot disk.

I only have linux partitions.

: Peter

--

Regards,
Wai Keung, Fung

Department of Automation and Computer Aided Engineering,
The Chinese University of Hong Kong,
Shatin, N.T.,
Hong Kong

Tel: (852)26098056      Fax: (852)26036002

 
 
 

Fail in upgrading glibc RPM package

Post by Peter T. Breue » Fri, 08 Sep 2000 22:11:29



: I can't mount my floppy!!  Even the file /dev/fd0 doesn't exist.  After I
: creat it with mknod and mount floppy, I get

: bash# mount /mnt/floppy

Wrong command.  Use

   mkdir -p /mnt/floppyA
   mount -t vfat /dev/fd0 /mnt/floppyA

: EXT2-fs: 02:00: couldn't mount because of unsupported optional features.

You are trying to load an ext2fs. Don't. Use vfat. And check that the
floppy is not already in use. Read your kernel messages in the syslog.

The error comes from the fs search, apparantly, so you know your floppy
is there. Be explicit about the file system type.

: But, I can find an /dev/fd0 entry in /etc/fstab.

And what does it say? If it's for ext2fs, change it (or better, ignore
it, as above).

: : It probably appears when you need it, if you are using devfs.

: What is devfs?

automagical /dev directory.

: : If not, the answer is: use a different rescue disk or dump it in the dos
: : partition using a dos boot disk.

: I only have linux partitions.

So use a different rescue disk.

Or load a linux partition reader/writer on your dos floppy. There are
plenty out there. The "ltools" spring to mind.

And please give us more data.  I can't read the syslog from here!  It
strikes me that you are giving the wrong parameters to the rescue disk,
for example, which may result in your floppy device being used as the
root fs. You don't want that at all!

Peter

 
 
 

Fail in upgrading glibc RPM package

Post by Fung Wai Keun » Sun, 10 Sep 2000 00:14:46


Hi all,

I finally have my libc upgraded.  Thank you very much for all your help.

: : I can't mount my floppy!!  Even the file /dev/fd0 doesn't exist.  After I
: : creat it with mknod and mount floppy, I get

: : bash# mount /mnt/floppy

: Wrong command.  Use

:    mkdir -p /mnt/floppyA
:    mount -t vfat /dev/fd0 /mnt/floppyA

I use RedHat 6.o rescue disk.  /dev/fd0 exists in this version.

: : EXT2-fs: 02:00: couldn't mount because of unsupported optional features.

: You are trying to load an ext2fs. Don't. Use vfat. And check that the
: floppy is not already in use. Read your kernel messages in the syslog.

: The error comes from the fs search, apparantly, so you know your floppy
: is there. Be explicit about the file system type.

: : But, I can find an /dev/fd0 entry in /etc/fstab.

: And what does it say? If it's for ext2fs, change it (or better, ignore
: it, as above).

: : : It probably appears when you need it, if you are using devfs.

: : What is devfs?

: automagical /dev directory.

: : : If not, the answer is: use a different rescue disk or dump it in the dos
: : : partition using a dos boot disk.

: : I only have linux partitions.

: So use a different rescue disk.

: Or load a linux partition reader/writer on your dos floppy. There are
: plenty out there. The "ltools" spring to mind.

: And please give us more data.  I can't read the syslog from here!  It
: strikes me that you are giving the wrong parameters to the rescue disk,
: for example, which may result in your floppy device being used as the
: root fs. You don't want that at all!

: Peter

--

Regards,
Wai Keung, Fung

Department of Automation and Computer Aided Engineering,
The Chinese University of Hong Kong,
Shatin, N.T.,
Hong Kong

Tel: (852)26098056      Fax: (852)26036002

 
 
 

1. Trouble upgrading from glibc-2.1.2 to glibc-2.2.2 (rpm failed dependencies)

I know this problem has been batted around a few times, but I haven't
been able to find information to help me complete my upgrade
successfully.

I've got an old install of Redhat 5.1 which I have since partially
upgraded upon demand.  I currently want to install glibc-2.2.2, but am
having trouble upgrading it with rpm.  Installing a version greater
than 2.1.3 seems to comflict with rpm-4.0.

#root:# rpm -i --test glibc-2.2.2-10.i386.rpm
error: failed dependencies:
        glibc-common = 2.2.2-10 is needed by glibc-2.2.2-10
        glibc > 2.1.3 conflicts with rpm-4.0-6x

If I try to upgrade to a newer version of rpm (ie: rpm-4.0.3), I get
dependency errors asking for a newer version of the glibc library.

#root:# rpm -U --test rpm-4.0.3-1.04.i386.rpm
error: failed dependencies:
        popt = 1.6.3 is needed by rpm-4.0.3-1.04
        libbz2.so.1   is needed by rpm-4.0.3-1.04
        libc.so.6(GLIBC_2.1.3)   is needed by rpm-4.0.3-1.04
        libc.so.6(GLIBC_2.2)   is needed by rpm-4.0.3-1.04
        libc.so.6(GLIBC_2.2.3)   is needed by rpm-4.0.3-1.04

How am I supposed to install GLIBC_2.2 or GLIBC_2.2.3 if installing it
conflicts with my RPM package?  Is there a mid-step that I should be
doing first?  If I install the newer version of glibc, then I'll break
rpm, and won't be able to install the newer version of rpm4.0.3!  Am I
missing something?

Thanks for the help!

Eric

2. IP Masq problem with http

3. Please tel me how to update or upgrade the redhat glibc 2.1 rpm package

4. 2.5.40 (several issues): kernel BUG! at slab.c:1292, imm/ppa IOMega ZIP drivers modules ".o" not found, XFS won't link, depmod complains on

5. Upgrade redhat glibc 2.1 rpm package

6. message queue permission problem...

7. Problem with Gnome RPM - Failed to open /var/lib/rpm/packages.rpm

8. E4500 disable CPU board, swap CPU board, while in production

9. what to do when upgrading rpm packages has failed deps

10. failed to open //var/lib/rpm/packages.rpm

11. RedHat 3.0.3 Installation - FAILED TO OPEN "/mnt/var/lib/rpm/packages.rpm"

12. rpm upgraded - kpackage won't read packages.rpm

13. RPM Package install failed: script execution failed...