Results 1 to 4 of 4
I rebooted Mint 11 last night and got so many errors I couldn't see them all. The last line hinted at file system problems. I ran fsck on the root ...
- 02-01-2012 #1
Thank goodness for fsck!
I rebooted Mint 11 last night and got so many errors I couldn't see them all. The last line hinted at file system problems. I ran fsck on the root partition and it returned several problems which a second pass was able to fix. Linux may not be a completely problem free operating system but at least it gives us really good tools to repair problems when they occur!
- 02-01-2012 #2forum.guy
- Join Date
- May 2004
- Location
- arch linux
- Posts
- 18,082
oz
→ new members/users: read this first | new member faq
→ no private messages requesting computer support - post them on the forums!
→ please use the "report post" button to alert our forum admins to problematic posts rather than responding to them yourself.
- 02-02-2012 #3Linux Guru
- Join Date
- May 2011
- Posts
- 1,813
yup, when in doubt...http://images6.cpcache.com/product/1...olor-Black.jpg
- 02-02-2012 #4
Something like that happened to me the other day. I booted Crux and couldn't get X. Slim had crashed due to not finding a library. So I tried startx, and the X-server crashed too. The log showed a different library, same error. I tried ls on /usr/lib and got a string of errors that clearly came from the file system. So I guessed that the libraries weren't being found because the directory was corrupt.
I rebooted into Slackbody and ran fsck. It reported finding the errors and fixed them. End of problem!
Now that's what I call user-friendly. Try doing that in Windows!"I'm just a little old lady; don't try to dazzle me with jargon!"


2Likes
Reply With Quote

