Mysql Fails to start on VM: InnoDB: Operating system error number 5 in a file operation.'Input/output error'

Anyone familiar with this? Consensus seem to be thats its indicative of a hardware error… but as its VM, unless my underlying disk is at fault. Crashed out pretty hard. Maybe filesystem corruption. But how verify on Debian VM. fsck give dire warning that the disk “will be severely damaged” if try and run on the live boot device. Any advice much appreciated?

Mysql Error.log

2019-09-23 00:11:55 672 [ERROR] InnoDB: Error in system call pread(). The operating system error number is 5.
2019-09-23 00:11:55 7fd8b23ef740 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means ‘Input/output error’.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2019-09-23 00:11:55 672 [ERROR] InnoDB: File (unknown): ‘read’ returned OS error 105. Cannot continue operation
190923 00:11:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

After Bouncing the database it seem to have resolved itself -this time it reported an inconsistency between the transaction log and the data file so presumably its rolled the transaction log forward or backwards to restore consistency . Say possible corruption! - but I’ve clean dump so I think I’m ok.