When doing my updates, I got this message:
error: unpacking of archive failed on file /boot/System.map-2.6.9-78.0. 13.EL;49a
Unfortunately, I installed Centos 4 about two years ago on my server that sits in the corner and does it's job of faithfully providing services without me touching it except to run a backup script and do a YUM update every week so. The result is that I have forgotten my Linux know how!
Help!
Todd
On Wed, 2009-03-04 at 11:38 -0800, Todd Cary wrote:
When doing my updates, I got this message:
error: unpacking of archive failed on file /boot/System.map-2.6.9-78.0. 13.EL;49a
Unfortunately, I installed Centos 4 about two years ago on my server that sits in the corner and does it's job of faithfully providing services without me touching it except to run a backup script and do a YUM update every week so. The result is that I have forgotten my Linux know how!
Out of space? do a df and df -i on the file system and see if the space looks tight. If so, cleaning out some cruft might help. Also, if /boot is mounted read-only I guess that could cause it.
Help!
Todd
<snip sig stuff>
HTH
Bill -
Thank you! My boot partition does not have any space available. Now there are what appears to be many files in there that are not needed, *but* with my sparse knowledge, I am reluctant to start erasing them.
Here is a sample:
-rw-r--r-- 1 root root 1310809 Mar 17 2008 initrd-2.6.9-67.0.7.EL.img -rw-r--r-- 1 root root 1296959 Mar 17 2008 initrd-2.6.9-67.0.7.ELsmp.img -rw-r--r-- 1 root root 1310005 Dec 18 2007 initrd-2.6.9-67.EL.img -rw-r--r-- 1 root root 1296326 Dec 18 2007 initrd-2.6.9-67.ELsmp.img
-rw-r--r-- 1 root root 759989 Feb 3 2008 System.map-2.6.9-67.0.4.EL -rw-r--r-- 1 root root 776963 Feb 3 2008 System.map-2.6.9-67.0.4.ELsmp -rw-r--r-- 1 root root 760171 Mar 15 2008 System.map-2.6.9-67.0.7.EL -rw-r--r-- 1 root root 777145 Mar 15 2008 System.map-2.6.9-67.0.7.ELsmp -rw-r--r-- 1 root root 759989 Nov 16 2007 System.map-2.6.9-67.EL -rw-r--r-- 1 root root 776963 Nov 16 2007 System.map-2.6.9-67.ELsmp
-rw-r--r-- 1 root root 1518757 Feb 3 2008 vmlinuz-2.6.9-67.0.4.EL -rw-r--r-- 1 root root 1458782 Feb 3 2008 vmlinuz-2.6.9-67.0.4.ELsmp -rw-r--r-- 1 root root 1518936 Mar 15 2008 vmlinuz-2.6.9-67.0.7.EL -rw-r--r-- 1 root root 1459052 Mar 15 2008 vmlinuz-2.6.9-67.0.7.ELsmp -rw-r--r-- 1 root root 1518693 Nov 16 2007 vmlinuz-2.6.9-67.EL -rw-r--r-- 1 root root 1458902 Nov 16 2007 vmlinuz-2.6.9-67.ELsmp
I would assume that the older vmlinuz files can be removed as well as the other old files.
Todd
William L. Maltby wrote:
On Wed, 2009-03-04 at 11:38 -0800, Todd Cary wrote:
When doing my updates, I got this message:
error: unpacking of archive failed on file /boot/System.map-2.6.9-78.0. 13.EL;49a
Unfortunately, I installed Centos 4 about two years ago on my server that sits in the corner and does it's job of faithfully providing services without me touching it except to run a backup script and do a YUM update every week so. The result is that I have forgotten my Linux know how!
Out of space? do a df and df -i on the file system and see if the space looks tight. If so, cleaning out some cruft might help. Also, if /boot is mounted read-only I guess that could cause it.
Help!
Todd
<snip sig stuff>
HTH
On Wed, 2009-03-04 at 14:38 -0800, Todd Cary wrote:
Bill -
Thank you! My boot partition does not have any space available. Now there are what appears to be many files in there that are not needed, *but* with my sparse knowledge, I am reluctant to start erasing them.
Here is a sample:
-rw-r--r-- 1 root root 1310809 Mar 17 2008 initrd-2.6.9-67.0.7.EL.img -rw-r--r-- 1 root root 1296959 Mar 17 2008 initrd-2.6.9-67.0.7.ELsmp.img -rw-r--r-- 1 root root 1310005 Dec 18 2007 initrd-2.6.9-67.EL.img -rw-r--r-- 1 root root 1296326 Dec 18 2007 initrd-2.6.9-67.ELsmp.img
-rw-r--r-- 1 root root 759989 Feb 3 2008 System.map-2.6.9-67.0.4.EL -rw-r--r-- 1 root root 776963 Feb 3 2008 System.map-2.6.9-67.0.4.ELsmp -rw-r--r-- 1 root root 760171 Mar 15 2008 System.map-2.6.9-67.0.7.EL -rw-r--r-- 1 root root 777145 Mar 15 2008 System.map-2.6.9-67.0.7.ELsmp -rw-r--r-- 1 root root 759989 Nov 16 2007 System.map-2.6.9-67.EL -rw-r--r-- 1 root root 776963 Nov 16 2007 System.map-2.6.9-67.ELsmp
-rw-r--r-- 1 root root 1518757 Feb 3 2008 vmlinuz-2.6.9-67.0.4.EL -rw-r--r-- 1 root root 1458782 Feb 3 2008 vmlinuz-2.6.9-67.0.4.ELsmp -rw-r--r-- 1 root root 1518936 Mar 15 2008 vmlinuz-2.6.9-67.0.7.EL -rw-r--r-- 1 root root 1459052 Mar 15 2008 vmlinuz-2.6.9-67.0.7.ELsmp -rw-r--r-- 1 root root 1518693 Nov 16 2007 vmlinuz-2.6.9-67.EL -rw-r--r-- 1 root root 1458902 Nov 16 2007 vmlinuz-2.6.9-67.ELsmp
I would assume that the older vmlinuz files can be removed as well as the other old files.
---- the proper way to handle the removal is via rpm
rpm -e kernel-2.6.9-67.EL kernel-2.6.9-67.ELsmp
Craig
On Wed, 04 Mar 2009 14:38:45 -0800 Todd Cary wrote:
Thank you! My boot partition does not have any space available. Now there are what appears to be many files in there that are not needed, *but* with my sparse knowledge, I am reluctant to start erasing them.
# yum install yum-utils # package-cleanup --oldkernels
This will remove all but the most recent two kernels (and kernel-devel packages)
Bill -
I did remove some of the older files (only a few) and there was then enough room to unpack the update. Is there some basic guideline on how many to remove?
Todd
William L. Maltby wrote:
On Wed, 2009-03-04 at 11:38 -0800, Todd Cary wrote:
When doing my updates, I got this message:
error: unpacking of archive failed on file /boot/System.map-2.6.9-78.0. 13.EL;49a
Unfortunately, I installed Centos 4 about two years ago on my server that sits in the corner and does it's job of faithfully providing services without me touching it except to run a backup script and do a YUM update every week so. The result is that I have forgotten my Linux know how!
Out of space? do a df and df -i on the file system and see if the space looks tight. If so, cleaning out some cruft might help. Also, if /boot is mounted read-only I guess that could cause it.
Help!
Todd
<snip sig stuff>
HTH
on 3-4-2009 2:48 PM Todd Cary spake the following:
Bill -
I did remove some of the older files (only a few) and there was then enough room to unpack the update. Is there some basic guideline on how many to remove?
Todd
William L. Maltby wrote:
On Wed, 2009-03-04 at 11:38 -0800, Todd Cary wrote:
When doing my updates, I got this message:
error: unpacking of archive failed on file /boot/System.map-2.6.9-78.0. 13.EL;49a
Unfortunately, I installed Centos 4 about two years ago on my server that sits in the corner and does it's job of faithfully providing services without me touching it except to run a backup script and do a YUM update every week so. The result is that I have forgotten my Linux know how!
Out of space? do a df and df -i on the file system and see if the space looks tight. If so, cleaning out some cruft might help. Also, if /boot is mounted read-only I guess that could cause it.
Help!
Todd
<snip sig stuff>
HTH
-- Ariste Software Petaluma, CA 94952
I would think that the current running kernel and the last should be enough. Maybe 3 for a short while after a kernel upgrade.
On Wed, 2009-03-04 at 14:48 -0800, Todd Cary wrote:
Bill -
I did remove some of the older files (only a few) and there was then enough room to unpack the update. Is there some basic guideline on how many to remove?
I suspect you have a minor mess-up in /etc/yum.conf (man yum.conf). IIRC, installonlypkgs (defaults to various kernel name variations) interacts with installonly_limit (default 3?). Somewhere, I can't recall where ATM, when the Xth version, specified by installonly_limit, is exceeded the oldest package version is automatically removed. However I seldom play with this stuff and haven't reviewed it in a long time so I'm unsure about this. I do know that the grub.conf (menu.lst) is automatically updated to remove the older versions. Maybe I'm confusing the two?
Let's hope one of the folks that are current and more expert will chime in.
Now, if you made the mistake I once made, this all breaks. I had a fall-back boot scheme set up that had a second disk bootable and a copy of root, /var, etc. on it to allow fast recovery (LVM snapshots were automatically created at various times to complete the process). I then set that backup boot disk's /root into my fstab and forgot to remove it after testing. Yum updates ran on it and never updated my primary root. Being (apparently) brain-dead I blithely copied stuff over never realizing what I was doing.
Fortunately, the only real repercussion was when things got pretty full and I realized what I had done I received numerous bruises from self-flagellation with a locally available and wielded clue-bat! :-(
As to your current clean-up effort, I think Craig mentioned the rpm method. That's what I would do. Just be careful that you double-check the version before you hit enter or you will not have enough clue-bats available to administer sufficient punitive lessons.
Todd
<snip>
Friends of CentOs mailing list.
I need some advice from you.
The xfce 4 panel disapear. In fact I can acess all of xfce (by clicking with mouse) but if I minimize the window it disapear. I make a uninstall and reinstall from yum. Nothing change.
Best wishes.
Arturo Brazil, South
Arturo Fatturi wrote:
Friends of CentOs mailing list.
I need some advice from you.
The xfce 4 panel disapear. In fact I can acess all of xfce (by clicking with mouse) but if I minimize the window it disapear. I make a uninstall and reinstall from yum. Nothing change.
you could try (backing up and) removing your xfce config directory, which I think is ~/.config/