[LINUX] How to solve the problem that the login screen is not displayed forever on Ubuntu 19.04 because it stops at the logo at startup

Maybe it's a problem that can occur not only in 19.04 but also in other versions.

phenomenon

When Ubuntu starts, it keeps loading forever on a screen that seems to be loading something while displaying the logo ↓

I don't remember the log at the time of the investigation, but when I googled that it was timed out for some reason, my predecessor had already solved it, so I will write a solution after writing a memo. Originally, I think that the article I referred to should be posted as a reference, but since it was a long time ago that I solved this problem, I forgot where the article of my predecessor was ...

Cause

It seems that there was an unnecessary line in the mount configuration file for unknown reasons, and I was trying to mount by referring to that line and it timed out.

Solution

Check / etc / fstab and delete unnecessary lines that you don't think of. In my case, there was a description of / swapfile that I didn't remember making, so I deleted that line.

this

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx /               ext4    errors=remount-ro 0       1
//Description of swapfile

like this

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx /               ext4    errors=remount-ro 0       1

Since the fix, the problem of stuck on the logo screen has been resolved.