Bug 466008
| Summary: | Anaconda installer crashes before installing anything | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bert Seltzer <bert.seltzer> | ||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | rawhide | CC: | bert.seltzer | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i386 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2008-10-07 20:55:17 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Bert Seltzer
2008-10-07 17:56:40 UTC
Please attach the exception to this bug report so we have some idea what's going on. Thanks. I've tried saving the report, but afterward, it's no where to be found. Suggestions?? Regards, Bert Before you reboot, it's /tmp/anacdump.txt. You can switch over to tty2 and scp it to another machine if you have somewhere to copy it to. Or you could take a picture. There's no way to get the report off the system. Like I said, anaconda never asks for NIC configuration. When I tried to save the report or scp it to another box on my LAN, anaconda does throw up a screen asking for network configuration but does not allow any input. If I try to manually get an interface up from tty2, I get no such device not matter what interface I use. I did try to take a picture but 1) my camera records too much Moire effect to make the image readable, and 2) I'd need to upload several dozen pictures to capture the entire log. - Bert We don't need the entire thing (most of the time) - just the first part with the file names and line numbers, and then the next line that has the actual error message. Created attachment 319694 [details]
first few lines of the report
here's the first few lines
Created attachment 319695 [details]
and the next ten lines or so
more...
Created attachment 319697 [details]
this is the last of it I was able to capture
This is the last screen I was able to process into readability
*** This bug has been marked as a duplicate of bug 465127 *** |