Bug 596981
Summary: | one minute delay from "Found installation media" to "running anaconda" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | anaconda-maint-list, jonathan, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-31 15:42:24 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: |
Description
John Reiser
2010-05-27 20:52:16 UTC
What's /tmp/syslog say? Are you getting a lot of read errors? /tmp/syslog is unavailable because the system hangs/crashes at start of X11: bug 596985. VT2 has no shell: too early. "dd if=/dev/sr0 bs=32k count=10000 of=/dev/null" says 330MB in 106 seconds (3.5 MB/s) with no errors in /var/log/messages, when run on an already-installed F14 rawhide on the same box. Media Check also passes when run during another boot on the same box. Drive is Optiarc AD-7240S about 8 months old, lightly used, and is the drive that burned the DVD in the first place, earlier today. Well, you could always try starting up a text install, seeing if you get the same long delay, and then grabbing the information if so. Or you could try the same thing with a serial console install, or a VNC install. anaconda supports syslog=. There's plenty of ways to get information. Running a text install (append " text" to the end of the kernel boot command line), then there is no file whose pathname matches /tmp/*syslog*. Perhaps you mean /var/log/messages? That is the filename which appears in "ls -l /proc/$(< /var/run/syslogd.pid)/fd". Anyway there aren't any I/O errors listed in /var/log/messages. What is the complete syntax that is implied by "anaconda supports syslog="? What other pieces must be available (such as a path through a firewall on another machine?), and how is that setup? > What is the complete syntax that is implied by "anaconda supports syslog="? > What other pieces must be available (such as a path through a firewall on > another machine?), and how is that setup? http://fedoraproject.org/wiki/Anaconda/Logging This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping (In reply to comment #5) > http://fedoraproject.org/wiki/Anaconda/Logging Some of the info on that page does not work. In particular, there is no file 'analog' anywhere in anaconda-13.42-1, which is the current shipping release. Thus it is problematic to construct the syslog configuration. Found a system with anaconda-14.12 that could run the 'analog' script to generate the syslogd configuration, and transfered the configuration file to the logging machine, and started the logger, and appended " syslog=<ip4>:<port>" to the kernel boot command line. There are no suspicious messages in syslog, but the one-minute delay no longer appears, either. |