0

My Gnome installation (Ubuntu 18.04) appears to be broken. After I log in, it displays some log messages and hangs. The last message says in effect "Starting Gnome." I've tried removing the proprietary graphics drivers and switching to a radically different graphics card; neither measure helped.

I assume, but am not sure, that Ubuntu itself is intact. It appears to work just as it should when I boot to rescue mode.

How can I repair my system with a minimum of disruption?

I found instructions for installing Gnome...

https://linuxconfig.org/how-to-install-gnome-on-ubuntu-18-04-bionic-beaver-linux

...and for repairing Linux...

https://www.ostechnix.com/how-to-fix-broken-ubuntu-os-without-reinstalling-it/

The first set of instructions are admirably simple: install a few packages. It seems to me that I should be able to uninstall the broken Gnome by removing the same packages in reverse order, but I don't know whether that is the best approach; I suspect that after I reinstall Gnome I'll have to reinstall all of my graphic applications. I'd prefer instructions specifically for repairing Gnome, but I haven't found any.

The latter instructions assume a system that functions in rescue mode, but don't distinguish between "repairing" Ubuntu and Gnome, so I'm not sure just what they're meant to accomplish. The system's useless as it is, but I'd rather know what this experiment is supposed to do before I undertake it.

Perhaps I should just restore the Linux partition with dd. If I save my current data first I won't lose anything. The only disadvantage is that I'll have to reconstruct whatever software I installed or reconfigured after my last backup.

1 Answers1

0

To check your file system...

  • boot to a Ubuntu Live DVD/USB in “Try Ubuntu” mode
  • open a terminal window by pressing Ctrl+Alt+T
  • type sudo fdisk -l
  • identify the /dev/sdXX device name for your "Linux Filesystem"
  • type sudo fsck -f /dev/sda5, replacing sdXX with the number you found earlier
  • type sudo fsck -f /dev/sda6
  • repeat the fsck command if there were errors
  • type reboot

To check your disk's SMART...

Start the Disks application. Select your HDD. Go to the "hamburger" icon and select SMART Data & Tests. Get screenshot(s) of the SMART Data and edit them into your question.

The SMART values says that the disk is OK. The only problem is there's a ton of command timeouts. I suspect a bad SATA cable.

Boot crashes...

Take pictures of your boot screen output. Either edit them into your question, or put them on imgur.com.

Update #1:

With the command timeout errors on the SATA disk subsystem, and we tried new SATA cables, and a backup drive worked fine when reinstalled back into the system, we conclude that the primary HDD is defective, or needs to be re-initialized and Ubuntu reinstalled.

heynnema
  • 73,649