Ubuntu 17.10 hangs on reboot after installation

Bug #1729437 reported by LinuxUser
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned
plymouth (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After installing ubuntu 17.10 desktop a window asking for a reboot opens.
After selecting the reboot I get the following error message from systemd: 'A start job is running for Hold until boot process finishes up (21s / no limit)'
The system hangs and continues to display this error message.
As far as I can tell this message comes up during the shutdown part of the reboot.

I used 'ubuntu-17.10-desktop-amd64.iso' as installation image on a usb drive, I started the installer by selecting 'Try Ubuntu without installing' in the boot menu and clicking the installer icon after the live systems boot up.

Happily I also found a workaround. Before booting the live system I changed some boot parameters with grub from 'quiet splash' to 'noplymouth' and then the installation worked and a proper reboot after installation was possible.

To make things clearer I have attachted a screenshot of the error message.
I encountered this bug on Lenovo ThinkPad T470 with an nvme SSD.

Revision history for this message
LinuxUser (linux-user-42) wrote :
tags: added: artful
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1729437/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
no longer affects: plymouth
Revision history for this message
Jack Simmons (ganesa-9) wrote :

On a clean install of Ubuntu 17.10 I get a similar error. Installation on new hard drive works without a glitch, and the "You must restart your machine yada yada yada...' popup appears. I then click on the restart button in the popup, the system begins the restart cycle, but goes to a black screen with a blinking text cursor (no error message). No commands work in this screen and I have to force shutdown. Then I restart the machine, and to all appearances Ubuntu 17.10 is present and working... but it makes me nervous.

I've tried a clean install on a different hard drive and get the same results. Any ideas about what might be going on?

CPU = AMD FX-8350
Board = M5A78L-M/USB3
Memory = Kingston HyperX FURY 16GB Kit (2x8GB) 1600MHz DDR3 CL10 DIMM
SSD = SanDisk SSD PLUS 120GB Solid State Drive - SDSSDA-120G-G27

Ubuntu 17.10.1 from : https://www.ubuntu.com/download/desktop/contribute/?version=17.10.1&architecture=amd64 installed on a USB stick for installation.

What am I doing wrong, or is this a known issue?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time.

Changed in ubuntu:
status: Confirmed → Incomplete
Changed in plymouth (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]

Changed in plymouth (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.