The first screenshot seems to show a particular problem with fscking the device
/media/extraspace/hudson/.m2/repository, which is in turn on the device
LABEL=extraspace. You could try changing the fsck pass of the former to 0, with the line
/media/extraspace/hudson/.m2/repository /var/lib/hudson/.m2/repository ext4 bind,defaults 0 0
(changing the terminal 2 to a 0) and skip the fsck pass. That should let you get the system up and running, and hopefully you can then look into why that line's there and whether the device should be fscked at boot or not.
If that does help and you want to fsck at boot, try changing the 2 to a 3: I see that
LABEL=extraspace is fscked in pass 2 also, and there's no way you can fsck a file system which is inside another file system which is currently being fscked, and is therefore not yet mounted.