Tag Info

Hot answers tagged

4

I'm just going to refer you to the ProLiant hardware troubleshooting flowchart listed here. I dont know what OS is/was on it and would love to reset the whole thing but i can't even get that far... That's concerning. Where did this server come from? Was it a known-good functioning system at some point? Even beyond that, HP ProLiant Gen8 equipment ...


4

No. This is not possible. The HP ProLiant DL380 G6 isn't a new server, though. It's three generations removed. If you're trying to use this for vSAN, don't. If it's any other situation where you need access to the RAW disk devices, you should purchase a dedicated SAS HBA from LSI or an HP-branded LSI controller. This can then be connected to the backplane ...


3

So, I'll pose another question: Why is it necessary to run HP Insight hardware diagnostics on servers prior to provisioning? In my comment above, I indicated that there's little to gain by doing this preemptively in large HP ProLiant environments. I should clarify my thoughts on that... In order of descending frequency, let's look at the types of issues ...


3

Please look at your server's ILO4 interface. It will detail each RAM module, its slot number, HP Part Number, capacity, frequency, load (rank) and heath status.


2

Yes. The carriers are the same between Gen8 and Gen9 systems. No, don't use non-HP disks... especially cheap SATA. Because this:


2

I don't think you're going to find another LUN on the system after extending the array and logical disk, unless you created a new array with the single disk. You'll likely just see the existing LUN will have some free space, with which you can extend the datastore. Assuming you're using the c# client, go to the Datastore in question via the Configuration ...


2

Replace your existing disk first. The 146GB 2.5" SAS disks are no longer manufactured. Even HP sends 300GB disks as replacements for 146GB drives. You're in Spain, so your best bet is to buy one or two replacement 146GB drives from eBay. They're very inexpensive. The server you're using, an HP ProLiant ML350 G5, is very old. I would not recommend using ...


2

Wow... (there are special tools available for HP systems) Install the hpssacli tool: And then look at the output of the hpssacli ctrl all show config command: # hpssacli ctrl all show config Smart Array P410i in Slot 0 (Embedded) (sn: 50123456789ABCDE) array A (SAS, Unused Space: 0 MB) logicaldrive 1 (838.1 GB, RAID 1+0, OK) ...


1

Look at the lights on the drive... Are they amber? Why do you think the drive failed? If the drive failed, why is the server off (or why was it powered off)? I'm sorry the drive is not in a RAID, but seeing that also indicates that your server/RAID controller firmware and ESXi installation are likely outdated. There are older Smart Array firmware ...


1

If you want to "know 100% that it will work", you should not only look at the modules already installed but also at which module configurations are listed as supported in your Proliant's QuickSpecs (I assume this is a DL380p G8), the User Guide or the HP Memory Configurator. An excerpt from the relevant QuickSpecs' section: General Memory Population ...


1

Assuming you're running VMware ESXi/vSphere, you can run console commands to get more detailed information on the hardware components. Specifically, you should be able to get the part number, and look that up online. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003587 Note from point 2 in ...


1

dmidecode -t 17 Linux dmidecode|less for esxi 4.x smbiosDump for esxi 5.x also see this for vmware http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003587


1

It seems that 0114 relates to the Memory DIMMs. If nothing has changed, I suggest you begin troubleshooting as a bad memory issue. If you have recently changed memory DIMMs please test without them.


1

Most of the other answers here have addressed the management features of an HP server, but not so much the reasons you would see a performance difference. HP-specific features like iLO and Intelligent Provisioning are wonderful, but they do not make your compile times any faster. First off make sure you are really comparing apples to apples on the CPU/RAM. ...



Only top voted, non community-wiki answers of a minimum length are eligible