Bug 28946
Summary: | installation dies in Anaconda | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <mathog> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | http://seqaxp.bio.caltech.edu/pub/PICKUP/anacdump.txt | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-02-27 23:37:59 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
Need Real Name
2001-02-22 22:51:01 UTC
What is the error you get when the new install failed? It said that there was an error in anaconda and then put up the message available at: http://seqaxp.bio.caltech.edu/pub/PICKUP/anacdump.txt that's also what it did on an upgrade attempt. It would have been nice if instead of dropping dead it provided some way to locate the files it could not find. I don't know if this is at all related, but somewhere during the upgrade/installation attempts a disk failed (/dev/sdb1). It may have been dead before I even started - it was a disk I wasn't currently using. It had been mounted for about 6 months, but no activity on it. There's nothing on this disk at all and no particular reason that the installation should even touch it. After I realized that I used an emergency boot disk to modify /etc/fstab on the existing root file system (/dev/sda1) to comment out the line about /dev/sdb1, and it didn't help - same error. /dev/sdb1 isn't totally dead as fsck runs on it up to a point, but then gives messages which suggest bad blocks. This error indicated that the CD you were installing from is missing essential files. Could you look on VC3 and VC4 (cntl-alt-f3 and -f4) and see if you are getting read errors reported by the kernel. Most likely the CD is bad or the CD drive in the system you are installing cannot read this media type. Closing due to inactivity - please reopen if you have anything to add to the bug report. |