I am running slackware 10 on my dual boot system.

This is what happens when from LILO I boot into Slack.

/dev/hda2 contains a filesystem with errors
check forced
Inode 557913 has illegal blocks

/de/hda2 Unexpected Inconsistency RUN fsck MANUALLY

an error occured during your file system check
you will be given the chance to login into system in single-user mode to fix problem.
if you are uing he ext2 filesystem run e2fsck -v -y <partition> might help

It doesn't!!

/dev/conscole:/#
root@(noone):/#


I ran fsck and I got this:
Inode #######, i_block should be #### should be ____

so I said sure why not..yes to all....then it did this for a while with a slew of what I assume are bad blocks, so I said yes to all of them.

I tried reinstalling the filesystem without formating my partitions, I don't want to loose my settings on my KDE desktop and the rest of my files. So if anyone has any suggestions not leading up to "reinstall slack" I would greatly appreciate it.

I want that option to be my very very last resort.

Thanks

CP


P.S linux is still fun! :-

It all depends what kind of partition you had. If it was ext2 or ext3, you probably just destroyed all of your inodes.

Unfortunately, when you run fsck or another program that is supposed to fix your disc, if you choose the wrong program or the wrong version, you run the risk of destroying data.

That is what happened to me some time ago when I used a very old version of e2fsck on a damaged harddrive.

You can try running the appropriate program for your archecture, but at this point you have probably done permanent damage to the partition table.

Speaking of which, if this happened suddenly, your harddrive was probably ruined anyway, and there most likely wasn't much you could have done to restore the data.

Good luck, but prepair yourself to "reinstall slack".

And next time, use ext3 so when this happens next, you can just recover the journal and be done with it.