On Tuesday 15 May 2001 03:31, [EMAIL PROTECTED] wrote:
> I have installed the Opera browser on LM8.0
>
> During the normal navigation I got a "freeze screen" .. the PC become
> completely unresponsive . I thought that this didn't happen on Linux .
> The fact that an application can bring down an OS was the reason that I've
> switched from Windows .. many people assured me that "freeze screens" and
> "blue screens" wouldn't happen. I am a bit disappointed :-(
>
> I had to press the reset button and reboot.
> But while the system was rebooting I've got a message that the disk wasn't
> cleanly unmounted and that some kind of check had to be done. The problem
> is that errors were found and I was presented two choices: 1) Press Control
> + D for normal startup. Which I did .. but with no luck 2)Provide root
> password to do some kind of manual fixes.
>
>
> Option number two is the reason I'm writing this e-mail.
>
> What can I do at the command line to fix this. I am newbie at Linux... I
> don't have a clue of what to do
>
> I really hate the idea of doing a fresh install and lose all my data.
>
> Can anyone help?
>
> Thanks,
>
>
> Luis Neves
First of all, you did not have to reboot
You could have pressed ctrl-alt-F2 and come up in a console
Then you login as normal and use these commands
$ ps ax | grep opera
>From the output of the list you should have a line that identifies the name
and process number of opera
Then you do
$ kill -9 (process number of opera)
and use ctrl-alt-f7 to go back to the GUI screen. If it is still a mess
(which can happen) then ctrl-alt-backspace will restart X (the basis of the
GUI interface) and you should be OK.
Opera is still a little shaky. I would recommend Konqueror, Nautilus, or
similar using Netscape when you need to access a javascript page.
Now for option 2
give the root password
the filesystem with the problem is what you want to fix, and you will be
shown its designation, like /dev/hda7 (which I will use as an example)
You want
e2fsck -b 8193 -r /dev/hda7
This will check the filesystem, asking you questions about fixing. It is a
very thorough equivalent to scandisk
If 8193 doesn't work, try
16385, or 24377, or 32769 or 65537 til one does work... certain filesystem
information is duplicated across many disk blocks so fixit information is
almost always available.
Once the check is done, type ctrl-alt-del to get a reboot going.
Now this is important... webmin is installed and activated on most of our
modern systems and the webmin server will be running even if your gui and
keyboard and mouse are all frozen (a very rare occurrence). If you have an
external access means from a network, login at https://(whatever your local
IP is):10000 using whatever browser might be available. GIve it root for a
user and root password for a user password and you can then force a reboot in
a clean fashion, or take other action to repair the damage from a remote web
browser.
Civileme
