925937f38b to burn a DVD and autoupdate with it. Your BIOS must be dated later than 2008 for this to work as well.Įasiest solution for the firmware problems of your D元60G5? Use the Smart Firmware DVD v10.10 (last free version) located at. v7.22 is the last "free" version out there that I was able to find although the latest is actually v7.24 (with fixes that I'd like, but free support from HP is difficult, even for an HP employee). It does require that your P400 firmware is >v4.0 to work (or even the hpsa can't find it).
HP CCISS CENTOS DRIVER INSTALL
I only did the "hpsa.hpsa_simple_mode=1 hpsa.hpsa_allow_any=1" on both the install and the grub update to get things to work.
HP CCISS CENTOS DRIVER PATCH
I can live with the constant log entries about the failed insertion, at least until the patch comes out. But at least I'm not spinning my wheels trying to figure this one out anymore. I do not know however when the fix will be released into the kernel patches nor how long it will take to propagate down to my level. This issue was raised as a bug and is being addressed as of JAN2017. Your only option is to look at it during the reboot/controller initialization phase. This means that you can't look at the SMART status, drive status, controller status, etc while the machine is running.
HP CCISS CENTOS DRIVER DRIVER
The system/drives work fine (they all were correctly added using the hpsa driver as listed in my last post) but your hpacucli program won't. So the controller never gets added to the device chain. hpsa 0000:06:00.0: addition failed -19, device not added. As such, you'd see the error:Ĭode: Select all hpsa 0000:06:00.0: scsi 2:0:0:0: added RAID HP P400i controller SSDSmartPathCap- En- Exp=1
![hp cciss centos driver hp cciss centos driver](http://homepagesupport.weebly.com/uploads/1/2/4/8/124811434/497061960.png)
What this created was a situation where the P400 tried to register itself with the SCSI system and it used the same registration ID as the first drive hence causing a conflict. There was a patch created that was supposed to detect the collisions and move the controller over to slot 3 (by default) but if your controller didn't respond to SCSI v5 correctly, it wasn't detected as a controller (the P400 is old enough that it had this problem). Additionally the controller itself was also reporting 0. What happened that prevented it from working was that the older RAID controllers started their first drive as SCSI target 0 reporting to the OS.
![hp cciss centos driver hp cciss centos driver](http://ensunucu.com/wp-content/uploads/2014/12/cciss_hpsa_yapi.png)
It also causes consistant entries in your dmesg log about an error that will not be fixed until another patch is released for the hpsa module. This bug is what prevents the P400 from being recognized as a driver. There is a bug that in the hpsa module that was introduced NOV2016 as a fix for other problems (the fix created a problem). You do not apparently need the kmod-cciss.x86_64 driver module for this to work. Some things I have discovered with further experimentation.ġ. Ok, a TREMENDOUS amount of further work done only to discover that there is nothing I can *currently* do about this.