• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1869
  • Last Modified:

cpio:lstat failed AND cpio: mkdir failed

i use ximian desktop on my red hat linux 7.2 machine. ximian corporation released an new version of their software downloader, red-carpet. when i started red-carpet, he says that i must upgrade my (old) red-carpet with the new one. he keeps saying this and not did not let me do anything else. the problem is that upgrading (rpm -Uvh) crashes with the error "unpacking of archive failed: cpio: lstat failed - input/output error". i thought that maybe rpm was too old for that package. i have tried to upgrade rpm-4.0.3 to rpm-4.0.4. : "error: unpacking of archive failed: cpio: mkdir failed - input/output error". this is happening while i'm logged in as root. what's wrong?
guzu
0
guzu
Asked:
guzu
  • 10
  • 6
1 Solution
 
guzuAuthor Commented:
in the meantime, upgrading kernel and others was ok. rpm -K was ok.
0
 
jlevieCommented:
The 7.2 version of rpm isn't the problem here. It works fine with Ximian. Do you have enough free space on the system for the unpacking of the rpm? Do a 'df' and see what your filesystems look like.
0
 
guzuAuthor Commented:
hello jlevie, i was waiting for you. df -h says i have 297 megs free. also i have 1gig of free swap memory. unpacking other packages was ok.
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
guzuAuthor Commented:
red-carpet was downloaded several times and the error was the same: "cpio: lstata failed"....
0
 
jlevieCommented:
Hmm, I've not encounted that error with Ximian. Are you using Ximian's tool to do the upgrade of RedCarpet? Normally it notices that it's version is old and asks to be allowed to do the update. I don't know what would happen if you tried to manually do the upgrade via an rpm.
0
 
guzuAuthor Commented:
well, that's how the all thing's started. i've tried to upgrade with ximian's tool. indeed, it asks to do the update. as you know, there's no other posibility so i pressed the update button. he says that everything is ok and it will restart i have to agree with that then he started over again and again. the i tried to do it manually, and i've found that errors. i've checked for the installed version of red-carpet and it was the old one... . i thought that it was rpm's fault (old rpm utility with new rpm package..) and the rest you know. could it be the hdd?
0
 
guzuAuthor Commented:
well, that's how the all thing's started. i've tried to upgrade with ximian's tool. indeed, it asks to do the update. as you know, there's no other posibility so i pressed the update button. he says that everything is ok and it will restart i have to agree with that then he started over again and again. the i tried to do it manually, and i've found that errors. i've checked for the installed version of red-carpet and it was the old one... . i thought that it was rpm's fault (old rpm utility with new rpm package..) and the rest you know. could it be the hdd?
0
 
guzuAuthor Commented:
sorry, i've reposted data during refresh...
0
 
jlevieCommented:
Besides Ximian, what other updates have been applied to the system and have all that are applied come from RedHat?
0
 
guzuAuthor Commented:
all updates (maybe except libstdc3, i can't recall now) are from ximian or redhat
0
 
guzuAuthor Commented:
bad news jlevie, i've done e2fsck -nf on my root partition and there are A LOT of errors... . do you think that e2fsck-ing from slackware would fix the errors? or i will loose information? (i have some bad memories about running e2fsck on my ext3 filesystem...
0
 
jlevieCommented:
There shouldn't be any problem with using e2fsck on an ext3 file system. In reality an ext3 file system is an ext2 with journaling. I believe you should be able to force an fsck of all filesystems by 'touch /forcefsck' and rebooting. When prompted during the boot, interrupt the and ask for an extensive check.
0
 
guzuAuthor Commented:
well, last time i've tried this, i've lost everything so, i'll try to boot a slack and fsck without having the partition mounted.... thanks. i'll keep you up to date.
0
 
jlevieCommented:
As far as I know it's safe to force the fsck at boot on a 7.x system. What you can't safely do is to manually fsck the root file system with it mounted and in use. The OS knows how to fsck the root at boot time, which is why the forcefsck technique exists.

Now, if you've got a flaky disk or controller all bets are off. The only times I've seen corruption of a file system involved bad disks/controllers or wierd software that ran with root privs. Under normal operation (oderly startup/shutdown of the OS) it's very unlikely for RH 7.2 to scramble anything on the system.
0
 
guzuAuthor Commented:
you are the expert onceagain. since i have strong reason to believe my hdd/mb don't match (for whatever reason), i've done the check from another partition/distribution. since i still can write you this, it seems to me that it works. also , the packages could now be installed on my system. probably, first step will be to replace the hdd. ok. now the points will be yours. thanks again.
0
 
jlevieCommented:
I'm glad we go to the bottom of this. I'll admit to being a bit mystified as to the rpm failures until you mentioned the disk problem. At that point the cause of the failure became quite clear. I still don't know why the corruption occured, but a disk/mb mismatch could be the root cause.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 10
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now