I have a weird issue with the installer.
I have a kickstart file that does not define the partition layout. Anaconda should automatically prompt the user for the disk layout.
I have a network install that does work this way. The same distro tree is copied from the network install and split into three CDs, genhdlist, comps rebuilt, etc... However, using the CD to install I get a error: "could not allocated requested partitions:"
Anaconda log: Log for CD local install: moving (1) to step partitionobjinit moving (1) to step autopartitionexecute
Log for NFS install: moving (1) to step partitionmethod
Any suggestions?
-steve
Stephen Mah wrote:
I have a weird issue with the installer.
I have a kickstart file that does not define the partition layout. Anaconda should automatically prompt the user for the disk layout.
I have a network install that does work this way. The same distro tree is copied from the network install and split into three CDs, genhdlist, comps rebuilt, etc... However, using the CD to install I get a error: "could not allocated requested partitions:"
Anaconda log: Log for CD local install: moving (1) to step partitionobjinit moving (1) to step autopartitionexecute
Log for NFS install: moving (1) to step partitionmethod
Any suggestions?
Maybe look at the 'clearpart' kickstart option too (if you haven't already!)
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom-guide/s1-kick...
It could be that there are existing partitions, or an un-initialized disk that is spooking out anaconda and it doesn't know what to do next.
pantz
On Tue, 2004-04-27 at 16:18, Stephen Mah wrote:
I have a weird issue with the installer.
I have a kickstart file that does not define the partition layout. Anaconda should automatically prompt the user for the disk layout.
I have a network install that does work this way. The same distro tree is copied from the network install and split into three CDs, genhdlist, comps rebuilt, etc... However, using the CD to install I get a error: "could not allocated requested partitions:"
Anaconda log: Log for CD local install: moving (1) to step partitionobjinit moving (1) to step autopartitionexecute
Log for NFS install: moving (1) to step partitionmethod
It looks like you may have some remnant of partitioning in your ks.cfg. Can you post it?
Forrest
Taylor,
Thank You, that pointed me in the right direction. I have a %pre script that prompts the user for "advanced partitioning", then it deletes partitioning info in the kickstart file. So, I have a ks.cfg (standard install) file & an expert.cfg (partitioning) file. I had the impression that anaconda re-reads the kickstart file as "ks.cfg". But for whatever reason, it only does that during an nfs install. For a CD install, I'll have to leave the file as expert.cfg.
I'll test it soon.
thanks again steve
Taylor, ForrestX wrote:
On Tue, 2004-04-27 at 16:18, Stephen Mah wrote:
I have a weird issue with the installer.
I have a kickstart file that does not define the partition layout. Anaconda should automatically prompt the user for the disk layout.
I have a network install that does work this way. The same distro tree is copied from the network install and split into three CDs, genhdlist, comps rebuilt, etc... However, using the CD to install I get a error: "could not allocated requested partitions:"
Anaconda log: Log for CD local install: moving (1) to step partitionobjinit moving (1) to step autopartitionexecute
Log for NFS install: moving (1) to step partitionmethod
It looks like you may have some remnant of partitioning in your ks.cfg. Can you post it?
Forrest
anaconda-devel@lists.fedoraproject.org