Dear original submitter - can you please reconfirm the disk partitioning scheme used? Was it LVM with separate /boot?
One thing to note is that from the logs the reporter's machine suggests that it is installed on top of LVM. Currently LVM is ambiguous from auto-resize point of view. >From implementation point of view, the resize (aka alogside install) is >available when: * existing installation is single full disk (e.g. full disk linux/windows) * where there is sufficient amount of free space available in that partition to perform a resize * there is sufficient amount of space left to install ubuntu if resize is attempted * the partitioner understands how to resize that file system This is pre-requisites =) Now the caveats * the resizing may fail if the extends are allocated in a such a way that a resize without defragmentation is not possible, or not supported enough by existing tools. This is ambiguous from LVM point of view, because: * do you want to resize the VG & create a separate normal partition - OR - do you want to create ubuntu lvm volumes within that group? * where should the boot loader go to? Sorry for not checking the auto-collected logs more carefully when first looking into the bug. Thank you mpt for updating the Partitioning Options Matrix ;-) I was previously interpolating options while reading it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040996 Title: Not offered "Install alongside" if other OS isn't Windows or Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1040996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
