Ubuntu hangs up [closed]

describe in more detail the symptoms, os version, please. Is there a second operating system on the computer?

In general, the algorithm is as follows:

If you reach the choice of options for the operating system / kernel versions, you are in the grub bootloader. Choose the last Ubuntu, hit e (hint below), find the lines in the editor

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

if there is, then

GRUB_CMDLINE_LINUX=""

change to

GRUB_CMDLINE_LINUX_DEFAULT="--verbose nosplash debug"

GRUB_CMDLINE_LINUX="--verbose nosplash debug"

look at the mistakes.

if it is possible to boot from the flash drive: find your hard disk / ssd, go look at /var/log/boot.log , /var/log/syslog , /var/log/Xorg.0.log

if you need to read the systemd logs, then journalctl -D путь_к_каталогу_с_логами can do this from a flash drive

if it doesn't even reach the bootloader - probably - mbr flew away from you (the disk dies, the Windows overwrites, accidentally deleted something)

common causes of errors:

• Video card drivers after system updates.
• incorrect updating of the system due to the fact that the left repositories were installed, after that some of the system libraries were updated, some were not, and together they could no longer work (this can affect the video, by the way). Detected, as a rule, by the fact that apt-get update && apt-get install does not work apt-get update && apt-get install
• flyback loader / mbr

How to treat (from what I came across):

• if the video drivers have flown: boot into Advanced options for Ubuntu , boot into the console, from a flash drive or download a video driver using a text browser and, accordingly, installation instructions, install it in console mode. (or just demolish)
• incorrect system update is the worst that I came across, there are no exact recipes, once I spent 6 hours just from the principle to cure. usually just reinstall the system.
• mbr (boot / grub) - google.

ps, if you boot from the flash drive and see the desktop and find your hard drive, rejoice, the drive is alive and the video card is not dead. and switching to the console does not work because of the hung video drivers. those. you can try, for example, make ctrl+alt+f1 and blindly type cd / ; sudo updateb; find . cd / ; sudo updateb; find . You will most likely see the hdd indicator blink. it means the system is alive

I also advise - for the future - set up (neatly) sshd so that you can log in to a computer without a flash drive just from the local network (or - if you set it neatly and forwarded ports - at least via a mobile phone) and correct the settings

Ps One of the best indicators of a hung system is the reaction to pressing the caps lock. if a small light comes on - not everything is so bad. If it does not work, Pts are bad, you will have to thoroughly heal.

What could be the reasons for the hangup of Ubuntu?

ubuntu is the proper name of one of the gnu / linux operating system distributions . the concept of “hung” is generally not applicable to the distribution kit.

and “stuck” you, judging by the symptoms, the linux program.

The first tool for diagnosing problems that this program encounters is its circular message buffer. You can view its contents with the dmesg program. Naturally, once the linux program itself is frozen, it will not be possible to launch the dmesg program and see the contents of the buffer, alas.

there is a hope that the implementation of the syslog daemon installed on your system (often rsyslog ) continues to work and the disk subsystem is still functioning. thanks to which the information from the ring buffer is written to /var/log/dmesg and / or /var/log/kern.log .

In these files, and it is necessary first to look for information about the problems. just note that during the boot process, the old /var/log/dmesg file will be renamed to something like /var/log/dmesg.0 , and /var/log/dmesg will be recorded in /var/log/dmesg starting from the current system boot.