Created attachment 703998 [details] anaconda storage log Description of problem: Anaconda clears Memory Technology Devices (MTDs), which are not valid install targets. MTD is NAND flash, and requires special tools to erase/write it. Anaconda appears to see it as a standard block device (which is it not) and tries to use it (erase and relabel), destroying the contents of the device (in this case, the bootloader), rendering the system unusable. Version-Release number of selected component (if applicable): anaconda-18.37.12-1 How reproducible: Only tried once, since it is destructive (renders system unbootable) Steps to Reproduce: 1. include 'clearpart --all' in the kickstart file 2. Perform a kickstart install on a system with NAND flash (i.e., mtdblock0) 3. Actual results: Anaconda attempts to erase and relabel the MTD, which fails and results in an incomplete install, as well as wiping out the bootloader leaving the system unbootable. See storage and program logs included. Expected results: Install ignores MTD and proceeds to provision the system normally. Additional info: I tested this on a new Marvell (Matrix) server, which uses NAND flash to store the bootloader and other system configuration information. To test that this is the only issue, I added: ignoredisk --only-use=sda clearpart --all --drives=sda to the kickstart file to ensure MTD (the NAND flash device) was not used. The install completed successfully.
Created attachment 703999 [details] anaconda program log
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.