Updated October 04, 2004
Created October 04, 2004
Autogenerated Site Map
Search this Site!:
Red Hat Linux 9 instalaltion via CD-Rom
The ide driver (built statically into the kernel) in Red Hat Linux 9 (RHL9) has a problem working with certain ide chipsets. Basically you can't perform a CD-Rom install. Funny thing is that the regular kernel afterwards seems to work with the CD-Rom ok (if I recall correctly).
So your choices are install in another way (network, hard drive, etc.) or get a boot disk with the kernel fix.
Updated boot disks are available from Compaq (HP):
Basically a slick method was used to modify only the kernel, but yet keep compatibility with all the other modules on the floppy and the read-only CD-Rom media. So this new kernel has the updated ide code but all the versioning is that of the original defective kernel. Life is great!
Of course what do you care about versioning on an installer kernel, just as long as it installs without much hassle, right? No need to update the modules on the CD-Rom if they aren't broke... Have fun using your original install media with this boot disk with updated kernel.
2003 Jun 05 15:17 File bootdisk.rhl9.readme (2,013 bytes)
2003 Jun 05 15:17 File bootdisk.rhl9dl.img (1,474,560 bytes)
2003 Jun 05 15:17 File bootdisk.rhl9us.img (1,474,560 bytes)
Bugzilla web article on this including notes on
the problem. Some items are not related to this
issue. I've used strikethrough on all the
comments I feel confident that are not a part of
this issue.
Bug 87742 - (IDE SERVERWORKS)RedHat 9 device driver for CD drive has boot error on Compaq ProLiant DL360
Bug#: 87742 Product: Red Hat Linux Version: 9 Platform: i686
OS/Version: Linux Status: RESOLVED Severity: normal Priority: normal
Resolution: DUPLICATE Assigned To: arjanv@redhat.com Reported By: blair@orcaware.com QA Contact:
Component: kernel
URL:
Summary: (IDE SERVERWORKS)RedHat 9 device driver for CD drive has boot error on Compaq ProLiant DL360
Keywords:
Status Whiteboard:
Description:
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
Description of problem:
We have a Compaq ProLiant DL360 with 1 Gbyte of RAM. Booting the system
off of the RedHat 8.0 ISO #1 works fine all the way for anaconda to
mount the ISO and install the OS from the CD.
Trying to install RedHat 8.0.94 or RedHat 9 has the system boot of the
CD fine, but when the installer goes to mount the CD, it fails, and
the installer asks for an alternate location of the OS. I was able
to install RedHat using a NFS image.
Now booting the final OS gets this error:
hda: CRN-8245B, ATAPI CD/DVD-ROM drive
hda: set_drive_speed_status: status=0x01 { Error }
hda: set_drive_speed_status: error=0x04
The CD-ROM can't be mounted or anything.
Blar
Version-Release number of selected component (if applicable):
kernel-2.4.20-8
How reproducible:
Always
Steps to Reproduce:
1. Upgrade to RedHat 9 on a system with a CRN-8245B drive.
2. Try to mount a CD-ROM, can't.
3.
Actual Results: Cannot mount any CDs.
Expected Results: Should be able to mount a CD.
Additional info:
hda: CRN-8245B, ATAPI CD/DVD-ROM drive
hda: set_drive_speed_status: status=0x01 { Error }
hda: set_drive_speed_status: error=0x04
------- Additional Comment #1 From Blair Zajac on 2003-04-01 17:35 -------
Created an attachment (id=90818)
dmesg output
------- Additional Comment #2 From Ben Klang on 2003-04-03 13:40 -------
I am encountering a similar problem with an HP DL360G3 (DL-360-G3) box. I was
able to successfully boot and install from CD using RedHat 8, but with the new
RedHat 9 (same server), I am only able to boot. Once booted in to RH9, I get a
dialog asking me for the language, keyboard, and install media. When selecting
CDROM ( the same CDROM I just booted from) it fails. It gives me messages about
not being able to mount CD-ROM, invalid media, and bad return codes when
probing UnitReady sense codes. I have verified the MD5 checksum in two different
machines. The RedHat 8 disc and the RedHat 9 disc are both burned to a CDR
from the same package. Both MD5 sums work correctly in both checksumming
machines.
------- Additional Comment #3 From Shane Witbeck on 2003-04-06 21:01 -------
I am having a similar issue with a Dell PowerEdge 1650. I have noticed the same
errors while trying to install rh 9. I have installed rh 9 on another desktop
machine using the same ISO's on the same CD's and performed the mediacheck
option prior. I am able to boot from rh 9 disk 1 and after I choose CD-ROM for
the location of the install files it does not go any further. The CD-ROM in
question is a TEAC CD-224E.
------- Additional Comment #4 From Arjan van de Ven on 2003-04-07 04:53 -------
PowerEdge 1650 is a different and known issue and greatly depends on the bios
version (A07 seems to work ok, later ones do not)
------- Additional Comment #5 From redhat admin on 2003-04-18 06:42 -------
I have a Proliant 1600 and I can boot but the install hangs *after* the media
check screen. I tried in both gui and text. I even tried booting with noprobe to
see if that helped. I have only tried RH9.0. Will try 8.0 tonight.
------- Additional Comment #6 From Need Real Name on 2003-05-05 14:17 -------
I have a Proliant ML370 G2 with a similar problem - runs 8.0 fine but fails
on the 9.0 cd 1 image. I know the image is good as it installs correctly on
another machine. From Alt F4 while testing the cd-image(which fails) I
get :
hda : command error : status=0x51 {DriveReady Seekcomplete Error}
hda : command error: error=0x54
end_request : I/O error, dev 03:00(hda) sector 1306624.
------- Additional Comment #7 From Jose DeLeon on 2003-05-11 23:59 -------
Same problem.
------- Additional Comment #8 From Michael Fulbright on 2003-05-13 12:42 -------
This error indicates the CD is bad. The mediacheck will sometimes pass on
marginal CDs that fail during installation.
*** This bug has been marked as a duplicate of 75008 ***
------- Additional Comment #9 From Blair Zajac on 2003-05-13 13:12 -------
I wasn't too clear about this, but, this is not a bad CD-ROM.
After performing a clean install of RedHat 9 from NFS mounted CD-ROM images,
everytime I boot the system normally from the hard disk I see this message in
dmesg:
hda: CRN-8245B, ATAPI CD/DVD-ROM drive
hda: set_drive_speed_status: status=0x01 { Error }
hda: set_drive_speed_status: error=0x04
So it's not a bad CD-ROM, rather a device driver.
Best,
Blair
------- Additional Comment #10 From Clark Tompsett on 2003-05-23 11:45 -------
This bug also affects Compaq Presario 900 laptops.
------- Additional Comment #11 From Michael Fulbright on 2003-05-27 14:49 -------
*** Bug 90227 has been marked as a duplicate of this bug. ***
------- Additional Comment #12 From Need Real Name on 2003-06-02 07:10 -------
Same here. RedHat 9 install fails to recognize cd#1 as valid installation
media. HW Compaq DL380... Seems pretty much like a driver bug to me... Any
workarounds? I could easily install over network, but I wan't to try out LVM,
and it's not possible to create logical volumes using text-mode installer (or
is it?)...
------- Additional Comment #13 From E Blaufuss on 2003-06-06 13:40 -------
We've got two Compaq ML 350s, both had the same problem with CD installs,
the media has been checked and used to sucessfully install on other machine.
An HTTP install worked, but CD remains unusable...
Is there any resolution or workaround to this problem?
------- Additional Comment #14 From zak on 2003-06-09 01:22 -------
*** Bug 92162 has been marked as a duplicate of this bug. ***
------- Additional Comment #15 From zak on 2003-06-09 01:27 -------
Me too - Compaq ML 350.
Also, although the issue clearly stems from a problem in the installer kernel
somewhere I think this bug is more appropriate in the installer section instead
of kernel. Is it possible to assign to installation, installer, anaconda and kernel>
This has to be a major boo-boo and I'm surprised that this bugzilla entry as not
had significantly more activity, especially from the RedHat folks.
Ciao
------- Additional Comment #16 From Arjan van de Ven on 2003-06-09 03:08 -------
tell me how I can replace the kernels on your cds and it might become
interesting to fix it. The current erratum kernel has the bug fixed but that
doesn't mean the kernel on the cd is fixed as well :(
------- Additional Comment #17 From Alan Cox on 2003-06-09 09:55 -------
Presario 900 is unrelated (search bugzilla for the keyword (RADEON IGP) for more
info on that
Dell 1650 with newer BIOS is fixed in main tree now and was a kernel issue
Compaq DL360 seems more complex but use "ide=nodma".
------- Additional Comment #18 From Alan Cox on 2003-06-09 10:21 -------
*** This bug has been marked as a duplicate of 71499 ***
------- Additional Comment #19 From zak on 2003-06-10 07:17 -------
Arjan,
Obviously you are not going to be able to fix the kernel on my cds or on the
thousands out there. However a boot image which would allow you to boot off the
floppy and then still use the cds for a source of RPMs to install surely is not
that far-fetched an idea?
Further, it seems that I was mistaken in marking 92162 as a dup of this bug. I
fixed that now.
------- Additional Comment #20 From Arjan van de Ven on 2003-06-10 07:22 -------
the problem is that only a small part of the kernel will go on such floppy, for
the rest kernel modules from the cd are used.... which aren't updatable
------- Additional Comment #21 From David Brown on 2003-06-23 00:41 -------
Firstly, can someone please reopen this bug. It has been marked Resolved -
Duplicate but i've searched through all the duplicates in this bug and none of
them fix the problem (most relate to bad installation media - which has been
ruled out in the case of this bug).
How not updateable are we talking here? Ie not gonna be fixed until new CDs are
done? or can it be worked around by providing updated bootdisk.img and other
files for users to merge into their existing disks and then burn?
I'm going to try stuffing around with the CD boot system and see if i can get
it working as we REALLY need to have this in our environment. Any help
appreciated - i'll post my findings (if any constructive come out of it).
------- Additional Comment #22 From Mark Whitehouse on 2003-06-23 14:35 -------
We have a similar issue with a Compaq DL380. We have made a custom 9.0 boot CD
with the latest kernel 2.4.20-18.9 but are still unable to install 9.0 from this
CD. So, from my perspective the issue is: how do I create a custom 9.0 CD which
will work with the Compaq DL380?
------- Additional Comment #23 From Paascal Boulch on 2004-03-03 05:23 -------
Here is a workaround regarding this problem by creating a boot floppy
http://www.cpqlinux.com/wget-ftp-index.html
Tested on Compaq ML370 with Redhat 9
Readme from compaq regarding the new boot disk. Also describes the problem well:
TITLE: Red Hat Linux 9 Professional CD install fails on certain ProLiant servers
==================================================================================
DESCRIPTION:
A CD-ROM based install of Red Hat Linux 9 Professional fails on certain ProLiant
servers. The install fails to find the CD-ROM drive and prompts the user to select
the type of install to perform. If CD-ROM is selected the install will again fail
to find the drive and the user will end up in an endless loop until another choice
is made.
SCOPE:
Red Hat Linux 9 Professional
DL320
ML330G2
ML350G3
DL360G3
ML370G3
DL380G3
DL530G3
ML570G2
DL580G2
DL760
RESOLUTION:
An updated boot floppy has been created and can be downloaded from: ftp.compaq.com
The floppy is created by using either dd or rawrite.
dd can be used as follows:
dd if=bootdisk.img of=/dev/fd0 bs=1440k
rawrite can be used as follows:
rawrite
Specify the name of the image file when prompted
Specify the "A:" drive when prompted for destination drive.
Once you have created the updated boot floppy, boot the above mentioned ProLiant server
on the floppy. You may insert the CD-ROM at any time after the server begins booting
on the updated floppy. If prompted, select "install from CD-ROM" and insert the Red Hat
Linux 9 Professional CD when prompted.
Installation should continue as normal.
Note: There are two versions of this updated boot disk.
* bootdisk.rhl9us.img is only for retail boxed Red Hat Linux 9 purchased in the US where
the md5sum for CD #1 is: "cd8872f2e2e3a42f548ed1bf947709f0".
* bootdisk.rhl9dl.img is for the supported/retail boxed Red Hat Linux 9 purchased outside
the US where the md5sum for CD #1 is: "50f414a2135d093a02704b4b513f92ba" or the unsupported
version downloaded from sites such as linuxiso.org where the md5sum for CD #1 is:
"400c7fb292c73b793fb722532abd09ad".
The md5sum of the updated floppies are as follows:
c2d235cf7c05030e8ae7d849421d4f01 bootdisk.rhl9dl.img
51fd0ef3d8d6c654d17b61e6f7b12fa4 bootdisk.rhl9us.img
Search this Site!:
Homepage: http://www.cpqlinux.com
Site Map: http://www.cpqlinux.com/sitemap.html