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.
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.