I have been using various flavors of Linux (ubuntu, debian, and Kali) under VMware Workstation, running Windows 10 as the host, and have been experiencing the file systems of the guest OS's going "Read only" intermittently - I think it happened 2 times yesterday and once today.
At first I thought it was just a bad install as it was happening under Kali only to start - however then it began affecting Ubuntu and Debian as well.
I have run SMART tests on the Windows side and they do not reveal any issues.
Below is what I see in dmesg after the most recent revert to read only:
[ 4.684740] random: crng init done
[ 5.357246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.361262] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.370915] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[ 5.371618] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 7.391713] e1000: eth0 NIC Link is Down
[ 15.455356] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[ 317.358720] EXT4-fs warning (device sda1): ext4_dirent_csum_verify:352: inode #155789: comm updatedb.mlocat: No space for directory leaf checksum. Please run e2fsck -D.
[ 317.358722] EXT4-fs error (device sda1): htree_dirblock_to_tree:962: inode #155789: comm updatedb.mlocat: Directory block failed checksum
[ 317.358944] Aborting journal on device sda1-8.
[ 317.359230] EXT4-fs (sda1): Remounting filesystem read-only
[ 317.361153] EXT4-fs warning (device sda1): ext4_dirent_csum_verify:352: inode #155843: comm updatedb.mlocat: No space for directory leaf checksum. Please run e2fsck -D.
[ 317.361154] EXT4-fs error (device sda1): htree_dirblock_to_tree:962: inode #155843: comm updatedb.mlocat: Directory block failed checksum
[ 317.373714] EXT4-fs warning (device sda1): ext4_dirent_csum_verify:352: inode #154974: comm updatedb.mlocat: No space for directory leaf checksum. Please run e2fsck -D.
[ 317.373716] EXT4-fs error (device sda1): htree_dirblock_to_tree:962: inode #154974: comm updatedb.mlocat: Directory block failed checksum
To fix this I have been rebooting and running "fsck /dev/sda1 -y" and it seems to be fine after that, for a while at least.
What might be causing this behavior, or is there anything more I can do to diagnose it given that this is in a VM and not a SMART capable drive?
Also note that I have not experienced any issues under windows that would indicate a failing SSD.