From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Description of problem: Default AACRAID modules aren't stable on a machine with greater than 12 gigs of ram. SCSI bus hangs and filesystems become unmounted or mounted r/o Version-Release number of selected component (if applicable): aacraid 1.1.5 pre 2373 How reproducible: Always Steps to Reproduce: 1. Install Adaptec 2120 or 2200s series raid card 2. Load aacraid module 3. Have more than 12G of ram Actual Results: During high IO load (demonstrated with Bonnie++ or lots of dd commands, after about 20 minutes of heavy IO, the system becomes unstable. SCSI errors show up in dmesg, SCSI times out and filesystems become unmounted or mounted read-only. Sometimes the system will kernel panic. Expected Results: System should continue to be stable. Additional info: Recent Adaptec firmware update with latest drivers fix the problem. This has been tested on 32G of ram systems.
Was the firmware update sufficient, or is both the firmware and driver update required? Please post the firmware and driver version numbers that fixed the problem.
The Driver was required. (1.1.5-2373) The firmware was mostly a performance increase. (RAID5) One caveat though, the Adaptec RPM has a bug in the install.sh script. 749c749 < if [ "${count1} == "1" -a "${count2}" == "2" ] ; then --- > if [ "${count1}" == "1" -a "${count2}" == "2" ] ; then -Mark C
Can you elaborate on the working firmware & driver versions? bios 7348 is on our card, but 7349 is -supposedly- available, but is not on adaptec's site. Links to the 7349 manual addendum are dead links. We cannot get this working with any current linux distro. Dual Opteron 16G Ram Adaptec 2130SLP raid 10 (4x74G U320) Tyan 2882 pro board booting from onboard sata drive, not raid We also cannot appear to add a driver at install, and cannot boot to installed os to update the system via adaptec's rpm.
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.