Previous attem[pts to upgrade 14.04 to 16.04 crashed - black screen, logged computer. I last attempt, I "tried" 16.04 whichworked. Then tried to instal 16.04 alongside 14.04 which crashed

Bug #1672423 reported by David French
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The instructions below are beyond my level/limited of pexpertise! Sorry!!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
Date: Mon Mar 13 14:53:56 2017
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
David French (dfrench987) wrote :
Revision history for this message
David French (dfrench987) wrote :

This latest problem/crash is the most recent installment in a series of difficulties, at the start of which I was using 14.04.
(Foolishly!) I was tempted by 16.04. Leaving what I thought was a reasonable period for early problems to be worked out, I moved to upgrade my 14.04 to 16.04 using the Update Manager.
When the upgrade was , ostensibly, finished, I re-booted my PC. At what I take to be the Grub screen, I clicked on the 16.04 line. The PC then worked through the customary procedure until the moment when the next screen should have been the opening desktop of what I hoped would be my new 16.04 installation. What followed was a black screen and a totally locked PC. Nothing worked. In the end I had to resort to the on/off switch on the back of my PC. I took this to mean that 16.04 had been largely installed - so the PC recognized it - but the problem was in the final moments.

On top of the 16.04 problem, my 14.04 would no longer worked - reacting to the attempts to upgrade it?

Eventually, on the Grub screen I clicked on 16.04 "startup", if I remember the word correctly and the programme opened. Given this I saved my critical files (Yes!! My backup was in total disarray!)

Looking for a fresh start, I downloaded a 16.04 file from Ubuntu and installed it .... black screen and locked PC. I suspected that my PC - with its 32 bit CPU - was rejecting 64 bit software, which I had used in desperation since I had no luck in my original search in locating a 32 bit download.

In reaction, I finally found a 32 bit download. This would not start in my PC and I had decided to re-download the 32 bit file.

At this stage, I wondered whether I could install the 64 bit download alongside my 14,04. which I had re-installed from an earlier download. Working from the 64 bit download, I started the 64 bit software on an "alongside my 14.04" basis. It worked fine - I must admit to my surprize and delight. Given this, I moved to install, on an alongside the 14.04 basis, the 64 bit software from the downloaded disc which I had just tested. The installation had barely started when it crashed and the bug report was prepared.

I hope this rather rambling resume of the path which culminated in this most recent crash helps you.

If you get any insights which might help my attempts to upgrade to 16.04 I would appreciate your guidance. Meantime ... back to resurrecting whatever remains of my 14.04

Revision history for this message
Phillip Susi (psusi) wrote :

Mar 13 14:48:55 ubuntu ubiquity: /dev/sda1 is mounted.
Mar 13 14:48:55 ubuntu ubiquity: e2fsck: Cannot continue, aborting.

This seems to indicate that tried to open the hard disk while the installer was running. Did you? If so, don't do that.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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