Hide Forgot
Description of problem: I wrote the boot and dvd RHEL 7 public beta images to separate USB keys and booted off the boot.iso. Anaconda automatically detected the DVD image and was able to verify it successfully. I then get the following error: "Failed to setup installation source; check the repo url." Clicking "Done" brings me back to the main menu, but the installation storage never successfully gets configured. How reproducible: Always Steps to Reproduce: 1. dd the boot and dvd images to different USB keys 2. boot off of the boot.iso key 3. anaconda should automatically detect the dvd image and automatically default to it 4. Ensure that anaconda can verify the image 5. Observe the "Failed to setup installation source; check the repo url" error at the bottom of the screen
Created attachment 835529 [details] anaconda.log
Created attachment 835530 [details] storage.log
Created attachment 835531 [details] program.log
Created attachment 835532 [details] packaging.log
Why didn't you just boot from the DVD USB?
(In reply to Brian C. Lane from comment #5) > Why didn't you just boot from the DVD USB? For some reason this old dell workstation that I am installing to only boots off of a small 1G USB key that I have, and not my 30G SD card + USB card reader (which is the only device I could find that could fit the DVD image at the moment).
If you switch to a shell and look at /run/install/repo does it have the iso mounted? According to storage.log it mounted /dev/sdc there, but according to packaging.log it didn't like the repo /run/install/repo
(In reply to Brian C. Lane from comment #8) > If you switch to a shell and look at /run/install/repo does it have the iso > mounted? According to storage.log it mounted /dev/sdc there, but according > to packaging.log it didn't like the repo /run/install/repo Yes, the iso gets mounted to /run/install/repo
*** Bug 1090557 has been marked as a duplicate of this bug. ***
*** Bug 1113011 has been marked as a duplicate of this bug. ***
*** Bug 1172889 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0312.html