Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
The other day I got a error in one of my Linux vm where it was asking for a force file system check after I had forcefully restarted(which I know I shouldn't have done).
So while running fsck it prompts me for fixing bad superblocks and inode no.
I am not sure what was that all about.
Am I suppose to give yes to all or will that affect my data and file system.
Can anyone help me with a brief description on this or if possible help me with some good links where I can learn about fixing hard disk related errors in linux and repairing them.
Is it advisable to all fsck fix the corrupted INODE because last time I remember I did a fsck -y on one of my machines and next time that machine gave a kernel panic so i had to revert back.
In any case you should not run fsck on a mounted file system in multi-user mode. It should be run in single user mode and unmount the filesystem first. Here are something small and handy:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.