Ubuntu Bionic hangs during boot
by achim_59 from LinuxQuestions.org on (#4WXEF)
This actually applies to my neighbour's laptop, but he's not very technically minded and I try to help him when he has problems. To make it easier I'll just refer to him as D.
He recently brought his laptop over, saying he couldn't log on. When I fired up the machine it started the usual way, but then it just hung on the splash screen. He left the machine with me and I've been trying to figure out what's wrong. It isn't anything that he installed, since he always calls me before installing anything new.
The following link suggests that it has something to do with the snapd service:
https://askubuntu.com/questions/1051...dist-upgrade-o
However, D's machine doesn't just have a long delay, it hangs completely, so I think it is a different problem. Besides, that askubuntu post talks of kernel 4.15.0-24 and D's machine is booting with 4.15.0-72.
Another askubuntu post says that the problem is with Wayland (replacement for X) and suggests simply disabling it:
https://askubuntu.com/questions/1149...5-after-update
I tried that, but the problem persisted.
Yet another site (https://itsfoss.com/fix-ubuntu-freezing/) suggests the problem lies with the NVIDIA graphics drivers. I followed the steps described, and sure enough the boot started with a non-graphics splash screen and eventually went further (like in the old days when you got the log output as part of the boot sequence). Sadly, this process also hangs eventually. The last few messages are as follows:
Code:[FAILED] Failed to start Snappy daemon.
See 'systemctl status snapd.service for details.
Starting failure handling of the snapd snap...
Starting Wait until snapd is fully seeded...
[ OK ] Stopped Snappy daemon.
Starting Snappy daemon...
[ OK ] Started Failure handling of the snapd snap.
[ OK ] Started Snappy daemon.
[ OK ] Started Wait until snapd is fully seeded.
[*** ] A start job is running fo Hold unt...finishes up (14min 30s / no limit)Since I started typing this stuff a couple of cleanup messages were added to that list, but the clock is still running and the boot up is still not finished.
That's where I'm at now. There is a possibility that the boot problems can be fixed as described here:
https://linuxconfig.org/ubuntu-boot-repair
I guess I'll try that, but judging from what I've seen so far, an automated boot repair probably won't do the trick.
What I'd like to try is to get the latest update in the hope that that will fix the problem. It should also be possible with apt-get to re-install the snapd package explicitly. Trouble is, there's no networking running when I start in recovery mode. There is an option to try starting it, but from what I've read, it doesn't work properly. Certainly the one time I tried that option it didn't work. I notice on the display of D's laptop, that the network manager script dispatcher service has been started, but whether that means I'd be able to run apt-get is another matter. Besides, the snapd seeding process is still not finished after 30+ minutes.
I'm really grasping at straws at this point. can anybody provide me with a hint as to what else I could try?
If I manage to solve the issue, then I'll describe what I did so that others with the same problem can benefit from my experimentation. I'll also mark this thread as solved if I get that far.
All suggestions welcome.
He recently brought his laptop over, saying he couldn't log on. When I fired up the machine it started the usual way, but then it just hung on the splash screen. He left the machine with me and I've been trying to figure out what's wrong. It isn't anything that he installed, since he always calls me before installing anything new.
The following link suggests that it has something to do with the snapd service:
https://askubuntu.com/questions/1051...dist-upgrade-o
However, D's machine doesn't just have a long delay, it hangs completely, so I think it is a different problem. Besides, that askubuntu post talks of kernel 4.15.0-24 and D's machine is booting with 4.15.0-72.
Another askubuntu post says that the problem is with Wayland (replacement for X) and suggests simply disabling it:
https://askubuntu.com/questions/1149...5-after-update
I tried that, but the problem persisted.
Yet another site (https://itsfoss.com/fix-ubuntu-freezing/) suggests the problem lies with the NVIDIA graphics drivers. I followed the steps described, and sure enough the boot started with a non-graphics splash screen and eventually went further (like in the old days when you got the log output as part of the boot sequence). Sadly, this process also hangs eventually. The last few messages are as follows:
Code:[FAILED] Failed to start Snappy daemon.
See 'systemctl status snapd.service for details.
Starting failure handling of the snapd snap...
Starting Wait until snapd is fully seeded...
[ OK ] Stopped Snappy daemon.
Starting Snappy daemon...
[ OK ] Started Failure handling of the snapd snap.
[ OK ] Started Snappy daemon.
[ OK ] Started Wait until snapd is fully seeded.
[*** ] A start job is running fo Hold unt...finishes up (14min 30s / no limit)Since I started typing this stuff a couple of cleanup messages were added to that list, but the clock is still running and the boot up is still not finished.
That's where I'm at now. There is a possibility that the boot problems can be fixed as described here:
https://linuxconfig.org/ubuntu-boot-repair
I guess I'll try that, but judging from what I've seen so far, an automated boot repair probably won't do the trick.
What I'd like to try is to get the latest update in the hope that that will fix the problem. It should also be possible with apt-get to re-install the snapd package explicitly. Trouble is, there's no networking running when I start in recovery mode. There is an option to try starting it, but from what I've read, it doesn't work properly. Certainly the one time I tried that option it didn't work. I notice on the display of D's laptop, that the network manager script dispatcher service has been started, but whether that means I'd be able to run apt-get is another matter. Besides, the snapd seeding process is still not finished after 30+ minutes.
I'm really grasping at straws at this point. can anybody provide me with a hint as to what else I could try?
If I manage to solve the issue, then I'll describe what I did so that others with the same problem can benefit from my experimentation. I'll also mark this thread as solved if I get that far.
All suggestions welcome.