Query on fsck and bad superblock
 

Hello everyone,

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:

Best way to check and fix corrupt disk?
Repairing Linux ext2 or ext3 or ext4 File System(fsck)

And an interesting article about the fear to run fsck:

http://aplawrence.com/Unixart/fear-of-fsck.html

Though I would suggest to do backup before running fsck (for fixing) if you suspect something is wrong with the hard disk.

Thanks!