Red HatThis forum is for the discussion of Red Hat Linux.
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.
I've some bad blocks, that redhat stops and does a force check to fix/ignore upon boot up. Is there a way to bypass at boot, remove, or repair the bad blocks?
An option for e2fsck is to mark the bad blocks and flag them so that data will not be saved onto it. 'man e2fsck' to look at the different arguments you can pass.
Thanks,
After looking at man for e2fsck, I couldn't find anything that flagged the bad superblock so that data would not be saved to it. Only thing close was the -l option to write the bad block to a badblock file, but I have no idea what the file is called. I tried making one using the command e2fsck -pv -L badblocks /dev/hdc , but it just keeps saying Bad magic number in super-block, while trying to open /dev/hdc. It can't read the block or something.
-c
This option causes e2fsck to run the badblocks(8) program to find any blocks which are bad on the filesystem, and then marks them as bad by adding them to the bad block inode. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.