Comment 5 for bug 748340

You also mentioned your fstab which I'm including below for reference; if you want to disable the fscks which are failing, you can set fs_passno to 0 (set last column to zero); this means that mountall wont fsck these fs on boot anymore.

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/vda5 during installation
UUID=54e7f946-69a5-4cf7-891c-c7fad695ea4e / btrfs defaults,subvol=@ 0 1
# /boot was on /dev/vda1 during installation
UUID=79f93bfc-984d-4554-8eea-dcb4892f21f0 /boot ext3 defaults 0 2
# /home was on /dev/vda5 during installation
UUID=54e7f946-69a5-4cf7-891c-c7fad695ea4e /home btrfs defaults,subvol=@home 0 2