Bug 22288

Summary: Intall. failure with published bug fix
Product: [Retired] Red Hat Linux Reporter: Need Real Name <mco-redhat_com>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED WONTFIX QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: high    
Version: 7.0   
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: 2001-01-26 23:32:44 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:
Attachments:
Description Flags
Bug report in a text file edited by Anaconda none

Description Need Real Name 2000-12-14 09:10:03 UTC
MY BOX :
Abit KT7 RAID
Athlon Thunderbird 800 MHz
SDRAM : 256 MB PC100
Video : SIS 6326 with 8 MB (RedHat compatible)
HD : 20 GB IDE, master on the primary IDE controller
CD-ROM : IDE-ATAPI, master on the secondary IDE controller
BIOS : boot with CD-ROM/FD/HD
There is a FAT16 of approximately 300 MB on the HD


THE PROBLEMS

10) "crc error"
-------------------
Boot with the RedHat "Installation" CD-ROM
In  the Welcome page, typed : linux x86_serial_nr=1
Few seconds after I become :
   . . .
   Partition check
   hda: hda1
   RAMDISK: Compressed image found at block 0
   crc error VFS:cannot open root device 08:41
   Kernel panic: VFS: Unable to mount root fs on 08:41


20) "signal 4"
------------------
Unabled the UDMA for primary and secondary IDE controller, master and slave disks, and changed PIO mode to "1".
Reboot with the RedHat "Installation" CD-ROM.
In  the Welcome page, typed : linux x86_serial_nr=1 text
   . . .
   running /sbin/loader
   Running anaconda - may take some time to load
   install exited abnormally --received signal 4
   sending terlination signal ...done
   sending kill
   . . .
   you may safely reboot your system

After the reboot : same error as in "10)" above


30) "Dependency searching without ending"
--------------------------------------------------------------
Reboot; changing the PIO mode to "auto"
Reboot with the RedHat "Installation" CD-ROM.
In  the Welcome page, typed : linux x86_serial_nr=1 text
   . . .
   message line was approximately : searching for dependencies

This dependencies search don't end.


40) one more "crc error"
----------------------------------
Reboot; changing the PIO mode to "3"
Reboot with the RedHat "Installation" CD-ROM.
In  the Welcome page, typed : linux x86_serial_nr=1 text
   . . .

Same error as in "10)" above


50) "Exception happened"
-------------------------------------
Reboot; changing the PIO mode to "1"
Reboot with the RedHat "Installation" CD-ROM.
In  the Welcome page, typed : linux x86_serial_nr=1 updates text
  floppy disk with "update-disk-20001009.img" inserted
The installation begin until partioning and automatic partition requested
   . . .
   message line was approximately : Exception happened, you can save the incident on a floppy disk

I saved this incident on a floppy disk and can send it upon request


60) "Exception happened"
-------------------------------------
Reboot; changing the PIO mode to "0"
Reboot with the RedHat "Installation" CD-ROM.
In  the Welcome page, typed : linux x86_serial_nr=1 updates text
  floppy disk with "update-disk-20001009.img" inserted
The installation begin until partioning and automatic partition requested
   . . .
   signal 11



CONCLUSIONS
I can no more ...
This PC had a correct Windows instalaltion.
What to do ? Thank you for help.
Michel  mco

Comment 1 Need Real Name 2000-12-14 09:12:47 UTC
Created attachment 6393 [details]
Bug report in a text file edited by Anaconda

Comment 2 Michael Fulbright 2001-01-03 18:23:10 UTC
This sounds like either a hardware problem with the CDROM drive or perhaps there
are errors on the CD media you are using. I have not seen this problem before.
Did you burn the CD yourself?

Comment 3 Need Real Name 2001-01-06 03:46:53 UTC
This seems to be a hardware incompatibility with the Abit KT7 RAID motherboard.
I have changed it to an Abit KT7 (without the RAID components) motherboard and it works very well.

Comment 4 Michael Fulbright 2001-01-26 23:32:41 UTC
Thank you for the followup. Hopefully the 2.4 kernel will help with some of
these hardware problems.