[Hp Smart Array P400 Drivers Download
Elpidio Heart
hello i want to reinstall the windows operation system in DL380 G5 server, i want to get the DL380 G5 smart array p400 controller driver for SAS hard disk , could you sent me the download link for that?
Good morning , could you support to me in the following issue ? customer has installed a HP PROLIANT SERVER DL 380 G5 for more than 9 years , it has a SMART ARRAY P400 installed also for more than 9 year working every day more than 78800 hours continue , suddenly the card has started to fail , and when we boot the machine the card is not seen when we see the display from server , we have done at least 10 times the procedure and 9 times it is not showed , just one time it was showed , Smart Array P 400 controller failure ( Not Found ) ( PCI DEVICE missing ) .
it happens when we boot the machine at the beginning when the Server start to identify the hardware , there is another scsi card installed but it is identified at boot step properly , but not the SMART ARRAY CARD
Updating the HP DL360G5 System ROM to revision P58 3/9/08 or higher is required in addition
to updating to this HP Smart Array firmware revision for the modified shutdown sequence to ensure
sufficient time for HDD head parking of internal HDDs.
because the server can not boot properly because the smart array P400 problem , how could we to install System ROM to revision P58 3/9/08 or higher , HP MSA 60 and/or MSA 70 firmware version to 2.16 and the upgrade from smart array P400 ?
That we would need just the executable to update the HP BIOS as I mentioned before , 2.16 MD and the SMART ARRAY P400 ( 7.24B) that we have downloaded the executable but it would need to update the BIOS just if we use the 7.24B version
this machine was installed some years ago and the guys used all the drivers delivered by HP , it was 2008 year , the Server has installed an application which it should be handled carefully and we would need just the additional to achieve that the SMART ARRAY P400 work properly .
This packages has been enhanced and enhanced and used to support HP 410i Smartarray beefore more recent ones were added. Also AFAIR, all HP Smartarrays can be driven with the hpsa driver set. However, this package allows you to create media for btld (boot-time load driver) which is what you are going to need. If this package doesn't work for you try searching for hpsa driver.
I see that someone mentions that it is part of an EFS 5.770a tar file. Problem is that I don't have a Unix server to process a tar file until I build this server. Catch-22. A simple BTLD image file would be great.
NOTE: If you have downloaded and extracted the tarball contents on a
windows box, you may use the rawrite.exe file to create EFS
diskette set. You may download tls096.zip from SCO website
at Refer to RAWRITE.DOC
file present in tls096.zip for license agreement and usage.
Hmmm, well, yes - quite some time ago I managed to make a USB stick look like a bootable 180 kB floppy to my PC, composing floppy boot sector structures (BIOS parameter block, NO MBR!), FREEDOS boot files, and a rescue program into a very small partition. Booting it was a two step process: set the BIOS to recognize the stick as a floppy, and then booting the stick.
Interested in the details?
@RudiC........In this case, SCO is installed by booting from DVD/CD but then reading boot-time disk drivers from a floppy during the process. So it isn't the case that we need the floppy USB stick bootable. Just a USB stick to be recognised as a pseudo floppy during the installation after booting from DVD/CD. Incidentally, generally if I need to create a bootable floppy (I'm really lazy!!!) I use a free downloadable Windows based package called Rufus and it does all the work. It will convert an ISO into a bootable USB stick. Well worth checking it out.
@jgt........They look like two really useful pieces of software. I will be checking them out. Thanks. Like the archaeologist said, "I didn't find it because I wasn't looking for it", however, now I've found it, it'll be in my toolkit.
JGT, hicksd8, RudiC, many thanks. I've managed to get a usb floppy regognised by the system already (attach with a floppy disc in the drive at boot time) and to download the wd v 3 BTLD for the CD ROM so that's not a problem.
A fast and reliable storage controller is one of the most important parts of a Proxmox VE server. This article lists some hardware raid controllers that are known to work well and some information configuring them. You can use the lspci command in the Proxmox command line. Look for a line with RAID Controller or similar. For a RAID controller to be supported, it must be a "real" hardware controller rather than an embedded or "fake" RAID. Embedded controllers are not supported in Proxmox, and if they do work, you are doing so at your own risk.
Paramount feature for real raid controller if you want high performance is an on board cache and "write back" mode enabled. This way the OS doesn't have to wait until data is physically written to disk, since they are immediately written to the cache and the controller will take care of finishing the subsequent write to the disk(s). If you don't want to loose your data in case of black-out, you need a battery backup (BBU). That ensures that any pending writes during a blackout can finish being saved as soon as power is restored. Some controllers support using an SSD so that a BBU isn't so important, but some SSDs do not deal with power loss well, do your research before relying on this solution.
A RAID controller using write-through instead of write-back behaves very poorly. You can use the command pveperf to have a general idea of performance. Look at the FSYNCS/SECOND value.Here is a real world example of the performance you can expect.
The configuration of the RAID array can also have a major impact on performance. RAID 5 should not be used with modern hard drives because rebuild times are long enough that a second drive could fail causing the entire array to be lost. If you were planning on using RAID 5, consider using RAID 6 instead. That being said, RAID 6 should be considered slow. If you are looking for performance, look for something that stripes you disks. RAID 10 or 60 is generally considered a good balance of performance to redundancy with RAID 60 providing additional layers of redundancy.
This Adapter is working well under Proxmox. Attention: make sure you have write cache enabled and use a BBU! Without write cache the vms seem to 'hang' or 'freeze' sometimes. Performance give about 50MB/s on a Raid 5 with 3 HDD's a 1TB
All Adaptec controllers with BBU unit are known to perform well. If possible, take one with "Zero-Maintenance Cache Protection", e.g. Adaptec 5805Z or 6405/6805 with Adaptec Flash Module 600 (AFM-600)
Monitoring your disks is important so that you can know to replace any disks that may be failing. The following is how you can manually fetch the status of a disk in array. The first time you want to monitor the smart status of your disks, you must install the smartmontools package.
After that, you can use smartctl to fetch the status of any particular disk in the array. Just change the number after the comma (,) to indicate which drive in the array you care about. The following example checks the second disk. Changing the 1 to a 0 would check the first disk.
My problem is that I can't get the DBAN build environment to work. If I could, I'd apply the above patch myself without changing the kernel.. which is actually all I need. The standard DBAN kernel works with HP DL380 G3 using the SmartArray controller it just doesn't know the device name.
Hi elfarto / all, i had tried the customized version of deban 2.2.6 on one of the HP Proliant DL380 G4 with HP Smart array 6i controller , it detected the disk after which it errors that /etc/nit.d/main cannot mv the file /var/log/lshw.xml as it cannot found, kindly assist
- Tronado
juanino, thanks for the ISO. I downloaded it and booted OK, but it does not detected disks on my DL360 G4 with a SmartArray 6i controller. There are two disks and I've broken the RAID array. I've tried them as unconfigured drives and I've also tried them as individual RAID 0 disks.
I'm testing this today. It appears that even though I built the CD correctly and get it to boot, it's still not recognizing the disks. I've got some hardware to test on now and I'll be re-testing it with the iso. I'll get back to you.
I've resorted to the Ubuntu live CD and running a random DD, but I'd love to be able to use DBAN properly. These servers are old and slow and not having an indication on progress of the DD is making life difficult.
I have a bunch of HP DL360 G4s and a pair of HP DL380 G4s I'm using to wipe the rest of the disks. While I was on site, I had no problem modifying the /etc/init.d/main file with Andrew's changes, and that worked. However, I really need a remastered ISO with 2.2.6 with at least those changes. The 2.2.7 ISO reports a different error, and I really didn't have time to dork with it.
Hi and sorry to bring up such an old thread but i have another problem.
first of all, thanks to "cable and wireless", that helped me to get dban recognize dban, but now to the problem: i have 2 raid controllers (both smart array p400 with different versions) and dban only recognizes 1 of them, would it be enough if i edit the main from DBAN_SD_FOUND=$(find /dev/cciss -type b grep '/c0d[0-9]+$' ) to DBAN_SD_FOUND=$(find /dev/cciss[0-9] -type b grep '/c0d[0-9]+$' ) so it can regocnize both raids?
and the second problem: when i alter the main and write :w and :x (using "vi main") and then run ./main it uses my altered code but when i restart the code is changed back to the default. how do i change that permanently? im using an usb-stick.
HP Proliant ML370 G5 server, RAID 5 degrade volume, one drive dead, second predicted fail. Need to recover the server that currently can't boot. Array Configuration Utility shows "background parity code 786 Background parity initialization queued or in progress on Logical drive 1.I tried and the server currently can't boot into it's SBS 2003 OS.
795a8134c1