same thing here to, after upgrade from 1.2 to 2.0b3
also with dev kernle, starting fsck by hand results in the same error message