e2fsck superblock boot error

Hi,
I've got a mostly working system: Debian on a 2.4.18 kernel, I'm trying to upgrade to 2.6.4. I've configured and installed the new kernel using kpkg, the issue is when I try to boot it I get an error from fsck which says that it's either not checking an ext2 filesystem (which it isn't, it's ext3) or the superblock on the drive is bad. It then gives me a prompt to enter the root password for maintenance. How can I correct this?
thanks in advance

Upgrading may have altered /etc/fstab. Give the root password and edit /etc/fstab with vi.
If it shows ext2 you could change it to ext3. Another possibility is that your kernel does not have
ext3. A thread here mentions that:
http://216.239.53.104/search?q=cache...hl=en&ie=UTF-8

I actually have edited fstab, I changed ext2 to ext3, and I have ext3 support compiled into the kernel. Any other ideas?

If everything was OK before the change to 2.6, I have no clue...

What happens if you run from a rescue disc and do a manual e2fsck?

see man e2fsck
You should do this to an unmounted disc or the filesystem could be damaged.

I've just upgraded to 2.6.4 on my Debian box, and I'm having the exact same problem, however my partitions are ext2 and my fstab has not changed since I have installed Debian (2 days ago). I'm beginning to think it's a bug in the kernel, however dezert_fox is the only other person I've found with this problem, and it looks like we both have Debian installed.

Did you get the kernel source from Kernel.org, or did you use an image from Debian.org? I compiled mine from the source on Kernel.org, maybe that is the problem. It looks like, for now, Debian.org is only offering 2.6.3, so maybe waiting for them to release 2.6.4 in a .deb format would be the way to go.

I got the source from kernel.org... I don't see why the .4 release would have the bug though, isn't an even number supposed to be the stable release?

And, sorry, a manual run of e2fsck from the 2.4.18 boot disk i have produces no errors.

I got the source from kernel.org... I don't see why the .4 release would have the bug though, isn't an even number supposed to be the stable release?

Yes, 2.6.4 is the newest stable release, however sometimes kernel packages for different distributions have patches the creator of the package added to fix behavior problems with that kernel on that distro, and sometimes bugs creep into even stable releases of software. This would mean it's either a Debian-specific problem, a bug unknown or not corrected in the kernel, or we both just configured the kernel incorrectly. I doubt it is a filesystem or hard drive problem, as we have different filesystems and hard drives, both of which work fine in other releases of the kernel.

Another guy with Debian having the same problem.

Looks like it's a problem with the distro, as he's running 2.6.1 with the same problem. Been googling, havn't found a fix or any other information as of yet.

I found this page on google and contacted the guy who found a solution. Apparently the answer lies in configuring the kernel properly. I'l hopefully get a response from him soon.

Just make sure that your boot partition type is compiled into your kernel, and not a module