Bug 58879
Summary: | Redhat Installation Problem | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | babe <sagar555> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | andreas.loesch, jra, sagar555, srevivo |
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: | 2002-04-11 09:14:33 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
babe
2002-01-26 13:35:53 UTC
These messages seem to imply that you have a bad cd. <4>hdc: command error: status=0x51 { DriveReady SeekComplete Error } <4>hdc: command error: error=0x55 If this is a CD you burned yourself, please check the md5sums against those published on our FTP site. Otherwise, please contact the vendor from whom you received these CDs. I have the same problems, but I tried different ISOs (from different Mirrors) every time the MD5 checksum was ok and also the check of the burned images passed the 'linux mediacheck'! The anacdump.txt looks similar, if you want me to post it, don't hesitate to ask. <aol> Mee too. </aol> I don't have the floppy with the dump handy (and that dump dialog shouldn't automatically die afterwards, neither), but that traceback is with 5% of mine. Toshiba Portege 3010, APA-1460 SCSI, Yamaha CDW_6416 (which otherwise works fine, and the entire combo did the 7.1 install *flawlessly*), and the disks pass mediacheck. It just can't get disk 2 unmounted to move to disk 3. 4 tries. 17 hours. Little sleep. My production laptop. Very Bad Bug to have. Happy to help you fix it. AND CAN WE MOVE THE BOOTLOADER SETUP TO TEH FRONT OF THE INSTALL? Having an unbootable machine because a potentially survivable aborted update died before it was installed *when all the parameters were captured up front* is Also Very Bad. Write the bootloader *just as soon as you can*. Very Grumpy. Please reopen -- yes, it's a bug. |