Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
some days ago my CC2.2 (RH9based) did not start because data integrity check of an mount point / partition (ext3), 30 pages with several errors(Inodes)were scroling.
SO I deleted this mount point in the fstab and restarted CC.
I checked the partition with fsck -n -> no errors found.
By using fsck -nf 6 errors were listed.
After repairing with fsck -pf, fsck -nf reported everything clean.
1.Is my partition now clean?
2. What error checking/correction is used after an uncomplete shutdown?
3.What error correction modules / programm are available and perhaps better than FSCK ?
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
fsck is the only thing you can use. the filesystem is most likely clean, but whatever files you may have been working on when the machine was reset may be incomplete, or have bad data in them.
when the filesystem is loaded, a clean bit or byte is checked, and if clean, changed to unclean, i think. when you shutdown normally this is changed back to clean. that way if you boot, and the filesystem says unclean, then it knows to check.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.