Description of problem: The F10 DVD iso stored on one partition, with the install booted from the extracted vmlinuz/initrd.img from the DVD iso, fails to find the install files. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Extract vmlinuz and initrd.img from DVD iso to /boot 2. Add new section to /boot/grub/grub.conf to boot the install 3. Copy the images directory and contents from the DVD iso to the same directory as the iso file. 4. Boot and select HD install Actual results: At the point where the HD install media directory is defined anaconda adds /images/install.img and fails to recognise the existing install.img file even though the path is correct. Expected results: The install should continue as normal Additional info: So I tried to follow http://fedoraproject.org/wiki/Anaconda/Options and amended the boot line to include repo=hd:/dev/sda6:path/to/iso stage2=hd:/dev/sda6:path/to/install.img and booted - it gives the same error again. I have also tried the "askmethod" added to the kernel line at boot and it makes no difference.
I have made some progress in finding where the solution to this bug lies. I am defining the path on my partition where the iso is stored as Local/home/mike/isos/f10 which is on a partition /dev/sda6 and usually mounted as /opt If I examine the VT console output using ctrl-Alt-F3 then the output shows: 21:35:44 INFO : partition /dev/sda6 selected 21:35:44 INFO : mounting device /dev/sda6 for hard drive install 21:35:44 INFO : Path to stage2 image is /mnt/isodirLocal/home/mike/isos/f10/images/install.img 21:35:44 ERROR : failed to open /mnt/isodirLocal/home/mike/isos/f10/images/install.img: No such file or directory This clearly seems to be due to a missing "/" between isodir and Local Hence by defining the path (differently to all previous versions of Fedora installs to HD) as /Local/home/mike/isos/f10 i.e. adding a leading "/" to the path, and restarting the install this no longer gives the failed to open error and the install now continues. I don't know if this is an intentional undocumented feature of the f10 install or a bug in the anaconda code? However this should certainly be flagged up for the common bugs for f10, and the code should be fixed. I don't know if this is related to the other reports of problems finding the images/install.img file for the nfs install case also?
I have now gone back and re-checked the official install guide at http://docs.fedoraproject.org/install-guide/f10/en_US/sn-installing-from-harddrive.html and one sees that, for the HD install case, the guide says "Also specify the Directory holding images....": The table shows: Partition type Volume Original path to files Directory to use VFAT, NTFS D:\ D:\Downloads\F10 Downloads/F10 ext2, ext3 /home /home/user1/F10 user1/F10 One can see that the official documentation in the latter case omits the crucial "/" on the right hand side that is required before user1/F10 i.e. it should be /user1/F10 in this case. This needs to be amended in the official F10 install guide since the released F10 isos cannot be changed at this stage.
This is definitely a bug in the documentation, as you really should be specifying a leading slash on the path name to be really correct. I know no one here tests paths like that, so we really do need to be making sure the docs match. Docs guys: Please make sure the documentation specifies that the paths you should use for installing from hard drive start with a slash. Thanks.
http://git.fedorahosted.org/git/docs/install-guide.git?p=docs/install-guide.git;a=commit;h=918fc10e53b436c4a71cc5fbb623b3ca59d64daf Committed to install-guide git repo. Karsten, can we get Dave or another Docs person to republish and create new TGZ and ZIP versions on the web site, then close the bug?
Still not implemented as of 3rd January - can this be actioned and closed?
(In reply to comment #4) > http://git.fedorahosted.org/git/docs/install-guide.git?p=docs/install-guide.git;a=commit;h=918fc10e53b436c4a71cc5fbb623b3ca59d64daf > > Committed to install-guide git repo. Karsten, can we get Dave or another Docs > person to republish and create new TGZ and ZIP versions on the web site, then > close the bug? Nope, there is still no one besides the two of us who can make that archaic system work. I just rebuilt from git to include all the bugfixes, then published tarball, zip, and regular HTML on docs.fp.o. It should come live later this afternoon. Thanks for the bug fix, btw.
Excellent news.....thank you.