[matrim]

I've got Redhat 8.0 installed. Recently the filesystem or hard drive got some bad blocks, at least one. Is there a way to bypass the block so it skips this, or delete it or repair it somehow? I run fsck and it fixed/ignored the bad block once or twice, but upon reboot now the error is coming back. Most of the time now it even freezes after checking the filesystem. I'm not sure what to try next. Any ideas?

Is there a way to bypass the force check upon boot?

[Squashman]

http://www.rt.com/man/badblocks.8.html

Only run this on unmounted disks

It takes a LONG time to run.

It should be installed on your system already. If it is not, it should be on your install disks.

[matrim]

Hmm, well i know it has bad blocks already, the badblock program will just tell me what i already know. What i need is to find out how to bypass the forced check upon boot, or something I can use when it drops me to the shell other than fsck.

When using e2fsck i get: Bad magic number in super-block while trying to open /dev/hdc

The bad block is 544779.

[Squashman]

BadBlocks marks off the bad parts of the disk so that they are not used anymore.

[matrim]

Ahah! I tried it and it found bad blocks, but then froze hehe. So i'm trying fsck -t ext3 -b 8193 /dev/hdc3 and am going through tons of bad inodes, like hundreds of fixes. Not sure why this occurred. I installed on a good part of the hard drive, and things were going well, it never lost power or crashed...

[Squashman]

Sometimes hard drives go bad. I have had to run the badblocks command on my raid twice in the past 4 months.

[lynch]

Save your stuff and get a new hard drive.
lynch