I have an external SSD with Linux Mint Installed onto it (so not as a live USB, but as if it were an internal SSD). I used this around 1 week ago, and it worked fine. Tried to boot into it today, and suddenly it's not fine anymore.
When I boot I get a blue screen with a grey alert box saying:
Could not start the X server (your graphical environment) due to some internal error.
And it goes on to tell me to contact my system administrator and restart MDM when the error was corrected. The only option I can select there is 'ok' which will reboot the system.
This error persistently repeats itself on every boot attempt.
When I boot into the recovery mode, either of two things happen, seemingly randomly.
Either it will boot into recovery mode fine, but that obviously doesn't give me a fully functional system (e.g. I can't use a dual monitor setup because it doesn't load the display manager and I can't seem to manually start it either).
The other thing that can happen when booting into recovery mode is that I end up in a terminal-like environment which is definitely not the root shell, but appears to simply be Linux Mint without a gui. I can log in and seemingly access the terminal, but haven't done much other than
sudo reboot now in order to try and boot back into something that works a little better.
After logging into the terminal-like environment, I do get an error which reads:
sktemp: failed to create file via template `/var/lib/update-notifier/tmp.XXXXXXXXXX/': read-only file system run-parts: /etc/update-motd.d/95/hwe-e01 exited with return code 1 /usr/lib/update-notifier/update-motd-fsck-at-reboot: 33: /usr/lib/update-notifier/update-metd-fsck-at-reboot: cannot create /var/lib/update-notifier/fsck-at-reboot: Read-only file system
So it appears the system believes the file system to be read-only, where it shouldn't be. Now I could (maybe? possibly?) simply
CHOWN the entire system, but that doesn't seem like a wise idea.
I have also looked through the syslog, but that didn't really tell me anything. The word 'error' appears 16 times, but I have no idea as to how to interpret this information.
I have, of course, done my research prior to posting here. Following some of the things I found, I ran
fsck -Af -M
su, but both times all I got back was
fsck from util-linux 2.20.1
which doesn't really tell me anything.
Also I found that the OS may put a filesystem in Read-Only to prevent corruption, but I'm uncertain what would have caused said corruption, much less how to fix it.
Now I'm not looking for someone to 'fix this for me'. Instead, I'd love if any of you would be able to point me in the right direction as to what could be going on, if there are any other tests I can run to narrow down the issue etc.
- Release: LinuxMint 17.2 (rafaela)
- GNOME: 3.8.4 (Ubuntu 2015-12-02)
- Xorg: 1.15.1 (20 July 2017 07:11:13PM)
- CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
- Graphics: Intel onboard