Results 1 to 8 of 8
Im not sure if that is the correct command... but
I had to run that in class today and it KILLED my system... When I try to boot up I ...
- 06-27-2010 #1Just Joined!
- Join Date
- Jun 2010
- Location
- Texas
- Posts
- 9
fsck??
Im not sure if that is the correct command... but

I had to run that in class today and it KILLED my system... When I try to boot up I get sleeping for ever...
What happened?
- 06-27-2010 #2
fsck command checks File system integrity only. It checks and repair file systems.
What do you mean by sleeping? Does it throw any error message?When I try to boot up I get sleeping for ever..It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 06-27-2010 #3Just Joined!
- Join Date
- Jun 2010
- Location
- Texas
- Posts
- 9
That was the message.
When I ran it..
1. it gave the warning
2. I told it to do it anyway as that was the assignment in class
3. It told me I had an error and it was going to fix it, it also said that THIS CAN NOT BE DONE IT WILL CAUSE ... as you can see I dont have it up still.
4. Then it froze, I tried to exit the terminal but it wouldnt let me, I had no control over any aspect of the computer.
5. The only way to get control was a hard reboot.
6. When it came back up it said I had to specify an OS then said will sleep forever... or something along those lines.
I have already reinstalled the system so I can start from scratch. I am just curious why this happened if anyone else has any info on it. I am anal about backups so that is not an issue and it was a good learning experience for me.. BUT lol
- 06-28-2010 #4
there is a warning message for a reason, you shouldn't run fsck on a mounted filesystem
- 06-30-2010 #5Just Joined!
- Join Date
- Jun 2010
- Location
- Texas
- Posts
- 9
That explains why mine is the only system it crashed. I was the only one running a mounted version, everyone else is running it virtually.
What is it about a mounted system that causes it to do that?
- 06-30-2010 #6
fsck checks integrity of filesystem and fix errors, if there are any. A mounted partitions might have a lot of open files and running fsck on it might corrupt those files. If mount partition is /, result could be worst.
A few distros do not allow running fsck on mounted system.It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 06-30-2010 #7Just Joined!
- Join Date
- Jun 2010
- Location
- Texas
- Posts
- 9
- 06-30-2010 #8
they probably did it with the filesystem unmounted, which is the correct and safe way to run the command


Reply With Quote
