Comment # 12 on bug 1123094 from David Walker

I've been running Mint in "production," but I tried running the recent
Tumbleweed a couple of weeks ago (20190704) to see if it would work.  It
didn't, so I switched back to Mint, but I've continued running experiments.

The symptom I've seen most since then is that the root partition is suddenly
read-only.  At that point, I can't reboot the system without power cycling it. 
Unfortunately, that also loses log records at the time of the crash.

So, I ran another experiment yesterday while redirecting "journalctl -f" into a
file on a USB-connected SSD.  My plan was to generate load by using zypper to
download the latest (very large) Tumbleweed, but packagekit got there before
me, so I let it run.  I then started watching a movie with Kodi and waited. 
The result was more dramatic than usual.  After 20-30 minutes, the screen went
black with only a blinking cursor in the upper left corner of the monitor. 
Ctrl-Alt-F1 brought up a text-mode login prompt, but I didn't get a password
prompt after typing "root".  After several seconds, it printed the names of the
two network interfaces (eno1 and enp2s0, as I remember) and issued the login
prompt again.

Fortunately, my trick of using another disk to collect log records worked. I'll
attach the last several seconds and can provide the full log records for that
system boot, if it would help.  An interesting thing is that smartd started
running tests just as things went bad.  It look to me like Mint isn't running
smartd.