Booting with the following parameters: linux ks=http://chukar.rchland.ibm.com/Fedora17-sharpie-cdrom-minimal-ks.cfg Here is the kickstart file 8<---8<---8<---8<--- # Kickstart file automatically generated by anaconda. #version=DEVEL install cdrom lang en_US.UTF-8 keyboard us network --onboot yes --device eth0 --bootproto=static --ip=9.5.250.145 --netmask=255.255.255.0 --gateway=9.5.250.1 --nameserver=9.10.244.100 --hostname=sharpie.rchland.ibm.com --noipv6 network --onboot yes --device eth1 --bootproto=static --ip=9.5.252.203 --netmask=255.255.255.0 --hostname=nibbler.rchland.ibm.com --noipv6 timezone America/Chicago rootpw --iscrypted aaaa selinux --enforcing authconfig --enableshadow --passalgo=sha512 firewall --service=ssh --service=http # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --drives=sda part pv.008003 --grow --size=500 volgroup vg --pesize=32768 pv.008003 logvol swap --name=lv_swap --vgname=vg --grow --size=1024 --maxsize=6096 logvol / --fstype=ext4 --name=lv_root --vgname=vg --grow --size=1024 --maxsize=51200 part /boot --fstype=ext4 --size=500 part prepboot --fstype=prepboot --size=4 bootloader --location=partition --timeout=5 --append="rhgb quiet" %packages --nobase @core %end 8<---8<---8<--- Fails with the following message: Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated. failure: repodata/repomd.xml from anaconda-0: [Errno 256] No more mirrors to try.
Created attachment 580799 [details] anaconda.log
I changed the yaboot conf file on the DVD to not include a root= statement (from a suggestion by wwoods) and it still fails. [ 0.000000] Kernel command line: ro rd.luks=0 rd.md=0 rd.dm=0 ks=http://chukar.rchland.ibm.com/Fedora17-sharpie-cdrom-minimal-ks.cfg
[anaconda root@9-5-90-177 tmp]# mount | grep sr0 /dev/sr0 on /run/install/repo type iso9660 (ro,relatime)
[anaconda root@9-5-90-177 tmp]# ls -l /mnt total 4 drwxr-xr-x. 8 root root 4096 Apr 27 10:37 sysimage
lorax 17.11 added a symlink for /mnt/install -> /run/install (see commit 309bbbb). Try rebuilding with a newer lorax?
<mock-chroot>[root@chukar ~]# rpm -qa | grep lorax lorax-17.10-1.fc17.ppc64 <mock-chroot>[root@chukar ~]# rpm -qa | grep pungi pungi-2.10-1.fc17.noarch Will download the lastest lorax and pungi and rebuild, thanks!
<mock-chroot>[root@chukar ~]# rpm -qa | grep lorax lorax-17.16-1.fc17.ppc64 <mock-chroot>[root@chukar ~]# rpm -qa | grep pungi pungi-2.11-1.fc17.noarch [anaconda root@9-5-90-148 /]# ls -l /mnt total 4 lrwxrwxrwx. 1 root root 14 Apr 27 13:51 install -> ../run/install drwxr-xr-x. 8 root root 4096 Apr 27 14:24 sysimage [anaconda root@9-5-90-148 /]# mount | grep sr0 /dev/sr0 on /run/initramfs/live type iso9660 (ro,relatime) [anaconda root@9-5-90-148 /]# ls /run/install/ isodir ks.cfg repo [anaconda root@9-5-90-148 /]# ls /run/install/repo/ [anaconda root@9-5-90-148 /]# ls /run/install/isodir/
Hi, I'm seeing the same issue with the fc17 beta x86_64 dvd. The installer fails with the same message as the attached log. If the kickstart is graphical, the edit feature works, and automatically finds the correct mountpoint and repo for the local installation. However in text mode the edit function is unavailable. Either way, the problem can also be resolved by running the following command from a shell, which allows the installer to retry and continue correctly. ln -sf /run/initramfs/live /mnt/install/source The cd doesn't seem to be mounted in the place expected by the installer.
Thanks, Daniel. I have verified that creating that symbolic link [anaconda root@9-5-90-177 /]# ls /mnt/install isodir ks.cfg repo [anaconda root@9-5-90-177 /]# ln -sf /run/initramfs/live /mnt/install/source and then selecting "retry" will allow installation to continue.
anaconda-17.25-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.25-1.fc17
Package anaconda-17.25-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-17.25-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7353/anaconda-17.25-1.fc17 then log in and leave karma (feedback).
anaconda-17.25-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
This is not fixed.
Try this updates image: http://bcl.fedorapeople.org/updates/817084.img
817084.img fixed it.
anaconda-17.26-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.26-1.fc17
Package anaconda-17.26-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-17.26-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7623/anaconda-17.26-1.fc17 then log in and leave karma (feedback).
anaconda-17.26-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.