Description of problem: anaconda seems confused at fdisk commands in %pre section in ks.cfg. The fdisk command does run, but the partitions created with fdisk can not be mounted, even though file systems are created. Version-Release number of selected component (if applicable): The default installation FC4 installation media. How reproducible: Every time. Steps to Reproduce: 1. put the following commands in %pre section in ks.cfg: cat <<FDISKEND > /tmp/fdisk.txt ## sub commands will be input for fdisk to create partitions o ... wq FDISKEND dd if=/dev/zero of=/dev/sda bs=512 count=1024 ## zero out mbr again. fdisk /dev/sda < /tmp/fdisk.txt ... ##In the normal ks.cfg partition definition I have the following file system defined. part / --fstype ext3 --onpart sda1 part swap --onpart sda6 part swap --onpart sda7 part swap --onpart sda8 part /usr --fstype ext3 --onpart sda5 part /example --fstype ext3 --onpart sda9 part /var --fstype ext3 --onpart sda10 part /0 --fstype ext3 --noformat --onpart sda11 ... 2. Have a look of the installation screens after press "ctrl-alt-F2", "ctrl- alt-F2", ... "ctrl-alt-F5". it shows that the file systems are created and no errors are thrown out. 3. run "df -k" on the interactive shell screen, but it doesn't show entries for /mnt/sysimage/{usr,var,example,0} that will normally show if we use the default graphical partitioning screens for interactive installation. Actual results: "df -k" shown only the /mnt/sysimage entry, and so the installation in fact install FC4 OS into memory! not onto hard disk! Expected results: "df -k" should report all file systems defined in ks.cfg. like: /mnt/sysimage /mnt/sysimage/usr /mnt/sysimage/var /mnt/sysimage/example /mnt/sysimage/0 Additional info:
Can you provide your full ks.cfg as well as /tmp/anaconda.log from the installer?
>12 months with no info.