After install completes, Xubuntu 14.04.2 hangs on reboot

Bug #1419372 reported by Richard Elkins on 2015-02-07
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)

Bug Description

Started with a Linux Mint 17.1 (Rebecca) system such that 4GB is reserved for swap and Mint occupied 23GB, leaving 24GB available for Xubuntu. I booted into the thumb drive desktop. I successfully installed Xubuntu 14.04.2 from the ICON on the desktop.

When I went to reboot, Xubuntu hung. During the hand, I was able to Ctrl-Alt-F1 and attempt a reboot there. This resulted in a report of "I/O error".

Attached you should find a compressed tar archive of some logs, including the /var/log/installer directory.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Feb 7 17:20:30 2015
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/xubuntu.seed boot=casper quiet splash --
InstallationDate: Installed on 2015-02-07 (0 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150203.1)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Richard Elkins (texadactyl) wrote :
Richard Elkins (texadactyl) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed

I'm getting the same problem with a Installation under VMware Player 6.0.5. After a successful installation (installing packages and updates over the internet) the installer hangs on the reboot.

I added /var/log/installer in a tar archiv

Phillip Susi (psusi) wrote :

Can you be more specific about this IO error? Instead of trying to shutdown, can you run `dmesg` and see if there were any recent IO errors and exactly what they were?

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Richard Elkins (texadactyl) wrote :


"IO error" is what was displayed. There were no observable I/O errors on the display. The compressed tar file has the /var/log/installation directory. There are a lot of other logs in that archive.

It sounds like you want me to repeat the install-along-side type of installation and collect a dmesg log. Yes? Collect anything else at the point of the hang?

Phillip Susi (psusi) wrote :

I don't see anything out of the ordinary in the logs so my only guess is that whatever error happened caused the disk to go read-only so the logs could not be written, thus the only way to find out what went wrong is to run dmesg and look.

BTW: VMware Player runs stable and after a "hard reset" with Virtual machine->Power->reset guest, the system comes up in a clean state. :-) I'll attach log and configuration files.

Richard Elkins (texadactyl) wrote :

I was determined to get the whole contents of /var/log using Ctrl-Alt-F1 when I reproduced a hang the second time. Strangely enough, the reboot-hang did not happen the 2nd time. So, I backed off and tried a 3rd time and the reboot proceeded as expected.

All 3 times, I used the same preexisting Linux Mint 17.1 (Rebecca) installed partition and swap partition as a starting point and the exact same thumb drive contents of Xubuntu 14.04.2.

Note that this consumed a lot of time but it is worth it from my own experience as a recipient of bug reports.

In the interest of everyone's time, I'll close this as unreproducible. If Daniel Mehrman can reproduce his observations consistently, I suggest that he reopen this bug report or create a new one.

Richard Elkins (texadactyl) wrote :

On second thought, "incomplete", as it is defined on launchpad, seems to be correct.

I can repeat this bug with different machines, but on the other hand it's just a virtual software and there is no warranty that this could be a VMware Player bug.

So long no other people reporting a VMware "problem", we can close this ticket so far.

Well, with the latest iso version (20150218.1) the problem is gone and everything runs smoothy now.

Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers