Created attachment 1481087 [details] Photograph of error message Description of problem: Anaconda crashes during "Configuring storage" phase with message: The following error occurred when installing. This is fatal and installation will be aborted. mount ['bind'. '/mnt/sysimage/tmp', '/mnt/sysimage/ostree/deploy/fedoraatomic/deploy/ b92cd00155717a415e3185do9fdfd9379b52f1142516939f99cc045bd82do/ymp] exited with code 32 Version-Release number of selected component (if applicable): Fedora Atomic 28 image downloaded from Fedora web site. Verified file checksum OK. Wrote iso image to usb stick successfully with media writer. How reproducible: Peforming a bare metal install. Just boot from the USB stick and invoke anaconda installer. Configure system in normal way; I setup BIOSBOOT, /boot and /boot/efi as partitions and remaining space as LVM managed. Created /, swap, /home, /tmp and /var with free space on a SATA attached disk drive. Anaconda installed OS, but failed when configuring its own disk configuration. Steps to Reproduce: 1. Create USB stick with Fedora Atomic version 28 2. Boot from USB stick 3. Answer configuration questions and start automated installation Actual results: Aborted installation Expected results: Working, bootable system. Additional info:
Hello, Could you please provide us installation logs. You can find them in /tmp/*.log directory.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.