fresh install (over running 17.04) failed

[Pnashdc]

I decided to try a fresh install over a running that was a bit sluggish, but otherwise fully operational. I selected a UEFI and the only other option I selected was to use only part of the drive (128G SSD). I expected to use a swap file, but the installer insisted on using a swap partition that previously existed on a second drive (2G HDD) that was used for a different OS on that drive. So, I also selected a swap partition on on the SSD.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CasperVersion: 1.380
Date: Sat Jul 22 15:45:12 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

[Phillip Susi (psusi)]

Your disk is currently partitioned to boot in bios mode, but you booted the installer in EFI mode. A warning message prompted you that this could be a problem and recommended performing a bios mode install instead, but you chose not to. You either need to perform the bios mode install, or partition the disk using GPT and set up an EFI system partition to install in EFI mode. This will be done for you if you choose the "use entire disk" guided install option.

[Pnashdc (pnashdc)]

I understand. However, my bug report was not an effort to determine a work
around. I am able to effectively install and use the new version.

The behavior is unexpected and, as far as I can tell, not clearly and
prominently documented (i.e., BY DEFINITION, it is a bug). Moreover, I
expect that the current behavior and documentation will be problematic for
many users.

Finally, the real issue is how the swapfile is managed by default. Again,
the actual behavior differs from the documented behavior.

On Thu, Aug 31, 2017 at 12:33 PM, Phillip Susi <email address hidden> wrote:

> Your disk is currently partitioned to boot in bios mode, but you booted
> the installer in EFI mode. A warning message prompted you that this
> could be a problem and recommended performing a bios mode install
> instead, but you chose not to. You either need to perform the bios mode
> install, or partition the disk using GPT and set up an EFI system
> partition to install in EFI mode. This will be done for you if you
> choose the "use entire disk" guided install option.
>
> ** Changed in: grub-installer (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1705848
>
> Title:
> fresh install (over running 17.04) failed
>
> Status in grub-installer package in Ubuntu:
> Invalid
>
> Bug description:
> I decided to try a fresh install over a running that was a bit
> sluggish, but otherwise fully operational. I selected a UEFI and the
> only other option I selected was to use only part of the drive (128G
> SSD). I expected to use a swap file, but the installer insisted on
> using a swap partition that previously existed on a second drive (2G
> HDD) that was used for a different OS on that drive. So, I also
> selected a swap partition on on the SSD.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.04
> Package: ubiquity 17.04.9
> ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
> Uname: Linux 4.10.0-19-generic x86_64
> ApportVersion: 2.20.4-0ubuntu4
> Architecture: amd64
> CasperVersion: 1.380
> Date: Sat Jul 22 15:45:12 2017
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
> ProcEnviron:
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> LC_NUMERIC=C.UTF-8
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/
> +bug/1705848/+subscriptions
>