I want to install CentOS 5.1 with hardware RAID on an HP DL140 G3 server that I have here for testing. It prompts me for a storage controller. According to this readme page for the latest driver at ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1463703615/v44436/mpt linux-4.00.13.01-2.rhel5.i686.dd.gz.txt CentOS 5 should already contain a "default driver version contained in the Red Hat Enterprise Linux 5 installation CD" I would rather like to use that than go the complicated route of providing the latest HP driver. That "HP Internal Port SAS/SATA HBA with RAID" actually is a RAID controller from LSILogic and I tried to load all four LSILogic drivers provided on the driver list, but none is accepted. Does somebody have experience with this server/RAID controller and can tell me if I can go somehow with the drivers provided by CentOS 5.1 or do I need to go with the drivers provided by HP?
Kai
On Mon, 2008-04-14 at 23:33 +0200, Kai Schaetzl wrote:
I want to install CentOS 5.1 with hardware RAID on an HP DL140 G3 server that I have here for testing. It prompts me for a storage controller.
Check your BIOS Settings for the controller. May be that it needs to set to "Mass Storage" if available in the HP Bios. I am not a die hard HP person so check the settings available. I know for a fact this is a problem with other manufactures.
Maybe there is a HP Guy or Gal in here some where that can elaborate some more on this for you.....
According to this readme page for the latest driver at ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1463703615/v44436/mpt linux-4.00.13.01-2.rhel5.i686.dd.gz.txt CentOS 5 should already contain a "default driver version contained in the Red Hat Enterprise Linux 5 installation CD"
Then again the MPT Drivers for that controller may have been dropped for that controller. I do know several have been "End of Lifed" I know this to be true for other high end server manufactures. Support for them ended in RHEL 4. So that would = CentOS 4 as well.
I would rather like to use that than go the complicated route of providing the latest HP driver. That "HP Internal Port SAS/SATA HBA with RAID" actually is a RAID controller from LSILogic and I tried to load all four LSILogic drivers provided on the driver list, but none is accepted.
See bios explaination above.
Does somebody have experience with this server/RAID controller and can tell me if I can go somehow with the drivers provided by CentOS 5.1 or do I need to go with the drivers provided by HP?
Kai
John wrote on Mon, 14 Apr 2008 23:26:59 -0400:
Check your BIOS Settings for the controller. May be that it needs to set to "Mass Storage" if available in the HP Bios.
There is nothing I can set regarding this. There is also a built-in HP SATA fakeRAID controller for the mainboard built-in SATA ports. I switched that off. I also switched SATA ports off now. There's nothing else in the BIOS I could try I think. There's also nothing in the controller's BIOS that seems to be fitting this description, the only hardware-related thing I can change there, is a hook interrupt or what they call it. I didn't dare to change that yet.
According to this readme page for the latest driver at ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1463703615/v44436/mpt linux-4.00.13.01-2.rhel5.i686.dd.gz.txt CentOS 5 should already contain a "default driver version contained in the Red Hat Enterprise Linux 5 installation CD"
Then again the MPT Drivers for that controller may have been dropped for that controller.
Well, I was going by their description which says that RHEL 5 comes with these drivers. Of course, that could still be wrong ...
I do know several have been "End of Lifed" I know this
to be true for other high end server manufactures. Support for them ended in RHEL 4. So that would = CentOS 4 as well.
It seems that RHEL 4 did not have the drivers on board. Their software configuration guide mentions that you need to install a driver (if I recall right). Unfortunately, the guide wasn't updated for RHEL, although they say they support RHEL 5 and 5.1 on this machine.
Maybe I actually hit a different problem than I think. This is the first time that I need to install an extra driver for installation or use an external HBA SAS/SATA adapter. Some more information:
During inital anaconda setup I can see that various mpt drivers get installed. It's too fast output at this time to read well thru ALT F3/F4, but it looks like the controller and SATA drives are found and handled under /dev/sda with no error. The drivers loaded are mtpbase, mptscsih, mptsas and scsi_transport_sas. After choosing eth0 as install source and retrieving the kickstart file setup asks me "unable to find any devices of the type needed for this installation type. Would you like to manually select your driver or sue a driver disk". The "manual" selection gives me a list of storage drivers. I then tried to use the driver given by HP which is a dd file and install it from a USB stick. I can select /dev/sdb1 and it shows the .dd files as the only one available. When I choose this it tells me "no devices of the appropriate type were found on the driver disk". At the same time ALT+F4 shows "unable to identify CD-ROM format" and F3 a line "modules to insert" that is empty. The dd file is a 1.440 floppy image it seems. Am I doing something wrong here?
In case that matters: of course, I already set up the two drives in the LSI SAS utility for a RAID1 configuration and it shows them now as "LSILogicLogical Volume 3000" which seems to be quite ok to me.
I'd appreciate any insight you might have. I'm going to try out their forums now and see how good they are.
Kai
there is a bug on the bugtracker concerning "lsilogic" http://bugs.centos.org/view.php?id=2531 but I'm not sure if it could relate to my issue or not. Searching for "lsilogic.ko" with Google reveals only this single article, so that information might just be fake.
Kai
On Tue, 2008-04-15 at 14:46 +0200, Kai Schaetzl wrote:
John wrote on Mon, 14 Apr 2008 23:26:59 -0400:
Check your BIOS Settings for the controller. May be that it needs to set to "Mass Storage" if available in the HP Bios.
There is nothing I can set regarding this. There is also a built-in HP SATA fakeRAID controller for the mainboard built-in SATA ports. I switched that off. I also switched SATA ports off now. There's nothing else in the BIOS I could try I think. There's also nothing in the controller's BIOS that seems to be fitting this description, the only hardware-related thing I can change there, is a hook interrupt or what they call it. I didn't dare to change that yet.
According to this readme page for the latest driver at ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1463703615/v44436/mpt linux-4.00.13.01-2.rhel5.i686.dd.gz.txt
Well only other choice is to download the driver from HP and make it. Put it on a floppy start the install and type linuxdd @ at the install prompt. Or B...Look into using and older version of centos
CentOS 5 should already contain a "default driver version contained in the Red Hat Enterprise Linux 5 installation CD"
Then again the MPT Drivers for that controller may have been dropped for that controller.
Well, I was going by their description which says that RHEL 5 comes with these drivers. Of course, that could still be wrong ...
I do know several have been "End of Lifed" I know this
to be true for other high end server manufactures. Support for them ended in RHEL 4. So that would = CentOS 4 as well.
It seems that RHEL 4 did not have the drivers on board. Their software configuration guide mentions that you need to install a driver (if I recall right). Unfortunately, the guide wasn't updated for RHEL, although they say they support RHEL 5 and 5.1 on this machine.
Maybe I actually hit a different problem than I think. This is the first time that I need to install an extra driver for installation or use an external HBA SAS/SATA adapter. Some more information:
During inital anaconda setup I can see that various mpt drivers get installed. It's too fast output at this time to read well thru ALT F3/F4, but it looks like the controller and SATA drives are found and handled under /dev/sda with no error. The drivers loaded are mtpbase, mptscsih, mptsas and scsi_transport_sas. After choosing eth0 as install source and retrieving the kickstart file setup asks me "unable to find any devices of the type needed for this installation type. Would you like to manually select your driver or sue a driver disk". The "manual" selection gives me a list of storage drivers. I then tried to use the driver given by HP which is a dd file and install it from a USB stick. I can select /dev/sdb1 and it shows the .dd files as the only one available. When I choose this it tells me "no devices of the appropriate type were found on the driver disk". At the same time ALT+F4 shows "unable to identify CD-ROM format" and F3 a line "modules to insert" that is empty. The dd file is a 1.440 floppy image it seems. Am I doing something wrong here?
In case that matters: of course, I already set up the two drives in the LSI SAS utility for a RAID1 configuration and it shows them now as "LSILogicLogical Volume 3000" which seems to be quite ok to me.
I'd appreciate any insight you might have. I'm going to try out their forums now and see how good they are.
Kai
on 4-15-2008 5:46 AM Kai Schaetzl spake the following:
John wrote on Mon, 14 Apr 2008 23:26:59 -0400:
Check your BIOS Settings for the controller. May be that it needs to set to "Mass Storage" if available in the HP Bios.
There is nothing I can set regarding this. There is also a built-in HP SATA fakeRAID controller for the mainboard built-in SATA ports. I switched that off. I also switched SATA ports off now. There's nothing else in the BIOS I could try I think. There's also nothing in the controller's BIOS that seems to be fitting this description, the only hardware-related thing I can change there, is a hook interrupt or what they call it. I didn't dare to change that yet.
According to this readme page for the latest driver at ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1463703615/v44436/mpt linux-4.00.13.01-2.rhel5.i686.dd.gz.txt CentOS 5 should already contain a "default driver version contained in the Red Hat Enterprise Linux 5 installation CD"
Then again the MPT Drivers for that controller may have been dropped for that controller.
Well, I was going by their description which says that RHEL 5 comes with these drivers. Of course, that could still be wrong ...
I do know several have been "End of Lifed" I know this
to be true for other high end server manufactures. Support for them ended in RHEL 4. So that would = CentOS 4 as well.
It seems that RHEL 4 did not have the drivers on board. Their software configuration guide mentions that you need to install a driver (if I recall right). Unfortunately, the guide wasn't updated for RHEL, although they say they support RHEL 5 and 5.1 on this machine.
Maybe I actually hit a different problem than I think. This is the first time that I need to install an extra driver for installation or use an external HBA SAS/SATA adapter. Some more information:
During inital anaconda setup I can see that various mpt drivers get installed. It's too fast output at this time to read well thru ALT F3/F4, but it looks like the controller and SATA drives are found and handled under /dev/sda with no error. The drivers loaded are mtpbase, mptscsih, mptsas and scsi_transport_sas. After choosing eth0 as install source and retrieving the kickstart file setup asks me "unable to find any devices of the type needed for this installation type. Would you like to manually select your driver or sue a driver disk". The "manual" selection gives me a list of storage drivers. I then tried to use the driver given by HP which is a dd file and install it from a USB stick. I can select /dev/sdb1 and it shows the .dd files as the only one available. When I choose this it tells me "no devices of the appropriate type were found on the driver disk". At the same time ALT+F4 shows "unable to identify CD-ROM format" and F3 a line "modules to insert" that is empty. The dd file is a 1.440 floppy image it seems. Am I doing something wrong here?
In case that matters: of course, I already set up the two drives in the LSI SAS utility for a RAID1 configuration and it shows them now as "LSILogicLogical Volume 3000" which seems to be quite ok to me.
I'd appreciate any insight you might have. I'm going to try out their forums now and see how good they are.
Kai
Did you use the HP utilities to set up an array on the controller before you tried to install?
AFAIR you can only do that from the setup disk that came with your server, or download a new copy if you don't have it.
Scott Silva wrote on Tue, 15 Apr 2008 09:39:18 -0700:
Did you use the HP utilities to set up an array on the controller before you tried to install?
You press F8 and get in the controller utility. As I said I have set up a RAID1 that is named "LSILOGICLogical Volume 3000" just fine.
Kai
On Tue, 2008-04-15 at 14:46 +0200, Kai Schaetzl wrote:
John wrote on Mon, 14 Apr 2008 23:26:59 -0400:
Check your BIOS Settings for the controller. May be that it needs to set to "Mass Storage" if available in the HP Bios.
There is nothing I can set regarding this. There is also a built-in HP SATA fakeRAID controller for the mainboard built-in SATA ports. I switched that off. I also switched SATA ports off now. There's nothing else in the BIOS I could try I think. There's also nothing in the controller's BIOS that seems to be fitting this description, the only hardware-related thing I can change there, is a hook interrupt or what they call it. I didn't dare to change that yet.
According to this readme page for the latest driver at ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1463703615/v44436/mpt linux-4.00.13.01-2.rhel5.i686.dd.gz.txt CentOS 5 should already contain a "default driver version contained in the Red Hat Enterprise Linux 5 installation CD"
Then again the MPT Drivers for that controller may have been dropped for that controller.
Well, I was going by their description which says that RHEL 5 comes with these drivers. Of course, that could still be wrong ...
I do know several have been "End of Lifed" I know this
to be true for other high end server manufactures. Support for them ended in RHEL 4. So that would = CentOS 4 as well.
It seems that RHEL 4 did not have the drivers on board. Their software configuration guide mentions that you need to install a driver (if I recall right). Unfortunately, the guide wasn't updated for RHEL, although they say they support RHEL 5 and 5.1 on this machine.
Maybe I actually hit a different problem than I think. This is the first time that I need to install an extra driver for installation or use an external HBA SAS/SATA adapter. Some more information:
During inital anaconda setup I can see that various mpt drivers get installed. It's too fast output at this time to read well thru ALT F3/F4, but it looks like the controller and SATA drives are found and handled under /dev/sda with no error. The drivers loaded are mtpbase, mptscsih, mptsas and scsi_transport_sas. After choosing eth0 as install source and retrieving the kickstart file setup asks me "unable to find any devices of the type needed for this installation type. Would you like to manually select your driver or sue a driver disk". The "manual" selection gives me a list of storage drivers. I then tried to use the driver given by HP which is a dd file and install it from a USB stick. I can select /dev/sdb1 and it shows the .dd files as the only one available. When I choose this it tells me "no devices of the appropriate type were found on the driver disk". At the same time ALT+F4 shows "unable to identify CD-ROM format" and F3 a line "modules to insert" that is empty. The dd file is a 1.440 floppy image it seems. Am I doing something wrong here?
In case that matters: of course, I already set up the two drives in the LSI SAS utility for a RAID1 configuration and it shows them now as "LSILogicLogical Volume 3000" which seems to be quite ok to me.
I'd appreciate any insight you might have. I'm going to try out their forums now and see how good they are.
-----------------------------------------------------------------------------------------------------
****See here there is a reason I said type{linuxdd} and USE A FLOPPY. A usb stick is not going to do the job. I don't think you read the README! ****
CREATING A DRIVER DISKETTE
MAKING A DISKETTE UNDER A LINUX-LIKE OS:
1) Save the "mptlinux-4.00.13.01-2.rhel5.i686.dd.gz" file into a temporary directory. Use GUNZIP to extract "mptlinux-4.00.13.01-2.rhel5.i686.dd" from this file into the same directory
2) To make a diskette under Linux (or any other Linux-like operating system), you must have permission to write to the device representing a 3.5-inch diskette drive (known as /dev/fd0 under Linux)
3) First, label a blank, formatted diskette appropriately (ProLiant Red Hat Enterprise Linux 5 Driver Diskette). Insert the diskette into the floppy drive, but DO NOT issue the mount command:
# dd if=mptlinux-4.00.13.01-2.rhel5.i686.dd of=/dev/fd0 bs=1440k
4) This command creates a diskette containing the image of the input file (if=mptlinux-4.00.13.01-2.rhel5.i686.dd) to an output file (of=/dev/fd0) using the diskette size of 1440k (1.44MB). To make another diskette label that diskette, and run "dd" again, specifying the correct input file.
INSTALLATION
To install Linux using this "ProLiant Red Hat Enterprise Linux 5" Driver Diskette, boot your Linux machine with your Red Hat Enterprise Linux 5 CD1 in your CD-ROM Drive.
A menu will be displayed, prompting for your input. Type the following line of code to inform the operating system of the diskette:
# linux dd
Red Hat Enterprise Linux 5 will prompt for the ProLiant Red Hat Enterprise Linux 5 Driver Diskette during the installation procedure.
Kai
John wrote:
****See here there is a reason I said type{linuxdd} and USE A FLOPPY. A usb stick is not going to do the job. I don't think you read the README!
usb keys work fine as driver disks on centos-5, the .dd image can be loop mounted and the contents copied out onto the root of a usb-key.
also, its not 'linuxdd' its 'linux dd'
You can also give dd the remote network location for the driver disk, eg dd=http://foo/bar.dd.img : Does not work well, if its the network interface you need the dd for :D
Karanbir Singh wrote on Tue, 15 Apr 2008 18:20:09 +0100:
usb keys work fine as driver disks on centos-5, the .dd image can be loop mounted and the contents copied out onto the root of a usb-key.
also, its not 'linuxdd' its 'linux dd'
You can also give dd the remote network location for the driver disk, eg dd=http://foo/bar.dd.img : Does not work well, if its the network interface you need the dd for :D
thanks, gonna try both methods tomorrow. So, that .dd floppy image is not meant to be offered as a file source via that manual driver install option? What kind of file does that option want, an rpm? (HP has rpms, too). A .ko?
Kai
Kai Schaetzl wrote:
Karanbir Singh wrote on Tue, 15 Apr 2008 18:20:09 +0100:
usb keys work fine as driver disks on centos-5, the .dd image can be loop mounted and the contents copied out onto the root of a usb-key.
also, its not 'linuxdd' its 'linux dd'
You can also give dd the remote network location for the driver disk, eg dd=http://foo/bar.dd.img : Does not work well, if its the network interface you need the dd for :D
thanks, gonna try both methods tomorrow. So, that .dd floppy image is not meant to be offered as a file source via that manual driver install option? What kind of file does that option want, an rpm? (HP has rpms, too). A .ko?
now would be a good time to look at the installer docs at www.centos.org/docs/
also, i suggest you make an effort and actually try a few options. You need the driver disk images, either with the kmod's or with the normal 'legacy' type dd layouts for this to work at install time. if you see rpms' outside the DD image, its not going to work at install time.
Karanbir Singh wrote on Tue, 15 Apr 2008 21:17:26 +0100:
now would be a good time to look at the installer docs at www.centos.org/docs/
well, the problem is that the docs do not say anything about what kind of file that function wants to see. http://www.centos.org/docs/5/html/5.1/Installation_Guide/ch07s04.html "If you need to use a driver image, such as during a PCMCIA device or NFS installation, the installation program prompts you to insert the driver (as a diskette, CD-ROM, or file name) when it is needed." And that was it. That's not with "linux dd", it's later when anaconda by itself specifically allows me to provide the driver when it needs it. It allows me to pick filenames from the media. Very well. But what kind of file does it expect? If it expects me to select a dd image file. Well, I have already done that and it fails. That's why I'm asking what kind of file that anaconda dialog expects. If it expects something other than a floppy image then it's obvious why it fails.
Kai
On Tue, 2008-04-15 at 23:01 +0200, Kai Schaetzl wrote:
Karanbir Singh wrote on Tue, 15 Apr 2008 21:17:26 +0100:
now would be a good time to look at the installer docs at www.centos.org/docs/
well, the problem is that the docs do not say anything about what kind of file that function wants to see. http://www.centos.org/docs/5/html/5.1/Installation_Guide/ch07s04.html "If you need to use a driver image, such as during a PCMCIA device or NFS installation, the installation program prompts you to insert the driver (as a diskette, CD-ROM, or file name) when it is needed." And that was it. That's not with "linux dd", it's later when anaconda by itself specifically allows me to provide the driver when it needs it. It allows me to pick filenames from the media. Very well. But what kind of file does it expect? If it expects me to select a dd image file. Well, I have already done that and it fails. That's why I'm asking what kind of file that anaconda dialog expects. If it expects something other than a floppy image then it's obvious why it fails.
Kai
Yea, it's pretty obvious why it really fails. I'm sure HP did not type up that readme file for no reason. I'm also pretty sure there are a few people reading these threads that are confused right about now. They probably don't know what to make of the situation. I am also getting confused because I did not like the comment about you saying you were going to go to the HP Forums to see how smart they were!!! I also bet they are not NICE as the "centos-lists". If indeed this is a new HP Server (i'm to lazy to look it up) they have phone support. My thoughts are that its been about 2 days and you have not even began to put a dent in it (you know doing it the way hp said) because you did not even mention the driver install failing from the boot prompt.
This is not a grip it is the Truth and Facts....
I hope you don't expect me to snap back in the same tone that you used. I suggest you read what is written and not what you want to interpret in it. BTW: HP does not support Centos installations, they support only RHEL installations.
Kai
Kai Schaetzl wrote:
And that was it. That's not with "linux dd", it's later when anaconda by itself specifically allows me to provide the driver when it needs it. It allows me to pick filenames from the media. Very well. But what kind of file does it expect? If it expects me to select a dd image file. Well, I have already done that and it fails. That's why I'm asking what kind of file that anaconda dialog expects. If it expects something other than a floppy image then it's obvious why it fails.
what did VC#3,4,5 haveto say about why it failed ?
Karanbir Singh wrote on Wed, 16 Apr 2008 09:51:54 +0100:
what did VC#3,4,5 haveto say about why it failed ?
I already provided this information by myself very early on in a reply to John. In the meantime I was able to install. The problem was something very different. My FTP server somehow had a hickup and wouldn't deliver the kickstart file anymore (I had stated in my second posting I'm using kickstart, just for info). So, I realized I had never tried a non-kickstart install before. That didn't have a problem and didn't need additional drivers. I then checked the kickstart file and found that I had accidentally copied and edited the wrong file and overlooked that it gave a cdrom as the installation source. There is no cd rom and that error message about manually choosing a driver and presenting all those storage drivers was misleading me to believe it was looking for the RAID driver while it actually was looking for a driver that would help it find the CD.
Thanks for your efforts, Karanbir!
Kai
Kai Schaetzl wrote:
Karanbir Singh wrote on Wed, 16 Apr 2008 09:51:54 +0100:
what did VC#3,4,5 haveto say about why it failed ?
I already provided this information by myself very early on in a reply to John.
oops, sorry - missed it. That email seems to have not made it to my mailbox :/ I just looked through the thread and cant find it.
In the meantime I was able to install.
excellent!
overlooked that it gave a cdrom as the installation source. There is no cd rom and that error message about manually choosing a driver and presenting all those storage drivers was misleading me to believe it was looking for the RAID driver while it actually was looking for a driver that would help it find the CD.
ouch. I've never seen that myself.
Is there really no clear information on the anaconda screen that indicates its looking for a SOURCE to install from rather than a TARGET to install to ?
Karanbir Singh wrote on Wed, 16 Apr 2008 16:58:42 +0100:
Is there really no clear information on the anaconda screen that indicates its looking for a SOURCE to install from rather than a TARGET to install to ?
In hindsight I know what it means but at the time of the encounter I didn't realize that. As I didn't have anything else in mind than an installation over network (I must have picked the only kickstart file that doesn't use network installation, I wasn't aware that I had any) I was wondering "what the heck does it mean with that?". The anaconda message that pops up says:
"unable to find any devices of the type needed for this installation type. Would you like to manually select your driver or use a driver disk?"
Kai
On Thu, 2008-04-17 at 17:31 +0200, Kai Schaetzl wrote:
Karanbir Singh wrote on Wed, 16 Apr 2008 16:58:42 +0100:
Is there really no clear information on the anaconda screen that indicates its looking for a SOURCE to install from rather than a TARGET to install to ?
In hindsight I know what it means but at the time of the encounter I didn't realize that. As I didn't have anything else in mind than an installation over network (I must have picked the only kickstart file that doesn't use network installation, I wasn't aware that I had any) I was wondering "what the heck does it mean with that?". The anaconda message that pops up says:
"unable to find any devices of the type needed for this installation type. Would you like to manually select your driver or use a driver disk?"
I have just put 2 + 2 together in figuring out you are the same one that was asking about the kickstart configuration a few days back on how to configure it. I had no idea that these two problems were related. I indeed thought they were separate problems.
So the whole time it pas pulling the wrong kickstart file?
Kai
John wrote on Thu, 17 Apr 2008 11:52:32 -0400:
I have just put 2 + 2 together in figuring out you are the same one that was asking about the kickstart configuration a few days back on how to configure it.
wrong math.
Kai
On Thu, 2008-04-17 at 18:38 +0200, Kai Schaetzl wrote:
John wrote on Thu, 17 Apr 2008 11:52:32 -0400:
I have just put 2 + 2 together in figuring out you are the same one that was asking about the kickstart configuration a few days back on how to configure it.
wrong math.
So you are or are not the one ? Not? If not i am wrong then....
Kai
On Tue, 2008-04-15 at 18:20 +0100, Karanbir Singh wrote:
John wrote:
****See here there is a reason I said type{linuxdd} and USE A FLOPPY. A usb stick is not going to do the job. I don't think you read the README!
usb keys work fine as driver disks on centos-5, the .dd image can be loop mounted and the contents copied out onto the root of a usb-key.
And, I say for him to use a floppy if the server has a floppy drive. Now why?? It will take out his layer of complexity because using a the USB Drive requires to much effort from him to comprehend on how it should be done.
also, its not 'linuxdd' its 'linux dd'
Yeap, you's right 'linux dd'
Well, now if he read a little bit he would get the point and figure it out. He did not even read the Readme file about the driver to start with and how to install it. I believe he just linked into the email and that was it. Maybe I'm wrong...
You can also give dd the remote network location for the driver disk, eg dd=http://foo/bar.dd.img : Does not work well, if its the network interface you need the dd for :D
Karan, if he even would have attempted to even read the driver readme I do not think he would be saying anaconda installer want take the driver or what have you. I don't know but I have got the feeling that using 'linux dd' and the driver image will work.
John wrote:
I don't know but I have got the feeling that using 'linux dd' and the driver image will work.
prolly will, at this point I am not sure if Kai is even making an effort to actually install anything. The lack of any real anaconda error message or content from vc#3,4,5 seems to indicate so.
On Wed, 2008-04-16 at 09:54 +0100, Karanbir Singh wrote:
John wrote:
I don't know but I have got the feeling that using 'linux dd' and the driver image will work.
prolly will, at this point I am not sure if Kai is even making an effort to actually install anything. The lack of any real anaconda error message or content from vc#3,4,5 seems to indicate so.
Well we have made an effort and he needs to atleast try. The worst that could happen is it not working. Better Yet, the Disk Controller being no good. If he is really having probs then maybe he should try a Live CD or a HP Hardware tester (if one is available).
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&a... They have 2 different versions here for the HP DL140 G3. I think this is what he wants - mptlinux-4.00.13.01-2.rhel5.i686.dd.gz. That's for 'x86' and he mentioned the mpt drivers. Main Driver Page: http://h18004.www1.hp.com/products/servers/linux/dl140g3-drivers-cert.html
Pretty new server if you ask me. Seems like it should have HP support or service contract still. Kinda wondering why he has not called them? If it came from HP with RHEL then he can call them *if* he has a 'Subscription'.
John wrote on Wed, 16 Apr 2008 01:42:42 -0400:
And, I say for him to use a floppy if the server has a floppy drive.
Ahm, what makes you think there was a floppy? My decision to use a USB stick?
Kai
On Wed, 2008-04-16 at 16:31 +0200, Kai Schaetzl wrote:
John wrote on Wed, 16 Apr 2008 01:42:42 -0400:
And, I say for him to use a floppy if the server has a floppy drive.
Ahm, what makes you think there was a floppy? My decision to use a USB stick?
USb floppy but from what I gather by looking @ it there is none that was after I said that please excuse me.
Kai
Kai Schaetzl wrote:
That "HP Internal Port SAS/SATA HBA with RAID" actually is a RAID controller from LSILogic and I tried to load all four LSILogic drivers provided on the driver list, but none is accepted.
HP raids tend to have custom microcode to implement various HP specific features such as media interchange between all their different systems, so they aren't likely going to work with the hardware vendors generic OEM drivers.
John R Pierce wrote on Mon, 14 Apr 2008 20:45:46 -0700:
HP raids tend to have custom microcode to implement various HP specific features such as media interchange between all their different systems, so they aren't likely going to work with the hardware vendors generic OEM drivers.
I see. It looks, though, like they provide the genuine LSI drivers. There is an mptlinux-4.00.13.01 driver from 2007 at the LSI site for the SAS1068 controller while HP provides a mptlinux-4.00.13.01-2 driver. It could still be different, but from the sights it just seems to be a newer version.
Kai
-
John -
John R Pierce -
Joseph L. Casale -
Kai Schaetzl -
Karanbir Singh -
Scott Silva