Errors after system reset - advice?

From: Jim Butterfield (fjb_at_pathcom.com)
Date: 12/28/03 

Date: Sun, 28 Dec 2003 17:03:33 GMT

A friend of mine who's quite knowledgeable about computer systems,
especially hardware, reported the following problem. He'll likely fix
it by reinstalling; but ... does any have any advice as to what to do
if he encounters this situation again?

>Recently, I accidentally reset my computer after it was powered up with
Linux. When it rebooted, it gave me the following errors:

>1) "contains a file system with errors
>2) "unattached inode nnnn

>It told me to run fsck manually to fix the problem.

>>From my readings using Google search, I determined that the problem was
>created by the a sector being in use when I did an accidental reboot.

>These things can happen with Windows too, so maybe I was just unlucky.

>However, I have no idea what needs to be done.
>If I had any data files on this system, they would be cooked.
>If I had to fix it myself, I couldn't, without calling the experts.

>This is not a good situation to be in, but reinforces my opinion that
>Linux still has a long way to go, before it reaches Windows level of
>standards.

>I didn't have any data files on this system, so I will just reinstall the system.

If there are any suggestion, I'll pass them on.

                --Jim

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Quantcast