- Hp smart array p410i controller raid 50 serial#
- Hp smart array p410i controller raid 50 software#
- Hp smart array p410i controller raid 50 plus#
- Hp smart array p410i controller raid 50 windows#
Hp smart array p410i controller raid 50 plus#
Plus the first ever PSOD -> Perc H700 - buggy firmware caused entire server to crash PSOD in ESX! There was 6 months when the buggy firmware was the only option. Plus $269 for P420/1GB FBWC - no competition on pricing - Simple SAAP 2.0 key enables advanced functions for HP (including hp smartcache / hp smart path). HP has the flash back write cache - super-cap - awesome! LSI battery -> you feel it when the monthly battery drain drops the array into read-cache only mode causing latency issues all over the place. HP smart array uses a "idle XX seconds" scan for bad sectors. The battery and patrol scan - epic fail on LSI. Maybe raid-5/6 but I don't really use that.ĭatabase wise - same speed - limited by drives. SAAP 1.
Hp smart array p410i controller raid 50 software#
To access SAAP features, activate the software with a registered license key. Honestly with the H700,P400,P410 with 4 or 6 drives raid-10 - same speed. HP Smart Array Advanced Pack 8 HP Smart Array Advanced Pack About SAAP SAAP is a collection of additional and advanced controller features embedded in the firmware of select Smart Array controllers. The User interface - epic fail on LSI big time. LSI out of the box requires far more steps. Then there is the little stuff like HP defaults to pull a failed drive and re-insert it - no action required to rebuild "the ole pull n push trick" to rebuild. Hell HP P400 was LSI chipset and P410 was PMC-Sierra, yet the raid and utilities are 100% compatible, whilst the P420/P430 are still compatible - good luck migrating LSI raid sets across generations. I've tested the lot - trust me - LSI megaraid is far buggier than HP. They seem to have used all default settings, which could have favored either card given any particular workload.
The Dell H700 supports 512MB or 1GB of cache, if I remember correctly.ĥ) I didn't see any attempt to tune the controller settings for maximum performance for a given workload. The HP P4xx cards come with 256MB, 512MB, or 1GB of cache, and there is a very large performance difference between these configurations. The low profile, half height card has 8 ports and utilizes DDR2-533 memory.
Hp smart array p410i controller raid 50 serial#
RAM speed could also have been different - or not since they didn't specify.ģ) Two different expander backplanes in the arrays.Ĥ) The very small test size (4GB) means that cache will contribute greatly to the results, but I did not see a mention of how much cache each card had. The HP Smart Array P410 is HPs PCI Express (PCIe) 2.0 Serial Attached SCSI (SAS) RAID controller. In the case of a BIOS problem, the performance difference between the two could be very large. Same CPU across both, but still two different servers tested. Here are the issues that I noted:ġ) Two different servers. More specifically, there were too many unspecified configuration details and outright differences between the two test systems to conclude that one controller or the other is better. The nightmare begins again.As much as I love head-to-head benchmarking, this one is too loosey-goosey to be useful. Controller HP Smart Array P410i, Firmware Version 1.66, License Keys SupportedĪs you can see there is no OnlineSpare configured!! ARGH. Hpacuscripting.exe -internal -c "PathToFile.ini" The command completes successfully (nothing in PathToErrFile.ini) I don't seem able to configure an Online Spare with this tool.
Hp smart array p410i controller raid 50 windows#
also no good from my perspective as I don't know Linux, so would have quite a learning curve have managed to find the HPACUSCRIPTING.exe for windows at last!! You are right, this does appear to replace hpacubin.exe and has the same commandline params. and would mean re-engineering our automated build process significantly. For the input, but to change our process to LinuxPE would be a huge nightmare.
0 kommentar(er)
