Bug 1168845
Summary: | unable to enter into the installed system ,and the screen shrinks | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 21 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, lnie, mkolman, vanmeeuwen+fedora | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2014-12-01 15:29:59 UTC | Type: | Bug | ||||||||||
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
lnie
2014-11-28 08:53:41 UTC
Created attachment 962402 [details]
warning messages
Created attachment 962403 [details]
screen
It seems for me that there is not enough disk space,if so,I think warning messages should pop up during the installation , not after the installation. Please attach the log files from the installed system from /var/log/anaconda as separate text/plain attachments so that we can see what went wrong. Created attachment 963121 [details]
anaconda.log
Created attachment 963123 [details]
/var/log/anaconda
Thanks for the logs! I've checked them all and there does not seem to be any obvious errors during the installation. Could you attach the journal log dump from the installed system, so I can check what goes wrong during the startup ? Something like: journalctl -b > last_boot_journal.txt *** This bug has been marked as a duplicate of bug 1165781 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |