Our system (Ubuntu 18.04 on Dell Precision 7920 tower) froze when I tried to restart Spyder and when I restarted, it would not advance past the fsckd filesystem check (please see images). Since some of the errors seemed network related, I unplugged the ethernet and tried rebooting (same thing happened, but maybe some different errors; see 1st stuck point image). I rebooted and pressed F12 to do a system scan. Everything was good there, so the issue does not seem to be with the hardware. I changed the BIOS settings to default and after rebooting got to the same screen (but with different errors; 2nd image of stuck point). Dell suggested this: booting and pressing F2 -> System config -> STAT Operation -> change from Raid On to AHCI. A warning pops up that this may prevent your OS from booting or require a reinstall. I did not try this yet because I am worried it will wipe the data. Please let me know if this is safe to try. The SSDs are not currently in a RAID configuration.
I think we started having issues sometime after we tried to set up a TigerVNC server and ended up using x2go. Before this crash we could not to log in to one user account, which could be a log in loop error. It seemed like problems were related to X server or not connecting to a monitor or server for that user. We could run the terminal under that user account (e.g., with su boris), but could not launch GUIs from the terminal. If you read the errors in the fsckd scan, there are multiple sessions with that user are starting during fsckd scan, so I wonder if this could be the source of our problem. For a while, we tried using another user account until TeamViewer stopped on that account, but not others (since we are trying to work from home).
The day before the crash I added some paths to PATH and PYTHONPATH in .bashrc and .profile to help Spyder import a python module. I am not sure if this could be part of the problem.
This issue might be similar to the one in this thread with more discussion here., but there are some differences in the filesystem check and it seemed like they ended up reinstalling Ubuntu. We have a lot of software that was difficult for us to install/setup and would like to be able to fix this without reinstalling Ubuntu. Any suggestions would be greatly appreciated!
Example of filesystem check error when booting up: . . . [FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details [ OK ] Started Session 3 of user boris. [ OK ] Stopped Network Name Resolution [FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details [ OK ] Started Session 4 of user boris. [ OK ] Started xrdp session manager Starting xrdp daemon... [ OK] Started GNOME Display Manager. Fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress
Images: Fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress 1st stuck point Stuck point after BIOS default then reboot Warning about switching Raid On to AHCI
