[Bug 1412178] Re: Installer for 14.04 crashes

[Todd Austen]

Ok, i did an MD5sum check on the ISO, "ubuntu-14.04.1-desktop-
amd64.iso", and it matches what is listed on the UbuntuHashes webpage:

119cb63b48c9a18f31f417f09655efbd

Next, i checked the installation USB stick (i created a USB stick using
the PenDriveLinux universal USB installer).  Note, i did the same thing
with a 32-bit version of Ubuntu 14.10 (ie.
ubuntu-14.10-desktop-i386.iso) and it installed just fine on my Samsung
netbook.  So running MD5sum check:

119cb63b48c9a18f31f417f09655efbd

Same result.  So, it would seem that my installation media (a USB stick
in my case) is just fine.

Now, one thing I did not mention in my bug report, is that i'm actually
trying to install Ubuntu on a separate physical drive.  So i want to end
up with a dual-boot.  I have Win7 (64-bit) installed on the first drive,
/dev/sda and i installed Ubuntu on the second drive, /dev/sdb.  I'm
wondering if this is causing the problem?  Also, my first disk is an
MBR-based disk and my second disk is GPT-based.  My bootloader is UEFI-
based (rather than BIOS).

You see, when i installed the 32-bit version of 14.10 on my netbook, it
was successful, but there i have only one physical disk (/dev/sda).

I have read through some other bug reports, and my issue looks like it
may be related to Bug # 1303790, "In UEFI mode, installer crashes if OS
is installed on 2nd drive and grub installs successfully but ubiquity
doesn't think so".  Same failure pattern, installer fails on the
"Ubiquity" package.  But according to this bug, the install is actually
successful, it just reports that it has failed, and it messes up Grub.

So i'm wondering, as a workaround, if I fixed my Grub bootloader so that
Linux boots off of /dev/sdb (rather than /dev/sda) and then used a
program like EasyBCD to modify my Windows bootloader to present 2
options, and use the Windows bootloader for dual-boot presentation
(rather than the Grub bootloader), if this would provide me a
workaround?

I'm reopening this bug report, and setting back to "New".  I'll let the
experts assess whether this is the same bug as the one i mentioned, or
something different.

Tks,
Todd


** Changed in: ubiquity (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1412178

Title:
  Installer for 14.04 crashes

Status in ubiquity package in Ubuntu:
  New

Bug description:
  This is happened twice in a row for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.18.8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CasperVersion: 1.340
  Date: Sun Jan 18 10:17:06 2015
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper only-ubiquity quiet splash --
  LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1412178/+subscriptions