[vox-tech] xmms failure

[Peter Jay Salzman]

yeah, i was afraid of that.  here's fast instructions:

1. quit all applications
as root:
2. enter run-level 1.  log in as root if you need to.
3. mount -o remount,ro /dev/hd*? /

where * is the device holding the root partition and ? is the partition
number.  you can get these two things from /etc/fstab if you don't
already know them.

if mount complains that something is still accessing the filesystem
(which can be likely), use fuser to kill all user space processes
accessing the root partition.   i can never remember the syntax -- i
always have to look it up on the man page everytime i use it, but it's
something like "fuser -v -m /dev/hda*?"   you might want to check "man
fuser" to make sure i got that right.

make sure the filesystem is read only by looking at the output of
"mount" (with no options).  then you can run fsck safely.

before you do any of that, make sure you take a good long look at your
system logs to make sure it's not something else.   it could be
something much more benign than filesystem corruption[1].   in
particular, look for the "DriveSeek" type errors that result when
something bad happens to an IDE device like a failing IDE hard drive.

good luck!
pete

[1]: filesystem corruption isn't a big deal.  ext2/3 are very robust and
there's a lot of redundancy built into them.

begin Jonathan Stickel <jjstickel@netscape.net> 
> I just noticed that another of my programs is broken.  Trying to fix by 
> rpm gives a similar error.  How do I remount my Linux partition as 
> read-only and run fsck, as you suggest?
> 
> Thanks,
> Jonathan
> 
> 
> Peter Jay Salzman wrote:
> >hi jonathan,
> >
> >that cpio error may hint at either a munged rpm or filesystem
> >corruption.  it's odd that lstat failed.  i hope it was lstating
> >something within the cpio archive, and not something that's on the hard
> >drive.  some ideas to try in no particular order.  and yes, some of it
> >is grasping at straws:
> >
> >is xmms a symbolic link?
> >
> >try redownloading the rpm from a different site or using a different
> >method.
> >
> >try remounting / as read-only and run fsck.
> >
> >also, look for DriveSeek type errors in your system logs.
> >
> >pete
> >
> >
> >
> >
> >begin Rusty Minden <clownsinc@attbi.com> 
> >
> >>XMMS depends on other packages. For instance with Debian I have 
> >>to install unzip or I can't use skins. You may have updated a 
> >>package that was required and now XMMS does not see the required 
> >>package. This is only a guess though.
> >>
> >>Rusty
> >>
> >>On Tuesday 11 February 2003 10:13 am, Jonathan Stickel wrote:
> >>
> >>>I have been using xmms for quite some time, but just this
> >>>morning it stopped working!  All of its plugins seem to have
> >>>dissapeared.  The only change since I last used xmms
> >>>succesfully was a RH up2date of an unrelated program.
> >>>
> >>>I try to do an rpm uninstall of xmms, but it tells me it is
> >>>not installed.  Yet, the xmms binary is still in
> >>>usr/share/bin.  So I try to do an rpm install of xmms, hoping
> >>>it will overwrite any lost files, etc, and I get this error:
> >>>
> >>># rpm -Uvh xmms-1.2.7-13.p.i386.rpm
> >>>Preparing...               
> >>>########################################### [100%]
> >>>   1:xmms                  
> >>>########################################### [100%]
> >>>error: unpacking of archive failed: cpio: lstat failed - Value
> >>>too large for defined data type
> >>>
> >>>Any help out there?  Thanks,
> >>>
> >>>Jonathan
> >>
> >>
> >>Politics gives guys so much power that they tend to behave badly 
> >>around women. And I hope I never get into that.
> >>--William J. Clinton - Bill Clinton
> >
> >
> >heh.  i'd prefer ironic over moronic any day of the week!  ;)
> >
> >pete

-- 
First they ignore you, then they laugh at you, then they fight you,
then you win. -- Gandhi, being prophetic about Linux.

Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D