Bug 245315 - Fedora 7 kickstart installation failing with <= 256 MB RAM
Fedora 7 kickstart installation failing with <= 256 MB RAM
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i686 Linux
low Severity low
: ---
: ---
Assigned To: Jeremy Katz
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-06-22 08:24 EDT by Christian Mandery
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-30 09:29:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Christian Mandery 2007-06-22 08:24:00 EDT
Description of problem:
When trying to install Fedora 7 with the kickstart mechanism, the installer
fails with a message saying that the partition selected as the root partition
(e.g. sda1) could not be found.

If I try a manual installation (no kickstart) on the same machine, anaconda
tells me before starting the real installation that the system lacks enough
memory for the installation and that it will create a swap partition instantly
(which happens before the normal partitioning step).

Perhaps this pre-installation swap creation process screws up the later
partitioning done by kickstart.

This is the relevant part of the kickstart config:
bootloader --location=mbr
clearpart --all --initlabel
part swap --recommended
part / --fstype ext3 --size 1 --grow

Version-Release number of selected component (if applicable):
Fedora 7 Release

Steps to Reproduce:
1. Install with kickstart configuration for anaconda on a computer with 256 MB
RAM (or less).
Actual results:
Root partition device node does not exist. Installation aborts with an error

Expected results:
Installer should work with 256 MB RAM without additional swap or respect the
kickstart configuration when creating the swap partition.
Comment 1 Chris Lumens 2007-11-30 00:25:18 EST
I believe Jeremy's recent changes to when the partitioning steps get run in the
dispatcher should fix this up as all swap will be activated early on now.
Comment 2 Jeremy Katz 2007-11-30 09:29:16 EST
Yes, this should be helped with the early partitioning commit that we're doing now

Note You need to log in before you can comment on or make changes to this bug.