The most common cases of ext[234] with one whole-disk / and no swap worked fine (768MiB RAM)---meaning upon reboot, I could log into the install and browse the web, open a Konsole, and sudo apt-get update.
EDGE CASES:
XFS/JFS/btrfs with one whole-disk / and no swap worked fine.
ext[234]/XFS/JFS/btrfs 1024 MiB /boot, no swap, and a (remainder of disk) ext[234]/XFS/JFS/btrfs / worked fine.
Any use of physical backing for crypto failed, e.g.,
ext[234]/XFS/JFS/btrfs 1024 MiB /boot, no swap, and a (remainder of disk) crypto backend failed (no prompt to enter a passphrase, no visual indication---unlike with Ubuntu-MATE 17.10 RC desktop installer with which this step was successful) with an ubiquity traceback when I clicked the created partition and chose Change, then dumped me into a live session where I could restart the installer (upon which attempting to follow the same steps reproduced the traceback and the installer exited; or I could choose different non-crypto options, which worked fine).
Swap-only for the whole disk generated a traceback when I clicked the created partition and chose Change. I could restart the installer, as the above steps outline.
Attempting to use FAT(16|32) as whole-disk / correctly generated an error message after which I could choose non-FAT(16|32) options, as the above steps outline.
Attempting to choose Do not use this.. correctly generated an error message after which I could choose other options, as the above steps outline.
|