I have a DL380 G7 server which we are reusing for backups.
I recently took a working Ultra 320 ISCI card PCI X from a server we are decomissioning and decided to add it to it so we could hook up an autoloader drive.
Put it in via a PCI-X slot and the server refuses to boot, any ideas??
BIOS for DL360 G5
Search on internet: cp015225.
Link: https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_1532636ea34e4bb699ba366c27&swEnvOid=4024
** CRITICAL ** Online ROM Flash Component for Windows - HP ProLiant DL360 G5 (P58) Servers
Kind regards,
Fred
Hi,
I stripped the entire machine down to the chassis.
Cleaned each component as I reassembled.
Then started from a minimal configuration, working back to the full config, yet not luck !
The quickspec is showing a single supported SCSI card, but it is PCIe:
HP SC11Xe Ultra320 Single Channel/ PCIe x4 SCSI Host Bus Adapter
412911-B21
You have this special PCI-X/PCIe riser card in the server?
What is the exact model of the SCSI controller?
Yea I saw that not long ago about only being a single channel on the compat list. Not a special riser just the one from the optional list which weve had for a while.
I haven't got the number of the card on me as i have put it back in the old server and ran it back up. I have however decided to order that SCSI card just to resolve any compatability issues.
Hello,
One of my HP DL360P servers will be upgraded with SSD drives. I have two arrays. The first one use raid 1 for the operating system. The second array uses RAID 1+0 on 6 drives. I want to replace the second array with larger and faster SSD drives. My question is very simple. Can i disable the second array and replace the drive with SSD while the machine is running, or do I have to shutdown the machine, replace the drives and then configure them in the Smart Storage Administrator? Sorry if my question seems stupid but since I haven't done this on an HP server with a Smart Array P420i, I prefer to ask first in case I am missing something. Thanks in advance.
April 2018 and the issue still exists, at least it does on a DL20 Gen 9 manufactured in Sept 2017. The solution offered by LogicalStep to go back the the raid configuration and select the array to be the boot drive is what worked for me. With this being a known issue for three years one would think that it should be fixed by now.
wrote: Hi,
I have a Proliant DL360 Gen9 and need to config all UEFI settings with scripts.
I use conrep to set all the UEFI settings I need.I have a HPE Ethernet 10Gb 2-port 560SFP+ Adapter installed and need to set the following:
I need to set F9 -> System Utilities -> System Configuration -> Slot 2 Port1 : HPE Ethernet 10Gb 2-port 560SFP+ Adapter - NIC -> Device Level Configuration -> Shared Memory Features -> Disabled
This setting is not saved in the config file generted with conrep -s because it's "outside" of the RBSU settings.
What linux scripting tool can I use to get to this setting?
Thanks.
Currently none of the HPE scripting tools can modify the settings on add-in cards. You might check with the NIC vendor as they may have a tool
I am having this issue as well and it is damned infuriating.
It all started after I applied 2018.3. I've tried reverting everything to 2017.10. I am now trying 2017.7, but this is getting ridiculous.
How hard is it to fix some bloody fans?
It doesn't solve the problem for me.
And unfortunately this server recently fell out of warranty status, so HP won't even fart in my general direction.
No errors in the health logs. I've tried updating everything with SPP 2018.3, SPP 2017.10 and 2017.7, and the problem still won't go away. It's been like this for almost a week now.
And now one of the hard drives has failed. Don't know if the constant high fans rattled its connections loose or something, but now I can't even experiment further until the array rebuilds. Don't know if that also causes the fans to go crazy, but until the array is rebuilt I can't play anymore firmware flash merry go round.
wrote: It doesn't solve the problem for me.
And unfortunately this server recently fell out of warranty status, so HP won't even fart in my general direction.
No errors in the health logs. I've tried updating everything with SPP 2018.3, SPP 2017.10 and 2017.7, and the problem still won't go away. It's been like this for almost a week now.
And now one of the hard drives has failed. Don't know if the constant high fans rattled its connections loose or something, but now I can't even experiment further until the array rebuilds. Don't know if that also causes the fans to go crazy, but until the array is rebuilt I can't play anymore firmware flash merry go round.
What does iLO report the fan speeds at? Have you looked at the system tempatures in iLO to see if something is running warm? Has the ambient room tempature increased? Verify in RBSU the thermal settings are not set to max or increased cooling as those option will spin the fans faster. You checked both iLO and the IML logs?
.
We were repurposing the machine, and in the process I reconfigured the array from JBOD to RAID10, and I applied SPP2018.3. The problems immediately started occurring after that. There were zero problems prior.
The environment itself (server room) is identical to what it was before. I checked the bios system health report and everything showed up as Healthy. I haven't had time to dig further than that.
Hello,
I've recently installed an NVMe drive onto a PCI-e adaptor, and installed it into a Dell R610, which is older than a Gen8 DL380p. This worked, using a USB to boot from and the NVMe drive for the OS.
I've attempted to do the same on the HP server, but I've hit a snag. The PCI-e device is not being detected... at all. Is it possible that I need to appy a BIOS update, or some firmware in order for the server to detect the drive. I've attached an Image of the SSD in the x16 PCI-e slot.
Any help with getting the drive the be detected by the server, would be much appreciated.
Regards,
Rohan
Ignore this, looks like the drive I had ordered had a capacitor installed the wrong way round, and so need to return it. Test with a different drive (same make/model) and that works just fine.
We have fixed this issue and link is working now : https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04272529
Thanks,
Vajith
That is not how PCI-E or SATA works. Your drives will connect at whatever SATA speed standards the card supports. for connecting to drives (SATA 1.0 = 1.5 Gbps, SATA 2 = 3Gbps, or SATA 3 = 6Gbps). Getting data off or onto the card is an independent operation by PCI-E bus using the maximum combined bandwidth of all available real slot lines. But shortage of PCI-E bandwidth (lanes) can make communication with drives pause when onboard buffers fill up.
Quite often only certain combinations of PCI-E slots can operate at the same time. Extra slots are there merely to present the same lanes in a different mechancial intereface option. Furthermore individual PCI-E slots quite often do not include all lanes the connector supports, but instead provide more mechanical support or allow high end cards to operate at lower bus speeds. So x8 slots might have only x4 real lanes. PCI-E version changes the speed of individual PCi-E lines in a way similar to SATA version increments.
I will note that x4 PCI-E 1.0 slot actually provides 8Gbps bandwidth such that when talking to 1-2 SATA 2.0 drives that there is sufficient bandwidth for uninterrupted max performance. That is assuming non-RAID, RAID 0 or 1 operations and that the CPU can manage all striping "calculations" if software RAID 1 is used. So really only higher RAID options talking to many dirves at once are slowed. Even then disk operations may not be slowed at the card and bus. If your advanced RAID is software driven, the load of RAID on the CPU quite often throttles disk I/O back so far that the card itself can keep up with what has become a CPU limited I/O process.
It is true that SATA board drivers might balk at version 1.0 PCI-E. But in general backward compatibility is pretty good. Again I suggest you look more closely at how you use the SATA cards. Do you have hardware RAID drivers or is RAID software driven. If sofware driven, then CPU splitting data into strips and calculating data redundancy error codes could well mean the bottleneck is these old CPUs.
If no RAID - well a x4 PCI-E 1.0 card is more than fast enough to keep up (almost 3 SATA2 drives at once continuouosly) - unless you got a ton of simple VMs doing max I/O with little processing of data. Which is why I suggest you confirm where the bottleneck really is.
FYI - on separate issue with SE1101 servers ...memory slots. There is a reason that why many SE1101 will only accept 4 memory sticks -- the dual CPUs have only 2 memory channels each. 16GB limit.
No docs still online. But I think one memory slot is wired to each channel of each CPU. That is I do not think this server has an interleaved mode for the memory banks.
So to use all 6 slots you need a CPU that supports 3-memory channels. In general look for 56xx series CPUs. Actually I think you may need dual 56xx series. 24GB limit
Hey there,
we got a DL380 Gen8, P420i Controller, 19 SSDs - 3 Arrays, 3 logical Volumes, 2 OK, 1 with Error "Parity initialization failed" ... already searched for this Failure - but haven't found anything helpful on that! :-/
Is there any way to check "why" the initialization failed? And how do I force the Controller to redo the init?
Thx, bye from Austria
Andreas Schnederle-Wagner
