In RHEL4 it seems that Redhat/LSI Logic/Dell made the decision to include only the megaraid_mbox driver which doesn't include support for many older, yet popular hardware RAID systems, such as the Dell PERC2/DC based systems. A few months ago I posted on the RHEL4
mailing lists my experiences installing RHEL4 on a system with such a card. Since that time I've received quite a few emails asking about the procedure so I've decided to document it here. This is not a perfect step-by-step guide, but should provide enough information to get a system installed. It does require having another RHEL4 system so that you can compile the required kernel modules.
This page has been far more popular than I ever imagined. It get's several hundred hits a month and I get quite a few emails from people having various problems. I try to make changes when they are appropriate, but this was mainly written as a quick summary of what I did, it's not exactly a perfect, step-by-step instruction. There have been quite a large number of success reports, but many people also really struggle. I try to answer people that email me, but some have complained that I don't respond fast enough. I'm sorry, I really do try, but based on work and personal responsibilties I don't always have time to answer right away. Various mailing lists may be more appropriate if you're looking for more immediate help.
Purpose
Procedure to install RHEL4 on systems with unsupported Megaraid controllers such as the Dell PERC2/DC controllers. Actually, this is a pretty generic process that, with minor modifications, should work with any driver which you have source, and a machine on which to compile it.
Requirements
A system with and old style megaraid adapter -- otherwise, what's the point?
An already installed RHEL4 system (or possibly FC3 system or other system with GCC 3.4) with the kernel-devel rpms that match your install media (for example 2.6.9-11 for RHEL4 U1)
Getting Ready
On your working RHEL4 system make sure you have the kernel-devel packages installed that match the kernel on your install media (2.6.9-5.EL for RTM, 2.6.9-11.EL for U1). Create a directory to hold the megaraid source code from the 2.6 kernel. Click here to download the required driver source code included in the Redhat 2.6.9-11.EL kernel source package, which I would think it would be fine for most any kernel.
# mkdir /usr/src/megaraid
# cd /usr/src/megaraid
# tar jxvfp /usr/src/sofware/megaraid2.tar.bz2
Compile the Driver
Now comes time to compile the driver. This is a pretty simple process that should be similar to the following:
# make -C /lib/modules/2.6.9-11.EL/build SUBDIRS=/usr/src/megaraid modules
This should compile the required module. Obviously if you used different directories or are compiling for a different kernel then you will need to modify the above line for this adjustments. The compile will also produce a few warning but it seems safe to ignore these. Once this is complete you should have a megaraid.ko file in the directory. Simply copy the file to a floppy and your ready to start your install.
Install RHEL4
Start the install by booting from the CD and typing "linux noprobe" from the boot prompt. This will keep the installer from probing and attempting to detect your hardware. While still in the text portion of the install you will be prompted to pick your hard drive controller, since the driver is not going to be in the list now it's the time to manually install your driver using the following steps:
1. Press Ctrl-Alt-F2 to switch to a bash prompt
2. Insert the floppy that contains your megaraid.ko file
3. Create directory, mount floppy, install the module:
# mkdir /mount/floppy
# mount /dev/fd0 /mnt/floppy
# insmod /mnt/floppy/megaraid.ko
4. Verify that the module loaded by typing "lsmod" and seeing if megaraid is listed
5. Verify that your RAID array was found by pressing Alt-F4 and seeing the output from the module load
Hopefully at this point everything looks good. At this point complete switch back to the normal install screen by pressing Alt-F7. Since you've manually loaded the driver from the command prompt you can ignore this screen's instructions to pick a driver, simply pick the option to continue the install. Anaconda should load and the GUI portion of the install should begin. Complete the install as normal, with one exception, after all packages are installed and the system prompts you to press finish to reboot Don't do it, proceed to the next section! (If you make a mistake here it is recoverable by booting in rescue mode, but it's more steps).
Complete the Install
Because the megaraid driver was installed manually the installer will likely not build a proper initrd. We can fix this before the reboot right now with the following steps:
1. Press Ctrl-Alt-F2 to switch from the GUI to a bash prompt
2. Copy the megaraid.ko module with the command 'cp /mnt/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-11.EL/kernel/drivers/scsi'
3. Type 'chroot /mnt/sysimage' to set your root to your newly installed system image
4. Type 'vi /etc/modprobe.conf' and make sure that the line with 'alias scsi_hostadapter' says 'alias scsi_hostadapter megaraid'. Save the file.
5. Switch to the /boot directory 'cd /boot'
6. Create new initrd file 'mkinitrd initrd-2.6.9-11.EL.img.megaraid 2.6.9-11.EL'
7. Copy the new initrd over old initrd 'cp initrd-2.6.9-11.EL.img.megaraid initrd-2.6.9-EL.img'
8. Exit chroot environment by typing exit
9. Switch back to the GUI installer with Alt-F7 and press Finish
After these steps your system should be able to boot up a UP kernel. If your installing on an SMP section you'll need to boot up the UP system, compile the source driver again for the SMP kernel, install the module, recreate the initrd for the SMP kernel, and reboot again.
Why?
Why in the world would you go through this effort? The reality is, I have no idea. Fedora Core 4 installs fine on systems with these controllers, and for a 2.6 enterprise distribution, SLES9 works fine. If your totally stuck on Redhat then I'd suggest that you learn to be happy with RHEL3.
That being said, some of us are gluttons for punishment. We have several totally usuable servers that run RHEL4 great except for the lack of support for the Dell PERC2/DC's. After doing this once or twice I can now install RHEL4 on systems with these controllers in only a few minutes, and upgrading a kernel takes only a few minutes extra for each machine, so, once you've practiced a few times it's not that bad.
Besides, it was a personal challenge.
Friday, October 14. 2005 at 00:46 (Reply)
Thus some modifications to the above had to be made to the above instructions and the following link describes them...
http://lists.centos.org/pipermail/centos/2005-August/010021.html
Craig
Friday, January 26. 2007 at 14:08 (Link) (Reply)
I have two dirver on the first SCSI card and RAID 5, LU 0 on the second (PERC 2/DC card. During the install I don't see the SDC drive until I do the insmod a couple of times and then it shows up and I can partition it. I can then load the packages and everythiing looks ok until the actual copy begins.
Happens every time regardless of the variations suggested here. So, what's missing?
The machine is a Dell PE 6440
Friday, January 26. 2007 at 14:35 (Link) (Reply)
Is there some reason that you need the PERC2 to work during the install phase?
Sunday, January 27. 2008 at 19:05 (Link) (Reply)
After following the instructions, I get the following series of error messages:
...
(Clipped to save space)
...
Got any ideas?
BTW, I've been patient with all of this, and its only a matter of time that I figure it out. Any help is greatly appreciated.
Thanks a million...
-rad
Sunday, January 27. 2008 at 20:04 (Reply)
You need to get the module source for the megaraid driver that goes with the RHEL5 kernel from the source rpm packages.
If you understand what's required to get the module source from a kernel RPM then give it a spin, otherwise you can email me directly for more specific steps. I don't have any systems that need this driver anymore, but I'm sure I could talk you through pulling the code and compiling it.
Saturday, January 14. 2006 at 03:06 (Reply)
Tuesday, January 24. 2006 at 12:05 (Link) (Reply)
these instructions were a lifesaver for me! many thanks for posting.
Tuesday, January 24. 2006 at 14:03 (Link) (Reply)
Wednesday, March 8. 2006 at 06:41 (Reply)
Wednesday, March 15. 2006 at 16:10 (Reply)
Monday, April 10. 2006 at 21:53 (Reply)
Wednesday, April 12. 2006 at 13:35 (Reply)
I followed the instructions to a "t" on a 2nd machine in vmplayer.
i execute the following line and I get errors:
make -C /lib/modules/2.6.15-1.2054_FC5/build SUBDIRS=/usr/src/megaraid modules
I receive errors stating
megaraid.c:4501:error 'Scsi_Cmnd' has no member named 'state'
megaraid.c:4520:error 'Scsi_Cmnd' has no member named 'state'
megaraid.c:4520:error 'Scsi_Cmnd' has no member named 'state'
megaraid.c:4554:error 'Scsi_Cmnd' has no member named 'state'
make[1]:** [/usr/src/megaraid/megaraid.o] Error 1
make: ***[module/usr/src/megaraid] Error 2
I checked megaraid.c on the above lines and found:
line 4501 =
scmd->state = 0;
line 4520 =
wait_event(adapter->int_waitq,scmd->state);
line 4554 =
scmd->state = 1; /*thread waiting for its command to complete /
I do not compile often, thus this could be an error on my part although from what I have read, this should be working
more /etc/redhat-release
Fedora Core release 5 (Bordeaux)
gcc --version
gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3)
rpm -qa |grep kernel =
kernel-devel-2.6.15-1.2054_FC5
kernel-2.6.15.1.2054_FC5
Tuesday, April 25. 2006 at 14:04 (Reply)
There were some reported problems where the PCI ID's for some adapters were accidentally removed from both drivers causing a few cards that used to work to quite working even though the driver should be fine. You might try booting with "noprobe" and manually selecting the driver.
Tom
Thursday, May 11. 2006 at 18:08 (Reply)
1. Boot off the FC5 Disc #1
2. Pass noprobe as kernel parameter:
linux noprobe
3. The installer will prompt you to load drivers, when it fails to detect a
hard drive. Here you have the option of loading drivers using the
interactive menu or loading driver from a driver diskette (press F2 to
get to this option). Drivers are listed in alpabetical order. Be sure
to only load the megaraid driver. You'll see megaraid_mbox
driver, make sure you dont load that driver.
4. Proceed with the installer (anaconda).
Hope this help
--
uk
Tuesday, May 30. 2006 at 10:16 (Reply)
Wednesday, September 13. 2006 at 19:40 (Reply)
>megaraid_mbox drivers
>There were some reported problems where the PCI ID's
>for some adapters were accidentally removed from both
>drivers causing a few cards that used to work to quite
>working even though the driver should be fine. You might
>try booting with "noprobe" and manually selecting the
>driver.
The driver does appear in the list of selected drivers in FC5, however, even after noprobe and manually selecting it (and only it), the installation still is unable to detect any hard drive.
Could you elaborate on how this "PCI ID" problem could be diagnosed and solved?
I apologize in advance if this is a dumb question.
Thanks.
Wednesday, September 13. 2006 at 19:51 (Reply)
With a little more information we might be able to help.
Friday, September 15. 2006 at 22:56 (Reply)
The controller is showing (when in BIOS) as CERC ATA/100 RAID controller.
It has three disks attached to it, 32GB each.
It has its own "Control-M" utility where these disks are showing and diagnosing fine.
I am trying to install FC5 on it, but also tried CentOS 4.3, and 4.4, as well as latest Ubuntu server, all of them failing to detect any hard disk.
Thanks.
Friday, September 15. 2006 at 23:23 (Link) (Reply)
Saturday, September 16. 2006 at 20:51 (Reply)
Used all the defaults to create it, which is RAID 5.
I have since got hold of an IDE drive, and installed FC5 on it using all the default modules. Now I am in a state of a working server (still not recognizing the raid disks).
Here are the last four lines of /proc/modules
megaraid_mbox 29777 0 - Live 0xf8831000
megaraid_mm 10989 1 megaraid_mbox, Live 0xf8822000
sd_mod 16577 0 - Live 0xf881c000
scsi_mod 125289 2 megaraid_mbox,sd_mod, Live 0xf883d000
Thanks.
Kirill
Saturday, September 16. 2006 at 22:14 (Link) (Reply)
This is what I was referring to as a "problem" with the PCI ID's on FC5. The installer seems to properly detect the adapter as a megaraid style adapter, but it attempts to load the newer megaraid_mbox driver rather than the classic megaraid driver.
Try removing the megaraid_mbox driver and the manually modprobing the megaraid module in it's place. The command would be something like this:
modprobe -r megaraid_mbox
modprobe megaraid
Let me know how it goes.
Later,
Tom
Sunday, September 17. 2006 at 18:18 (Reply)
After initial screen I did linux noprobe
Then lsmod did not show up any megaraid.
insmod megaraid
did not do anything.
F2 offered me to select modules manually, which I did, and selected only megaraid, not megaraid_mbox.
After that, lsmod was showing
megaraid 36521 0 Live 0xf891b000
scsi_mod 125289 3 megaraid,sr_mod,sd_mod Live 0xf88b1000
I proceeded with install until I got to language selection. After that, lsmod still showed the good megaraid (not megaraid_mbox), however, /dev/ did not have any sd or hd devices other than my IDE drive.
So, it appears that, despite using megaraid, it still fails to see the drives.
Now, back to the megaraid2.tar that is referenced in this page, it does not compile with the gcc that is on FC5, here is what I get instead:
# make -C /lib/modules/2.6.15-1.2054_FC5/build SUBDIRS=/usr/src/megaraid modules
make: Entering directory `/usr/src/kernels/2.6.15-1.2054_FC5-i686'
CC [M] /usr/src/megaraid/megaraid.o
In file included from /usr/src/megaraid/megaraid.c:48:
/usr/src/megaraid/scsi.h: In function âprint_msgâ:
/usr/src/megaraid/scsi.h:97: warning: implicit declaration of function âscsi_print_msgâ
/usr/src/megaraid/megaraid.c: In function âissue_scbâ:
/usr/src/megaraid/megaraid.c:1152: warning: passing argument 2 of âwritelâ makes pointer from integer without a cast
/usr/src/megaraid/megaraid.c: In function âissue_scb_blockâ:
/usr/src/megaraid/megaraid.c:1215: warning: passing argument 2 of âwritelâ makes pointer from integer without a cast
/usr/src/megaraid/megaraid.c:1228: warning: passing argument 2 of âwritelâ makes pointer from integer without a cast
/usr/src/megaraid/megaraid.c:1230: warning: passing argument 1 of âreadlâ makes pointer from integer without a cast
/usr/src/megaraid/megaraid.c: In function âmegaraid_isr_memmappedâ:
/usr/src/megaraid/megaraid.c:1360: warning: passing argument 1 of âreadlâ makes pointer from integer without a cast
/usr/src/megaraid/megaraid.c:1367: warning: passing argument 2 of âwritelâ makes pointer from integer without a cast
/usr/src/megaraid/megaraid.c:1386: warning: passing argument 2 of âwritelâ makes pointer from integer without a cast
/usr/src/megaraid/megaraid.c:1390: warning: passing argument 1 of âreadlâ makes pointer from integer without a cast
/usr/src/megaraid/megaraid.c: In function âmegadev_ioctlâ:
/usr/src/megaraid/megaraid.c:3646: warning: ignoring return value of âcopy_to_userâ, declared with attribute warn_unused_result
/usr/src/megaraid/megaraid.c: In function âmega_internal_commandâ:
/usr/src/megaraid/megaraid.c:4501: error: âScsi_Cmndâ has no member named âstateâ
/usr/src/megaraid/megaraid.c:4520: error: âScsi_Cmndâ has no member named âstateâ
/usr/src/megaraid/megaraid.c:4520: error: âScsi_Cmndâ has no member named âstateâ
/usr/src/megaraid/megaraid.c: In function âmega_internal_doneâ:
/usr/src/megaraid/megaraid.c:4554: error: âScsi_Cmndâ has no member named âstateâ
make[1]: ** [/usr/src/megaraid/megaraid.o] Error 1
make: ** [module/usr/src/megaraid] Error 2
make: Leaving directory `/usr/src/kernels/2.6.15-1.2054_FC5-i686'
# gcc --version
gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Do you know either how to modify this code to make it work, or to get a version of megaraid.c that is compatible with the version of gcc that is on FC5?
Thanks.
Kirill
Tuesday, April 25. 2006 at 12:30 (Reply)
I am hoping someone will be able to help. I am very tired of fighting with this one. I just put together three other servers last week. This one is really getting under my skin.
The hardware I am using is...
intel Xeon EMT64 (dual processor) on an intel MB.
The PROBLEM is the stupid intel SRCS16 Sata RAID controller.
I can install 4.2, 4.3 and others but when I reboot it kernel panics. So, I am at a loss.
Any thoughts would be welcome.
Thank you,
Greg
Friday, April 28. 2006 at 15:11 (Link) (Reply)
VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Any ideas? HELP Please!!!
Thanks!
Doug Johnson
Wednesday, December 31. 2008 at 13:27 (Reply)
Wednesday, April 26. 2006 at 10:59 (Link) (Reply)
Thanks!
Doug Johnson
Tuesday, May 9. 2006 at 17:10 (Reply)
I have it for RHEL4-2.6.9-34
Let me know.
Dave
Friday, May 5. 2006 at 03:00 (Reply)
Many many thanks to Tom Sightler for this solution.
Best wishes
Thursday, August 24. 2006 at 14:10 (Reply)
Friday, May 5. 2006 at 11:51 (Link) (Reply)
Drak
Friday, May 5. 2006 at 13:10 (Link) (Reply)
Please note that this is for "Legacy Megaraid". These are controllers that were manufactured and sold in most cases over 5 years ago. If you have a X86_64 system it seems unlikely you would have a Legacy Megaraid controller.
If you have a Megaraid based controller built in the last 5 years it should be supported by the existing megaraid_mbox driver.
It seems many of the newer cards are not working because the megaraid_mbox driver included in RHEL4 does not recognize their PCI ID's. If that is your case you could compile a newer version of the megaraid_mbox on another x86_64 system and follow similar steps as in the article but since I don't have such a system it would be difficult to give your more specific advice.
Later,
Tom
Monday, May 15. 2006 at 18:21 (Reply)
Intel EtherExpress/100 driver (e100)
I20 Block driver (i2o_block)
Adaptec AHA-2740, 28xx, 29xx, 39xx (aic7xxx)
For the next installation I used the linux noprobe command. Once again when the installation paused because it couldn't find any disks and prompted me to load drivers, the FIRST driver I selected was the LSI legacy driver (megaraid) and then I selected the other drivers. From that point, the installation was smooth.
My assumption is that one of the other drivers ( I suspect the Adaptec driver since both are SCSI class drivers) either controlled or occupied resources that the LSI megaraid driver had to have and it would not load correctly without those resources. By loading it first, it gained controll of the resource(s) needed and the other drivers were not so bound.
Hope this helps someone.
Tuesday, May 16. 2006 at 10:32 (Reply)
thank you very much. I have a HP LC2000r server with the NetRaid 1Si Raid Card in it, and it had me stumped for days now why I couldn't get linux to recognize the card.
I tried to manually install the card and like you, it would freeze on me. The little command before "linux noprobe" helped bigtime. Currently, I am installing Fedora Core 5 on the system. I wonder if this switch works with Suse 10.1 as well, since I tried to install that before and it froze too on the driver install.
Again, thank you. Gotta love google and these forums....
Gerrit
Tuesday, May 16. 2006 at 10:55 (Link) (Reply)
Even from the initial boot you could probably just do:
rmmod i2o_block
modprobe megaraid
If your adapter has the option in the BIOS to run in I2O mode you can probably just set that and it might even work with the i2o_block driver
Later,
Tom
Wednesday, May 17. 2006 at 12:30 (Reply)
You may be right on this, but I checked, and my PERC2 controller had I2O emulation turned on. Maybe this should be turned OFF on the PERC2 so that the installation doesn't see the need to load an I2O driver. I've also done a quick internet search and found numerous questions/complaints about the I2O block driver, which probably means you are right. Haven't had the time to check about the Adaptec driver.
The bottom line for me is "what-ever-works" I guess and, presently, my system is up and running FC5 with no problems. Woo Hoo!
Thanks very much for this site though. Would have taken me much longer to get this problem resolved with it.
clif
Wednesday, May 17. 2006 at 14:13 (Link) (Reply)
I have a Dell 6450 with a PERC 2 sitting in my lab. Maybe I'll see if I can find time to give it a whirl with FC5 and see if I can verify the behavior.
Thanks for your input into this issue, I'm sure it will help others with similar problems.
Later,
Tom
Sunday, June 25. 2006 at 07:19 (Link) (Reply)
Last night I started to build a Fedora Core 5 system on a Dell PowerEdge 2300 with an LAS/AMI/American Megatrends MegaRaid card. I was getting the same lockup problem at the "Loading MegaRaid driver...". After reading your posts I decided to try shutting off the I2O emulation in hopes that it would work and that I could further this thread. On the card BIOS I set the emulation to MASSSTORAGE. Rebooted and voila everything loaded right up. HTH
Keith
Thursday, July 6. 2006 at 14:13 (Link) (Reply)
I have heard people say that you get better throughput to the disks by putting the drives in as individual containers and then putting a software raid on it. So I'm going to use the LTP to get stats on this RAID6 setup that I'm setting up. Then I'm going to rebuild it and have the card control the RAID5 and see what I get. As I type that I realize that I won't be comparing apples to apples, but it will suit my needs.
Friday, July 14. 2006 at 09:51 (Reply)
Wednesday, May 17. 2006 at 00:55 (Reply)
Creating root device
Mounting root filesystem
Kjournald starting commit interval 5 seconds
EXT3-Fs: mounted filesystem with order date mode
Switching to new root
request module: runaway loop modprobe binfmt-0000
request module: runaway loop modprobe binfmt-0000
request module: runaway loop modprobe binfmt-0000
request module: runaway loop modprobe binfmt-0000
System hangs at this point
Wednesday, May 24. 2006 at 12:25 (Reply)
The noprobe would approach would have worked, but you can remove the 'conflicting' drivers with:
rmmod megaraid_mbox
rmmod megaraid_mm
before:
insmod megaraid.ko
which then recognises the SCSI array correctly.
Thursday, May 25. 2006 at 16:52 (Reply)
The conflicting module is:
rmmod megaraid_mbox
The line in the modprobe.conf:
alias scsi_hostadapter megaraid
needs to replace the alias scsi_hostadapter megaraid_mbox as they conflict.
Once the module for the UP (uniprocessor) kernel has been replaced, you then reboot into the UP kernel via your bootloader (grub etc). Once you've done this, you compile your multiprocessor module. in a similar fashion.
As an additional side, as this is an old scsi card, it tends to be associated with a problem of the automatic 'power off' function not working either. ACPI is recognised by linux from 2001. Motherboards older than that...particularly those supproting multi-processors or RAID boards tended to have some ACPI capability.
Adding the text "acpi=force" at the end of the kernel line in grub.conf rectifies the powerdown problem for old boards that support it.
This works for the LP1000r, LP2000r, and a number of the other HP servers.
Thanks for providing this info - Works a treat, and I've learnt a fair bit following and applying your instructions.
Saturday, June 3. 2006 at 18:52 (Link) (Reply)
I have this card too (american megatrends RAID CARD LSI) and have problem: this card in FC4 and FC5 works only under Linux in RAID-0 with 3 scsi disk connected into array. When i set RAID-3 or RAID-5 - this config isn;t working under linux, i cannot format my radi-3 or raid-5 array visibble as /dev/sda
Anybody have look to work this card with RAID-3 or RAID-5 under linux ?
Best ...
Irens
Saturday, June 3. 2006 at 20:08 (Reply)
Could someone send me the compiled megaraid.ko for centos 4.3. I'm trying to install centos, but have no other linux machines running and is getting stuck on the scsi. So i'm in a deadlock right now....
Thanks in advance
Guru
Tuesday, June 6. 2006 at 09:26 (Reply)
http://users.telenet.be/studioo/megaraid-i586.ko
http://users.telenet.be/studioo/megaraid-i686.ko
and this is the step by step howto:
http://lists.centos.org/pipermail/centos/2005-August/010021.html
Hope this is useful for others with the same problem.
Geert Batsleer
Tuesday, June 6. 2006 at 19:57 (Reply)
Thank you for your time and effort for producing this floppy's, however it's not compiled with the same kernel as the current iso's: it's 2.6.9-34.0.1 so the system will not accept the diskdriver...
Also i have seen another strange thing: If i try to load the I586 i get an error (alt-f4) saying that this is not compliant with the I686 version, if i use the I686 version everything hangs... Also I noted that in the bios the Netraid is on pci irq 4 but in the error-screen i see that it tries to connect to another card (IRQ). But evenso i see first that he finds the raid and than 2 errors and nothing anymore...
Anybody has a suggestion?
Guru
Monday, August 28. 2006 at 18:33 (Reply)
Also i have seen another strange thing: If i try to load the I586 i get an error (alt-f4) saying that this is not compliant with the I686 version, if i use the I686 version everything hangs...
Can anyone help me with this?
Monday, June 12. 2006 at 12:41 (Reply)
make: *** /lib/modules/2.6.11-1.1369_FC4/build: No such file or directory. Stop.
If I go into the directory and try to execute build it just seems to be a link to a file that doesn't exist anymore.
Does anyone have a compiled driver for this Kernel or know what the deal with this error message is?
Wednesday, June 14. 2006 at 08:41 (Reply)
Thursday, June 22. 2006 at 04:54 (Reply)
you can find the driver at:
http://users.telenet.be/studioo/megaraid(rhel4u2).ko
It is for the 2.6.9-22 i386 kernel (RHELU2)
PS Had to use '/sbin/mkinitrd initrd...' instead of 'mkinitrd initr...' because it couldn't find mkinitrd without the path.
Wednesday, July 12. 2006 at 20:37 (Link) (Reply)
been expirimenting with megaraid driver for an add-in perc2/DC card connected to a compaq (old MSA) array. Works fine until I shutdown, in fact, it makes my box crash on shutdown or even sometimes when I rmmod the module manually.
This actually makes both of my raid5 logical arrays dirty and as a result at next boot, I can see all the PHYSICAL drives instead of the 2 logical ones. I don't think that should be the case. I wonder if this has somthing to do with the driver not really being suited for the 2.6 kernel.
Has anyone of you megaraiders seen this behavior before ? I have to tape a boot movie soon as I have a compaq Remote Insight Board(the daddy of an ILO) that can do this.
It clearly crashes into the megaraid code.
If only I found this page earlier, I could have said to try I2O/MassStorage setting, save u lot some trouble. I had the same issues as you guys only I played with some of those settings for 5 minutes and accidently discovered that.
In fact, I2O mode doesn't even work , I can't see the array. Also the driver doesn't seem to pick up the correct cache method(e.g Write-Back/Thru), it defaults to WriteThru., even when the logical drives on the array (which is information stored in the nvram on the card imho)
use the other method set in the bios, the driver doesn't pick it up.
Any info on instability with the megaraid driver, especially with an PCI card type Perc2/DC would seriously interest me.
thanks in advance
Wednesday, August 9. 2006 at 10:47 (Reply)
i have a AMI MegaRAID Enterprise 1200 card
i use centOS can not load in
http://users.telenet.be/studioo/megaraid-i686.ko
i already use this
i can not
Create new initrd file 'mkinitrd initrd-2.6.9-11.EL.img.megaraid 2.6.9-11.EL
can help me ...
Thank you
Friday, September 22. 2006 at 01:35 (Link) (Reply)
I made a megaraid driver disk for the CentOS 4.3 installation. I was able to successfully install CentOS 4.3 on a server with a PERC 2/DC.
Please see http://jacksontechsupport.com/resources/CentOS/megaraid/
for download and instructions.
Not really sure where to post this. Please feel free to repost the above web address.
Wednesday, October 18. 2006 at 07:27 (Link) (Reply)
I used this driver disk and finished the install but my box, Dell PE2300/Perc 2, vill not boot. I get the GRUB splash and when it starts to boot from VolGroup it stops and I get kernel panic, and VolGroup is not detected.
Any ideas?
regards
Agust J
Saturday, October 21. 2006 at 08:59 (Link) (Reply)
Thursday, October 26. 2006 at 18:17 (Reply)
Wednesday, November 1. 2006 at 05:29 (Link) (Reply)
I'm not a linux guru, but managed to make this work and I'm so happy about myself.
Sunday, October 29. 2006 at 04:08 (Reply)
This is what happens with Centos 4.x....
I get the spalsh screen asking for the start of the linux install, so I type "linux noprobe" and away I go. The vmlinux ....... starts, , and the next think that happens is a major crash, "kernel panic".
I have tried so many times, whith so many different switches I am thinking of giving up, if it was'nt for the fact I have to biuld it into a voip box I would have given up.
I just can't get past the "vmlinux......." the next thing is a crash.
Any assistance will be a blessing, please I am at a point of suicidal....!
Web-keeper
Jon
Wednesday, November 1. 2006 at 05:35 (Link) (Reply)
then used the "Complete the Install" instsructions at the top to finish before rebooting.
If you do kernel update you have to redo it for new kernel.
Sunday, November 5. 2006 at 02:05 (Reply)
P.S maybe we can get lucky and centos start supporting some of the older hardware on the next release
Sunday, November 5. 2006 at 10:59 (Link) (Reply)
On the other hand distro's like Fedora don't have the same support concerns. Pretty much, as long as it compiles, they'll ship it.
Later,
Tom
Saturday, November 25. 2006 at 11:29 (Reply)
Saturday, November 25. 2006 at 11:48 (Link) (Reply)
If you could be more specific about the issue you are seeing maybe it would help to understand. Saying "LVM is dead" is not very specific.
Saturday, November 25. 2006 at 14:45 (Reply)
Saturday, November 25. 2006 at 15:34 (Link) (Reply)
If you want to try to troubleshoot the GUI you would probably need to start it with strace and figure out what device it is hanging on. I'd be willing to give it a whirl if you think it's worth the effort but it would probably be easier if you email me directly and, if we're lucky enough to solve it we can post the solution here.
Thursday, December 7. 2006 at 06:02 (Reply)
I've followed your instructions word for word, but on re-boot
I get the following error, does anyone have any ideas?
Red Hat nash version 4.1.18 starting
mkrootdev: label /1 not found
mount: error 2 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed: 2
kernel panic - not syncing: Attempted to kill init!
I'm using RHEL 4 AS (2.6.9-5) on a DELL PE6400 (PERC 2/DC)
Thanks
Wednesday, December 13. 2006 at 17:31 (Reply)
Friday, December 15. 2006 at 15:51 (Reply)
Just to add my experience... Have a generic server with a LSI SATA MegaRaid controller. I tried RHAS v3 and FC4 w/ SMP and neither worked. I installed FC6 w/ SMP and it worked w/ no extra effort. But then I just got in RHEL ESv4 on a new server and figured why not try that... SMP fails, but the UP works. Obviously there's somethign newer in FC6 that has been updated/fixed.
Wednesday, February 28. 2007 at 14:26 (Reply)
Save the file (megaraid.ko) someplace in your home directory and then copy it to /lib/modules/`uname -r`/kernel/drivers/scsi/megaraid
Now do the rmmod for megaraid_mobx and megaraid_mm and the insmod for the megaraid.ko file. Edit /etc/modprobe.conf.
cd to /boot and do the mkinitrd, save the original someplace and copy the new initrd to the current one. You make be able to see the RAID drives (/dev/sd*) already. If not, re-boot.
Next use fdisk to create partitions on the newly visible RAID and mkfs to create the file systems. Worked for me ...
Bill
Sunday, March 18. 2007 at 19:00 (Link) (Reply)
I'm doing well until I get to the part where I try to get back to the normal install screen by using Alt-F7.
I get nothing. It just sits there and looks back at me.
Any Ideas???
(I've tried two keybds, and neither work.....)
Sunday, March 18. 2007 at 19:15 (Link) (Reply)
Let me know if that helps.
Later,
Tom
Thursday, July 26. 2007 at 16:18 (Reply)
Tuesday, May 22. 2007 at 01:57 (Reply)
Finally, I grabbed FC2 iso's and used them, and did a minimal install of FC2, the install went through flawlessly, no problems at all.
After FC2 was up, I followed the yum upgrade procedure at http://fedoraproject.org/wiki/YumUpgradeFaq and went from FC2 - FC6 in about 2 hours. After each upgrade, did a reboot into the new kernel, no issues, everything ran smooth.
Once in FC6, I used yum to install all the additional packages that I need (apache, mysql etc) another half hour.
All in all, I got the whole thing up and humming in 4 hours, and now kicking myself for not having done that in the first place, instead of trying fifty different things to make this work.
Anyways, hope that will help someone else.
Friday, June 1. 2007 at 03:41 (Reply)
I'm trying to install RHEL AS 4 Update 2(Original kernel 2.6.9-22.EL) into HP NetServer LXr-8500 that uses NetRAID 2M card. Just like many of u guys whereby the new Megaraid driver doesn't support old hardward. I followed Tom's instructions and sucessfully installed into the server. However I'm facing problem of booting the newly installed RHEL4. The bootup process stops at "Initializing hardware...". The following are the screen output:-
----------------------- Start of screen output -----------------------
Booting 'Red Hat Enterprise Linux AS-up (2.6.9-22.EL)
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.9-22.EL ro root=LABEL=/ rhgb quiet
[Linux-bzImage, setup=0x1400, size=0x1644e8]
initrd /initrd-2.6.9-22.EL.img
[Linux-initrd @ 0x37f7a000, 0x756a3 bytes]
Uncompressing Linux... Ok, booting the kernel.
ACPI: BIOS age (1997) fails cutoff (2001), acpi=force is required to enable ACPI
Red Hat nash version 4.2.1.6 starting
sda: asking for cache data failed
sda: assuming drive cache; write through
INIT: version 2.85 booting
Setting default font (latarcyrheb-sun16): [ OK ]
Welcome to Red Hat Enterprise Linux AS
Press 'I' to enter interactive startup.
Starting udev: [ OK ]
Initializing hardware...
------------------------ End of screen output -----------------------
May I know how do I check which hardware does the OS trying to initial and got stuck ? I'm very sure that I did the installation correctly by following every instructions posted by Tom, coz I managed to install into HP NetServer lp1000r without problem.
Could any of u guys pls advise ? Thank you very much in advance.
Thursday, June 28. 2007 at 10:28 (Reply)
Thursday, August 16. 2007 at 15:29 (Reply)
I'm not sure if there are still folks out there trying to get old PERC cards to work with newer distros, but I wanted to convert a few PowerEdge 4400 systems we have into iSCSI targets so I filled them with drives and tried to load SuSE 10.2. After much searching for solutions I was having no luck getting the RAID volume recognized by the installer. Then I found this mailing list entry:
http://lists.us.dell.com/pipermail/l...ch/030075.html
and
http://support.dell.com/support/edoc...m#Objects_Menu
In a nutshell, changing the adapter's emulation mode to Mass Storage (from I2O) was all that was needed for the megaraid driver to load at install, as well as subsequent reboots.
Note: make sure you update the firmware on the card to ensure stability, and also change the emulation mode after the update - I found out the hard way that a firmware update reverts this setting to the default of I2O!
This may work for other distros and legacy PERC cards as well, but I haven't tested any.
Hope this helps...
Saturday, August 25. 2007 at 15:09 (Reply)
Many thanks, vatmds.
I can confirm that it is also working on a Dell PowerEdge 6400 with Debian Etch.
Saturday, August 25. 2007 at 17:46 (Reply)
Most of the community distros seem to still include the "legacy" megaraid driver and your solution is fine for them.
Later,
Tom
Saturday, September 15. 2007 at 19:24 (Link) (Reply)
http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on-Systems-with-Legacy-Megaraid-Drivers.html
I am not clear from it. I already have another desktop computer where I already installed CentOS 4.3 and running CactiEZ very well but there is no RIAD. Please give me step by step guide or any idea how can I install CentOS 4.3 at HP Netserver LC 2000 U3 server.
Please help me.
N.B#( Link does not work) http://jacksontechsupport.com/resources/CentOS/megaraid/
http://users.telenet.be/studioo/megaraid-i586.ko
http://users.telenet.be/studioo/megaraid-i686.ko
Saturday, September 22. 2007 at 17:23 (Reply)
Asking someone to provide you perfect, step-by-step instructions to do something that is unsupported is somewhat unrealistic. You need to take the initiative and try to follow the instructions above (or other sites which provide similar procedures) and then, if you get stuck, you can ask specific questions on how to resolve your issue.
Later,
Tom
Wednesday, August 22. 2007 at 22:28 (Reply)
However it does not recognize my tape drive.
Not sure what might be the problem.
Tried different FC distros in rescue mode. Up to FC4 tape drive is recognized as SCSI device. Not FC5 or 6.
Any help?
Friday, October 3. 2008 at 18:25 (Reply)
Saturday, October 13. 2007 at 01:39 (Reply)
i managed to get redhat 4.2 EL to work with megaraid.ko.
i have deleted the megaraid_mm and mtop from the modprob.conf files
i have aslo run modprob -r megaraid_mm and mtop
when i run cat /proc/modules
i only see megaraid.ko CORRECT
but when i boot up i got ant insmod error.
insmod: error inserting 'megaraid_mtop.ko': -1 File exists
insmod exit abnormally!
i run cat /proc/modules again
and i can see
megaraid.ko and
megaraid_mm.ko WRONG
seems like there's a startup script trying to load megeraid_mtop.ko back to the OS when starting up.
any ideas how can i remove this error?
thanks
Saturday, October 13. 2007 at 13:55 (Reply)
Instructions for rebuilding your initrd image are included in the article and there are plenty of websites which describe this so I won't rehash it here.
Later,
Tom
Saturday, October 13. 2007 at 22:35 (Reply)
i did Create new initrd file /sbin/mkinitrd initrd 2.6.9_22.EL.img.megaraid 2.6.9_22.EL
cp initrd 2.6.9_22.EL.img.megaraid initrd 2.6.9_22.EL.img
i can boot up and login to the OS without any issues.but still i got the insmod error during bootup.is this error critical?
seems like the OS is working fine even with this error during bootup.
thanks
Tuesday, October 16. 2007 at 15:08 (Reply)
Friday, December 28. 2007 at 04:32 (Reply)
I have no doubt about the guide you've provided. But, I couldn't get it work on my HP Netserver LH 3000 U3 server.
While running with RHEL3, the default SCSI driver is sym53c8xx (and matched with Symbios reported card). But, the XP Pro reported it as megaraid driver.
There is no error of running "insmod /mnt/f/megaraid.ko" (i purposely create folder f in /mnt). The lsmod shows that megaraid modules is loaded but there is none of the SCSI hard disk detected and shown in CTRL+ALT+F4 console.
I've vet through all the comments of readers who are using Netserver and follow their guide too, but to no success.
Note, I've tried to compile two versions of megaraid.ko
1) one physical server with SMP kernel running but compiled with "make -C" to non-SMP kernel,
2) another on virtual machine with non-SMP kernel too.
(I'm installing RHEL4 Update 5 non-SMP kernel in Netserver, and both the platform of compilations are running RHEL4 U5 too).
Please help to compile one if what I've compiled is not suitable.
Many thanks,
Keith
Tuesday, April 29. 2008 at 09:37 (Link) (Reply)
Great guide. I got it to work with the latest version of RHEL 4 (4.6 w/ kernel 2.6.9-67.EL). Something happened and am having to redo the machine from scratch (the install, because I still have the module on a floppy) and it won't work. When I try to load the megaraid module, I don't get any message/error but it doesn't load. I did the noprobe option.
Any ideas? Where can I start to look to figure this out?
Regards,
Scott
Friday, May 9. 2008 at 03:40 (Reply)
Thank you for this very helpful tutorial. Unfortunately i'm not a "linux boy".
Trying to install the latest RHEL 4 (4.6 - kernel 2.6.9-67.EL). I create the disk on a Parallels installation of this release on my Mac. Without relevant problem.
But, but... I'm using a USB Floppy with my Dell 1850 and cannot find it on /dev/fd0. Any idea ?
Best Regards,
Yan
Friday, May 9. 2008 at 07:39 (Reply)
Perhaps you should find a list to post your problem on, the Dell PowerEdge list is pretty good, or if you have a Redhat support contract open a case.
Tuesday, July 15. 2008 at 19:34 (Reply)
Actually, I could load the driver manually during installation and get CENTOS installed. However, upon reboot the system would hang detecting logical volumes on the megaraid. I rebooted and set the PERC emulation to MassStorage and everything now works fine.
Thanks guys,
--Blake
Tuesday, August 26. 2008 at 12:00 (Reply)
Saturday, September 12. 2009 at 07:24 (Reply)
My question at this point is how to best support updates to the system. I would assume that as the kernel is updated, I will need to recompile the megaraid driver. Is this only the case for major kernel updates (e.g. 2.6.x to 2.7.x) or minor updates (e.g. 2.6.18-128 to 2.6.18-128.7.1) as well? What is the recommended path for that? To keep a VM patched in lockstep with the real server and use that VM just for recompilation of the driver?
Any input is greatly appreciated.
Friday, September 18. 2009 at 14:51 (Reply)
Thanks.
Wednesday, December 23. 2009 at 05:22 (Link) (Reply)
make does not work..
does anyone know help?