Ok, I think I was able to catch the error without having to get that desparate :) 

I logged in from work and did journalctl -f and got the following:

Looks disk hardware related but it's not getting worse so I doubt it's the disk itself, driver problem instead?

Thanks,

Richard