That's not a bug in ubiquity. Calling fsck on boot is the correct action for any filesystem; that running fsck on your root filesystem fails indicates either a problem with the kernel's filesystem handling, or a bug in fsck.xfs.
That's not a bug in ubiquity. Calling fsck on boot is the correct action for any filesystem; that running fsck on your root filesystem fails indicates either a problem with the kernel's filesystem handling, or a bug in fsck.xfs.