Clarify when "error unlocking" is related to hardware problems
Quite often, users can't unlock their Persistence for problems which are probably hardware-related. See #19948 (comment 218031)
The work done in !1427 (merged) does not help with this scenario: it does not report the I/O error as possible hardware failure to the user in the Welcome Screen, and instead we still report an error to activate persistent storage. Moreover, we don't report that I/O error after login.
We should give them a more informative error message, clarifying that hardware might be the culprit. Examples of signs of hardware problems:
udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/sdc2: Failed to activate device: Input/output error (0)
"wrong fs type, bad option, bad superblock"
- "Structure needs cleaning"
InvalidPartitionError
This can also happen when creating a Persistent Storage, on first unlock, e.g. wb:850daf82deacd04d6537f3d97ecd9101.
Edited by intrigeri