The other distro happened to use the label "/". If you have parallel mounted distribution, using mount-points for labels can be very confusing.
In any case, if simply going to another kernel solved the problem, then this clearly isn't an e2fsck-static bug. I am confused about how changing the kernel would cause fsck to bomb out, and changing the kernel boot option shouldn't make a difference either. Can you send me your /etc/fstab file? In any case, unless you can replicate it, and I'd suggest that perhaps this bug report should be closed out. -- [Feisty]Bug with kernel 2.6.20 on AMD 64 : no way to boot https://bugs.launchpad.net/bugs/107965 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
