Hi,
I've got a disk that won't fsck, says to run manually. When I do it says that it's got a corrupt group descriptor. I've tried restoring a backup super block and got the same error message.

I then removed the journal bit and ran fsck again.

It said that either partition table or the superblock was wrong. I've now got a huge load of:

Group 15** 's inode table conflicts with some other fs block.
Relocate(y)? yes <enter>

Group 15** 's inode table conflicts with some other fs block.
Relocate(y)? yes <enter>

Group 15** 's inode table conflicts with some other fs block.
Relocate(y)?

There are so many of these I think it's a problem. I've left something on the return key to keep saying yes but it's going through hundreds/thousands!

Help?

is your partition mounted when u try fsck...secondly did u try to boot via arescue CD and do fsck...

no, it wouldn't mount, not even forced, and I tried to get it back but eventually gave up and restored from backup.

I didn't try boot cd, I doubt it would have made a difference cos it seems that the filesystem itself became corrupted. FIlesystems in linux have some catching up to do...

try REISERfs for robustness

I'm aware that ReiserFS is a higher performance filesystem than ext3, but ext3 is still generally the standard, so it's a more thoroughly tested filesystem by sheer user base, kinda why Microsoft advanced so much in terms of stability with their most recent OSs, the user base found their problems for them, the best test lab in the world.

Unfortunately, I still don't feel as comfortable with ext3 or Reiser as I do with NTFS 5, even though I think Linux systems are more fun for people like me who love to meddle in stuff...