On 12/16/2016 10:24 AM, Richard Ibbotson wrote: > On Friday, 16 December 2016 17:13:35 GMT Georgi Tsanov wrote: >> Thanks to responding i ran blkid to see the partitions and ran fsck >> comman only for swap partition (dont know what this is) and home >> partition. when i tried to run the fsck command for the root >> partition it said that the root is mounted and it can cause damage. >> still cant figure out how to bring the gui back.. > > As a root user do... fdisk -l This will give you a list of > partitions. Which might look like... > > /dev/sda1 > /dev/sda2 > /dev/sda5 > > You have to work out which one to umount. In this case it might be > .... ' umount /dev/sda2 '. Doing that would unmount the drive or > partition. You can then run fsck. If you have to fsck the root partition (that is, the partition mounted as "/"), you'll probably need to boot a live disk in rescue mode, then fsck the partition. That shouldn't be necessary however...the boot process will generally fsck the root partition if it appears to need it. Having to fsck it manually would be rather abnormal. If you're not getting a GUI login, then the first thing to check are the system logs by getting a console login (ALT-F2) and doing things like "journalctl -a -b" to see the log entries for the current boot (or "journalctl -a -b -1" to see them for the previous boot). Are you running Wayland or Xorg? If it's Xorg, check the /var/log/Xorg.0.log file. If Wayland, try logging in using Xorg to see if its something with Wayland (there are known compatibility issues with Wayland in some cases). ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Okay, who put a "stop payment" on my reality check? - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
