begin: Richard S. Crawford <[EMAIL PROTECTED]> quote
> >
> >Strange things happened after that.  My mouse became more or less
> >unresponsive (it would move across the screen and could click on things but
> >nothing would execute -- I couldn't even click the "log out" button when I
> >shut down).  Now, when I boot the machine, I get the following error:
> >
> >/home contains a file system with errors, check forced.
> >/home:
> >Unattached inode 288672
> >
> >/home: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
> >        (i.e., without -a or -p options)
> >/u2: clean, 11/1376256 files, 43201/2749115 blocks
> >
> >[FAILED]
> >
> >*** An error occured during the file system check
> >*** Dropping you to a shell; the system will reboot
> >*** whne you leave the shell.
> >Give root password for maintenance.
> >(or type Control-D for normal startup):
> >
> >
> >This strikes me as kind of bad.

what you don't mention in the email is whether you've "taken care of this".

have you run fsck manually?

> >I'm going to go through all my normal channels: a brother-in-law who helped
> >me put this computer together in the first place, several discussion groups
> >and mailing lists, and the tons of documentation that are out there... but
> >am I right in thinking that I may have to reinstall Linux?

you need to move away from the Windows way of thinking.  there is very little
that can happen to your linux machine that requires a re-install.

in case you haven't run fsck manually:
        reboot the machine
        log in as root
        find out which partition /home is on by looking at /etc/fstab [1]
        fuser -k -m /home
        fsck /dev/hd[1]

next:

so your mouse becomes unresponsive every time you boot the machine?

even when you don't run vmware?

do a ps aux and look for a running process that might belong to vmware.  kill
it.  if your machine seems ok, then go to /etc/init.d/rcblah.d and rename the
symlink to the vmware startup script.   it'll be named something like
S99vmware.   rename it with a lowercase s: s99vmware.

you'll have your machine back.

to uninstall vmware, it's "rpm -e vmware"

at this point, you can try to reinstall vmware and see what happens.

pete

-- 
"You may not use the Software in connection with any site that disparages
Microsoft, MSN, MSNBC, Expedia, or their products or services ..."
                    -- Clause from license for FrontPage 2002

Reply via email to