Created attachment 1068381 [details] Partition scheme created by anaconda Description of problem: A partition scheme produced by Anaconda results in an un-bootable Atomic system. Version-Release number of selected component (if applicable): How reproducible: This reproduces in the official Atomic 22 ISO, the nightly 22 ISO, the 23 Alpha ISO, and the 23 Beta TC1 ISO. Steps to Reproduce: 0. The easiest way to reproduce this is to build a new VM. You'll need a large hard disk to experience the bug. I don't know how large it needs to be, but 50GB is too small and 128GB is enough. 1. Start an installation using an Atomic ISO, such as https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud_Atomic/x86_64/iso/Fedora-Cloud_Atomic-x86_64-22.iso 2. Select System > Installation Destination, then Other Storage Options > I will configure partitioning, then click the Done button. 3. Under New Fedora 22 Installation, click the "Click here to create them automatically" link. Actual results: The recommended partitioning scheme has a /home partition, as shown in the attached screenshot. That will prevent the system from booting. Expected results: The recommended partitioning scheme should be something that the OS can boot with. Ideally, it should mirror what the Automated partitioning option would produce, namely a small root partition and a docker-pool. Additional info: I think that the underlying problem is that OSTree expects to be able to hardlink everything under /, including /home. After reading how Atomic works, having a separate /home partition strikes me as very un-intuitive. If I just go for Automated partitioning instead of the list of steps I provided, Anaconda produces a good scheme. So far, I have preferred the steps I provided because they allow me to review the partition table changes before they are committed to the disk.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.