Hide Forgot
Created attachment 532376 [details] kickstart script In Fedora 16 final, I am seeing the following error during a kickstart install (unfortunately, the resolution of the screen is wrong and I can't find the error message in any of the logs in /var/log or /tmp, so my transcription isn't 100% correct): """ The following errors occurred with your partitioning: You have not defined a root partition ??? which is required for installation of Fedora to continue. You have not created a bootable partition. This can happen if there is not enough space on your hard drive ??? for the installation. Press OK to exit the installer. """ My partitioning commands in kickstart are telling it to reformat existing partitions (this is what's in the included file "part.include"): """ part /boot --onpart=LABEL=boot --label=boot --fstype ext3 part / --onpart=LABEL=root --label=root --fstype ext4 part swap --onpart=LABEL=swap --label=swap --fstype=swap part /local --onpart=LABEL=local --noformat """ Doing an `ls /dev/disk/by-label` gives "Anaconda boot local root swap", showing that all of these partitions exist. If I do "mount LABEL=boot /mnt/tmp", then `df -h` shows that this partition has size 485M. I will attach my kickstart script and various logs. Please let me know if I am omitting anything important or helpful.
Created attachment 532377 [details] storage.log
Created attachment 532378 [details] program.log
By the way, it's possible that the error reads "You have not defined a boot partition" or "You have not defined a root partition". The text on the screen isn't entirely legible.
Please look in /tmp for something that looks like logs from your ks %pre and attach them. Also, please attach /tmp/part.include and /tmp/anaconda.log. Thanks.
Created attachment 532395 [details] part.include The part.include file was in the description, but I'm now attaching it as well.
Created attachment 532396 [details] anaconda.log
Created attachment 532397 [details] log from preinstall script
It is saying both: there is no root partition and there is no bootable partition. It's I'm not sure what the issue is, but I have found that by adding 'clearpart --none' you will get the expected behavior.
Anaconda's processing of the clearpart command includes removing the "Clear Disks Selector" screen/step from the install flow. That screen/step initiates a reset of the storage instance. So, when there is no clearpart command, we reset the storage instance, which nukes the actions that reflect the user's partitioning commands. The only case this doesn't hit is autopart, since those requests have special representation that does not get destroyed by a reset. So, for the time being, you need to either use clearpart or autopart.
Adding "clearpart --none" seems to work around the problem.
so that means that you effectively can't re-use existing partitions? just to get this clear for commonbugs. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #11) > so that means that you effectively can't re-use existing partitions? Yes, but the extent is limited to those using kickstart.
(In reply to comment #11) > so that means that you effectively can't re-use existing partitions? just to > get this clear for commonbugs. No - you _can_ reuse partitions. You just have to explicitly use 'clearpart --none' instead of not putting anything at all. Make sense?
(In reply to comment #13) > > No - you _can_ reuse partitions. You just have to explicitly use 'clearpart > --none' instead of not putting anything at all. Make sense? Or, you can't reuse partitions unless you workaround the problem by adding "clearpart --none" (which the documentation states to be the default but due to this bug actually isn't). It just depends on how you look at it.
dlehman: thanks, that helps. Wasn't aware what clearpart --none did exactly. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.