Ubuntu

Comment 34 for bug 935585

Oh great - I get this too.
I worked around it by booting to recovery mode, doing an fsck and resuming boot.