Public bug reported:
This bug follows bug 1650782.
Media has been verified, no errors.
In the other bug the installer crashed after I manually partitioned the disk in
a particular way through the setup program.
To try to workaround it instead of Install Ubuntu I selected Try Ubuntu.
Launched the setup from the icon and at the "how to install" I choose again
"custom partitioning".
Created a standard "boot" partition from there and assigned to mountpoint /boot.
Then opened a terminal and created a luks partition an LVM volume inside
it and three logical volumes
ubuntu@ubuntu:~$ sudo -i
root@ubuntu:~# pvcreate /dev/mapper/sdc7_crypt
Physical volume "/dev/mapper/sdc7_crypt" successfully created
root@ubuntu:~# vgcreate lvm /dev/mapper/sdc7_crypt
Volume group "lvm" successfully created
root@ubuntu:~# lvcreate -L 10G lvm -n swap
Logical volume "swap" created.
root@ubuntu:~# lvcreate -L 15G lvm -n root
Logical volume "root" created.
root@ubuntu:~# lvcreate -l 100%FREE lvm -n home
Logical volume "home" created.
root@ubuntu:~# mkfs.ext4 /dev/mapper/lvm-root
mke2fs 1.42.13 (17-May-2015)
Creating filesystem with 3932160 4k blocks and 983040 inodes
Filesystem UUID: fa438be2-433e-4aac-a8ca-8c483f14743f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
root@ubuntu:~# mkfs.ext4 /dev/mapper/lvm-home
mke2fs 1.42.13 (17-May-2015)
Creating filesystem with 17835008 4k blocks and 4464640 inodes
Filesystem UUID: 378a8d39-19bd-45b4-a3a5-451b887cfe7c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
root@ubuntu:~# mkswap /dev/mapper/lvm-swap
Setting up swapspace version 1, size = 10 GiB (10737414144 bytes)
no label, UUID=6a805aed-320a-462e-a7d0-931100716c6c
Went back to the setup program (which was opened at the custom partitioning
page) I pushed back and next again (to open the custom partitioning page again).
In that page I could see the new volumes and assigned the mount points from
there for home and root.
Then I clicked next and the setup finished copying files. Before, when trying
to do the same partitioning within the setup, it crashed immediately after
clicking on install (and that was already reported in bug 1650782)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CasperVersion: 1.376
Date: Sun Dec 18 00:16:09 2016
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
LANGUAGE=it_IT.UTF-8
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: grub-installer (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ubiquity-2.21.63.2 ubuntu xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650824
Title:
Installation crashes if done with a particular partitioning scheme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1650824/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
