LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Enterprise Linux Forums > Linux - Enterprise
User Name
Password
Linux - Enterprise This forum is for all items relating to using Linux in the Enterprise.

Notices

Reply
 
Search this Thread
Old 05-10-2008, 12:01 AM   #1
PrimeMogul
LQ Newbie
 
Registered: Apr 2008
Posts: 22

Rep: Reputation: 1
installig driver for RAID controller


I have an older RAID card running RAID 1 on two HD with a hot spare. The vender said they had no driver for a more recent RedHat, so could not upgrade our kernel from 2.6.9-22.ELsmp. We bought a new controller: 3wares' 9550SX. This is not supported by our present Kernel (but is by more recent ones). The plan was to connect the hot spare to the new controller, configure it as a single drive, dd from the old mirror to this single, then put all the drives on the new and rebuildthe mirror. BUT how to get the old kernel to recognze the new controller?

We downloaded the source version of the 9550SX driver from 3ware, compiled it as suggested by article 15095 in www.3ware.com/kb and since "insmod 3w-9xxx.ko" runs without error, was told by the 3ware tech this means we were successful. But the last two steps in that article is

mkinitrd -v -f --with=3w-9xxx --with=scsi_mod ==with=sd_mod \
/boot/initrd-2.6.9-22.ELsmp.img 2.6.9-22.ELsmp
reboot

(I am using my kernel name rather than the one in the article). But curently our directories /boot and /initrd are empty and there is no *.img file that I can find. The 3ware tech said he did not beleive /boot was empty. Is it emty becaue of LinuxSE?

So just how do we include the new driver in the kernel? I really have no clue about hardware. Any clues what I should do?
 
Old 05-10-2008, 05:42 PM   #2
rayfordj
Member
 
Registered: Feb 2008
Location: Texas
Distribution: Fedora, RHEL, CentOS
Posts: 475

Rep: Reputation: 73
the mkinitrd command overwrites your current initrd in /boot.

in your example: /boot/initrd-2.6.9-22.ELsmp.img

to see if the driver is included you can "explode" the initrd and look in its module directory

Code:
mkdir -p /tmp/initrd-tmp
cd /tmp/initrd-tmp
zcat /boot/initrd-2.6.9-22.ELsmp.img | cpio -ivd
find . -type f -name 3w-9xxx.ko -print
or instead of 'find', 'ls /tmp/initrd-tmp/lib/' and look for the module.

if it is there then it is in the initial-ramdisk.

Hope this helps.
 
Old 05-10-2008, 08:26 PM   #3
PrimeMogul
LQ Newbie
 
Registered: Apr 2008
Posts: 22

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by rayfordj View Post
the mkinitrd command overwrites your current initrd in /boot.
Thank-you for the reply, but the problem is that /boot/ is empty. There is nothing to overwrite. Running your code snippet gives:

zcat: /boot/initrd-2.6.9-22.ELsmp.img.gz: No such file or directory

Again

Code:
# find / -name *.img -print
/usr/share/octave/2.1.57/imagelib/default.img
# find / -name *.img.gz -print
ls -al /boot
total 16
drwxr-xr-x   2 root root 4096 Jun 30  2006 .
drwxr-xr-x  23 root root 4096 May  9 14:10 ..
So I ask again.

Quote:
Originally Posted by PrimeMogul View Post
But curently our directories /boot and /initrd are empty and there is no *.img file that I can find. ... Is it empty becaue of LinuxSE? So just how do we include the new driver in the kernel?
 
Old 05-11-2008, 04:09 PM   #4
rayfordj
Member
 
Registered: Feb 2008
Location: Texas
Distribution: Fedora, RHEL, CentOS
Posts: 475

Rep: Reputation: 73
/initrd is empty. it is (or was) used to perform pivot_root from the ramdisk to harddisk.

/boot should not be and a properly labeled filesystem SELinux would not cause an problems with the mkinitrd command.

a default install of RHEL will place /boot on its own partition (especially with RHEL4 and RHEL5 since they use LVM for everythng else). if you look at your /etc/fstab does it have a mount entry for /boot and if you check 'mount' does it show /boot mounted?
 
Old 05-12-2008, 11:42 AM   #5
PrimeMogul
LQ Newbie
 
Registered: Apr 2008
Posts: 22

Original Poster
Rep: Reputation: 1
I discovered /boot was empty as it is not mounted by default.
Thanks--seemed to work as you said. Thanks for helping a newbie.
 
  


Reply

Tags
boot, raid


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Installing driver for Areca RAID Controller surv1v0r Linux - Hardware 2 10-04-2006 02:55 PM
RAID controller driver not available with Fedora?? cmt9000 Fedora 2 01-20-2006 12:05 PM
compile from source a driver for IDE/RAID controller asmar Linux - Software 2 05-16-2005 09:11 AM
Linux driver for HPs Proliant DL380, G4 Raid Controller nordickiwi Linux - Hardware 6 04-13-2005 05:25 AM
Symbios/Lsi scsi controller driver, not a raid acummings Linux - Hardware 1 11-18-2004 11:47 PM


All times are GMT -5. The time now is 12:02 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration