Bug 82792
Summary: | phoebe2 won't install because of the wrong cdrom iso9660 format | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Tadej Janež <tadej.j> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DUPLICATE | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 9 | ||
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: | 2006-02-21 18:51:25 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
Tadej Janež
2003-01-26 13:53:41 UTC
This sounds like a bad CD. Sometimes a CD can manage to pass the mediacheck and then fail later. I would recommend trying the CDs on a different machine and see if it can install from them as a sanity check. As you suggested I did a sanity check and the CD works ok on the other computers. Additionally I wrote down the exact words about the error on tty4 Here they are: .... <7>ISO 9660 Extentions: RRIP_1991A <4>Unable to identify CD-ROM format <4>VFS: Can't find ext2 filesystem on dev loop(7,0) (the above lines are also the same on the machines that worked with this CD!?) <4>hdc: irq timeout: status=0xd0 {Busy} <4>hdc: irq timeout: error=0xd0LastFailedSense 0xd0 <4>hdc: ATAPI reset complete The last three lines keep repeating and eventually I have to press ctrl-alt-delete. Hope that helps. Tadej Does it work better if you boot with 'linux ide=nodma'? I figured out the problem. It is a really strange one. As I said, the original CD1 didn't work on my testing computer, however, it worked fine on other computers. I was really frustrated and I downloaded the first image again and burned it on another CD (same brand of CDR - BenQ). I burned the new CD with the same burner (Plextor 241040TA). This burner is also used for reading the CDs during installation on my testing machine. And the new CD worked! So my wild guess is that the burner on my testing machine was more sensitive to reading 'scratched' or somehow 'bad' CDs than the normal cd-roms on the other machines that I used as a sanity check. But how did it (the bad CD) pass the MD5SUM check at the begining of the installation and then failed later? I guess this is still a mystery. The md5sum test in the loader is not guaranteed to catch all errors. The installation accesses the CD in a different pattern that the md5sum test (which accesses it sequentially). I've thought about trying to make the test more stringent but have not had time. *** This bug has been marked as a duplicate of 75008 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |