Description of problem:
There seems to be a bug with the anaconda installer for Red Hat Enterprise Linux
(v. 5 for 64-bit x86_64) using the 3WARE SATA RAID CONTROLLER 8006 series and
4GB or more of memory. The anaconda installer formats the hard drives and
installs some of the RPMS but it eventually hangs (between 15 to 20 percent).
The same system was used with 3GB and it installs without a problem. The problem
only occurs on systems with the 3WARE RAID SATA 8006 model which uses the
3w_xxxx kernel driver.
3WARE Raid adapters used for testing:
Raid Card RAM DRIVER STATUS
8006S-2LP 4GB 3w-xxxx FAILED
8006S-2LP 3GB 3w-xxxx WORKED
8006S-2LP 8GB 3w-xxxx FAILED
9500-4LP 3GB 3w-9xxx WORKED
9500-4LP 4GB 3w-9xxx WORKED
9500-4LP 8GB 3w-9xxx WORKED
It seems as though the problem is directly related to the 3w-xxxx driver on
RedHat 5 64BIT Kernel using 4GB. I have tried using LSI RAID controllers and the
3WARE SATA RAID controller 9500 series and did not experience any problems while
I also wanted to point out the fact that the system can be installed with 3GB
but when the 4GB are added I notice some strange problems such as RPM corruption
and unable to untar files
Version-Release number of selected component (if applicable):
* MotherBoard: Model MB-PDSMI+
* Processor: E6300 - CORE 2 DUO 1.86Ghz
* Memory: 4x1GB/ SUPER TALENT 1GB 240 pins PC2-5400 DDR2 667 Computer Memory
* Raid Controller: 3WARE RAID SATA 8006 2PT KIT (3WA80062LP)
* Hard Drives: 2x250GB Raid One (WD2500JS SATA II 250G 8MB/7200)
RedHat Version: Red Hat Enterprise Linux (v. 5 for 64-bit x86_64)
Kernel Version: 2.6.18-53.1.4.el5
Install Method: Kickstart/Anaconda
1. Attempt to install RedHat Version: Red Hat Enterprise Linux (v. 5 for 64-bit
x86_64) WITH 4GB of RAM via kickstart using a 3WARE SATA RAID Controller 8006
series or any 3WARE SATA RAID that uses the 3w-xxxx kernel driver.
2. Installer hangs while installing the RPMS between 15 to 20 percent. You can
still go through the different screens and see the anaconda process using CPU,
but it does not do anything.
3. Attempt using the same system with less than 4GB and the install completes.
Additional information from another user having the same problem:
This issue is still present in RHEL 5.2