Quantcast
Channel: ProLiant Servers (ML,DL,SL) topics
Viewing all 10362 articles
Browse latest View live

Proliant system board won't boot

$
0
0
My Proliant 591747-001 system board won't post after attempting to install an NVMe drive via PCIe x16 slot. It was working fine up until that point. I'm not getting any error codes at all, the CPU only gets slightly warm, but my GPU and system fans blow at 100%. No Proliant splash screen. I tried swapping RAM sticks, removing CMOS battery, swapping CPUs, but still nothing. Any solutions to this issue or is it dead?

Installing Server 2016 or 2016 with Intelligent Provisioning

$
0
0

Hi,

Why is this always so difficult? It's been the same all the way since the G8's. You get a new server and the BIOS and firmware is completely out of date, so you use inteligent provisioning to update, only to find out that even that is not working and doesn't show you the latest firmware/BIOS.

So you think, "Oh, this is a bit poor but OK I will just download the latest BIOS/ILO and Intel Provisioning from the website directly, so I do this and its a pain in *** to be honest but I manage to get my new DL380 up to date for all the ILO/BIOS and Intel Provisoning.

Now I go to install Server 2019 with a fresh ISO from the VLSC MS site through Intel Provisioning, great I think Intel Provisoning has found the Server 2019 image and says its fine to use, great. I wait about 15 , 20 minutes for it to finish installing, the server reboots and I just get the below and it gets stuck

https://imgur.com/ApV0b3N

I then try and install Server 2016 the same way and get exactly the same thing, what am I suppose to do now? I can install outside of inteligent provisioning but WHAT IS THE POINT OF IT IF IT DOESNT WORK WHEN EVEN UP TO DATE!

So frustrating

Installing Server 2019 or 2016 with Intelligent Provisioning

$
0
0

Hi,

Why is this always so difficult? It's been the same all the way since the G8's. You get a new server and the BIOS and firmware is completely out of date, so you use inteligent provisioning to update, only to find out that even that is not working and doesn't show you the latest firmware/BIOS.

So you think, "Oh, this is a bit poor but OK I will just download the latest BIOS/ILO and Intel Provisioning from the website directly, so I do this and its a pain in *** to be honest but I manage to get my new DL380 up to date for all the ILO/BIOS and Intel Provisoning.

Now I go to install Server 2019 with a fresh ISO from the VLSC MS site through Intel Provisioning, great I think Intel Provisoning has found the Server 2019 image and says its fine to use, great. I wait about 15 , 20 minutes for it to finish installing, the server reboots and I just get the below and it gets stuck

https://imgur.com/ApV0b3N

I then try and install Server 2016 the same way and get exactly the same thing, what am I suppose to do now? I can install outside of inteligent provisioning but WHAT IS THE POINT OF IT IF IT DOESNT WORK WHEN EVEN UP TO DATE!

So frustrating

DL380 G10 with the NVMe slot PCI Express Gen 3 SFF-8639 X4

$
0
0
Hi
I have a problem with NVMe SSD disks on esxi 6.5.
I installed on the esxi the three vib as described by the intel manual:
intel-nvme-vmd-1.6.0.1003-1OEM.650.0.0.4598673.x86_64.vib
intel-vmd-user.vib
lsu-intel-nvme-vmd-plugin-1.0.0-4vmw.680.0.0.00000.i386.vib
I have enabled the EFI feature but the system does not recognize the disks and does not detect the VMHBAs where am I wrong?

The server is a DL 360 GEN 10
CZJ9080450
 
4-6.5.JPG

Conrep Error WbemLocator

$
0
0

Hello
I want to run the tool Conrep via WinPE. If I want to load or save a file, I get this error message "Error creating instance of WbemLocator Conrep return Code: 0"

Conrep commandl: conrep -s -f dl380gen9.dat
Server: ProLiant DL380 Gen9

10 Gbit NIC not working on HPE DL380 Gen10

$
0
0

Hello,

I'm trying to get a 10 Gbit Network Card working. But it is not possilbe. I have a new ProLiant DL380 Gen10 server with Windows Server 2016 Datacenter installed.

First I tried to use a Intel fibre channel card, but it didn't work. The port doesn't get any IP. Switch config is correct and works for other servers (Gen5 to Gen9). The card is recognized by Windows as 10Gbit NIC, and I get a link, but no IP. Even with fix IP I have no connection.

So I ordered a new HPE FlexFabric 10Gb 2P 534FLR card (I thought, the Intel card maybe is not compatible with the new Gen10 server anymore). But with this card I have the same issue. Card seems to be working, but no IP or connection possible.

Anyone an idea?

Thank You!
BobMarleyBob

HP ML350 G9 error 1627 - power supply solution not sufficient

$
0
0

Hey guys,

i was installing a GPU in this server, but was unable due to lack of a power cable, but since then i´m unable to boot the server  due to error "1627 power supply solution not sufficient", which is weird since nothing changed.

The server has 2* 500W PSU (green LEds)

I cleared NVRAM, no change.

Ordered a 1400w PSU , still get the same error.

i tried connecting the 1400w PSU and a 500W PSU, i get the different types of PSU warning, but then it says the 500W is broken, and the critical failure 1627.

I´m unable to F9 (or any  F key) since the system fails.

Any idead is welcomed :/ 

 

DL380p Gen 8 No Display No Post Red System Health LED

$
0
0

Hey all, we have a DL380P 25-bay SFF that we have been trying to get going. It was operational when it was shut down (to the best of our knowledge), but since bringing it to our office it will not post or give any display when powered on and the system health LED is flashing red. I will break down what has been done to try and resolve this issue.

1. Connected to iLo, it shows Bios/Hardware critical, does not show any server specific info such as firmware revisions etc it all says not available.
2. Reflashed the firmware for both the bios and the iLo - No Change
3. Took the server to minimal config with just 1 CPU, 1 stick of RAM - No Change
4. Tested the CPUs and RAM in another server and it booted without issue
5. Disconnected the SAS controller - No Change
6. Replaced the SAS controller with one out of a working server - No Change (although the SID on it does show the CPU as amber, if we have both CPUs installed it shows both as amber, if we drop it to 1 CPU it shows that 1 as amber, even with CPU from a working server, and having tested this CPU in another server and verifying functionality and that the CPU does not show amber on that server)
7. Replaced the power supplies and connector module to the motherboard with ones out of a working server - No Change
8. Replaced all of the fans with ones out of a working server - No Change
9. Replaced the PCI Riser with one out of a working server - No Change
10. Removed the raid cache card - No Change
11. Replaced the raid cache card with one out of a working server - No Change
12. Replaced the CPU with an identical one out of a working server - No Change
13. Reset iLo by removing the battery and power - No Change
14. Removed the NIC card - No Change
15. Replaced the NIC card with one out of a working server - No Change
16. Replaced the motherboard - No Change
17. Set the Dip switches 1,5,6 - No Change
18. Set the Dip switch 6 - No Change
19. Replaced the memory with memory from a working server - No Change
20 - Ensured we have the memory seated in the correct slots per the 1CPU and 2CPU config diagram on the case - No Change

At the point we replaced the motherboard, we took the old board and set it up on our bench outside of the case to be sure it wasn't a grounding issue - No Change
We now have 2 motherboards doing the same thing, one with the original hardware that was with it, and the 2nd with all the hardware on it having come from a running server.

When the server is powered off all lights are green. When we power the server on all lights stay green, fans spin up, right after that the system health LED goes to flashing red, no display, no post. If we leave it on the fans will occasionally still spin up/down as if trying to regulate temperature but they don't "stay spun up"...

We are at an absolute loss here.


Dl380 G7 Blinking Red Status LED

$
0
0

Dear Forum Users, Yesterday I received a DL380 G7 in the post, it was working great, no problems at all. Today I go to setup more VM's in ESXI, to find out the server won't turn on. The power button has the orange light like normal, but the status LED is blinking red. If I unplug the power, and plug it back in, it will automatically turn on for 3 seconds, then turn off for 3, for about 10 cycles. After that if I press power it will do the same. I've already tried different psu, different cpus, different ram, different CMOS battery, different power cables, different raid cards, pretty much everything. I've been doing the usual googling for a few hours and nothings working. I've also tried reseeting the NVRAM, which fixed it for a few minutes, then back to this. Also, the component status panel has no lit LEDs.

Dl380 G7 Blinking Red Status LED

ML30 Gen10 NVMe drive only shows 1GB

$
0
0
Hello!

According to the UEFI Setup, my Samsung 983 DCT M.2 NVMe drive is only showing 1GB available. The same happens in Windows Server 2019 setup. The drive works correctly in another computer (showing all 960 GB). I’ve tried this on two different Samsung drives. Is there a way to get my ML30 to recognize the full capacity? The BIOS is the latest available.

Thanks!

Windows server 2019 install issues Dl20 gen10

$
0
0
Hi I'm having issues installing server 2019 on a new Dl20 g10. Intelligent provisioning will not load the iso and from windows installer it will not find raid.

I've updated IP to 3.23 and the issue persists. It will not load the iso it starts to validate then blinks back to the previous screen.

So I went the other route and I'm still having issues.

I've pulled the appropriate driver HP smart array s100i from the hpe website and placed on a thumb drive. When booted into server 2019 install media it doesn't find valid signed driver.

Any help would be appreciated.

HP proliant ML570 G4 无法进入系统

$
0
0

在完成备份后,重启服务器显示:

attempting boot from Hard drive (C:)

attempting boot from NIC

attempting boot from NIC

broadcom UNDI PXE-2.1 V2.0.5

copyright (c) 2000-2006 broadcom corporation

copyright (c) 1997-2000 intel corporation

CLIENT MAC ADDR: 00 1A 4B 52 65 EE CUID:00000000 0000 0000 0000 000000000000

DHCP.....\

之后服务器不断地循环attempting boot from NIC 无法进入操作系统,但是服务器的健康指示灯都是正常的,请问大神帮帮忙,这是什么问题导致的?

Upgrading CPU Issue on DL380 Gen9

$
0
0

Hello ;

I have an issue with my sever when i adding a new CPU , the server boot with a black screen.

there are no error on IML LOG aloso NO problem detected on AHS LOG

I use the clear NVRAM and run the manufacturing default on bios ,but the issue is on going 

Any help for this issue please

Install server 2019 desktop experience whit intelligent provisioning

$
0
0

Hi

Im trying to install server 2019 desktop experience whit intelligent provisioning

But the only choice I have is standard core I have upgraded ip to 3.22 but still no luck

So my only choice is a manual install and then install drivers is little annoying.

 


Missing drivers to HP DL160 G9

$
0
0

Hi guys,

I'm using HP DL160 G9 server with Matrox F2408 extenstion card. I had a problem with USB ports connected to Matrox box. After some time the USB ports were freezing and showed error Code 24 ("This device is not present, is not working properly or does not have all its drivers installed"). Normally, after restart it was working properly for longer time and then after 7-10 days it froze again.

I have checked that I was missing these drivers:

Base System Device PCI\VEN_8086&DEV_6F1D&SUBSYS_21EA103C&REV_01\3&103A9D54&0&80 
Base System Device PCI\VEN_8086&DEV_6F25&SUBSYS_21EA103C&REV_01\3&11583659&0&25 
Performance Counters PCI\VEN_8086&DEV_6F34&SUBSYS_21EA103C&REV_01\3&103A9D54&0&81 
Base System Device PCI\VEN_8086&DEV_6F76&SUBSYS_00000000&REV_01\3&103A9D54&0&5B 
Base System Device PCI\VEN_8086&DEV_6F9C&SUBSYS_21EA103C&REV_01\3&103A9D54&0&F4 
Base System Device PCI\VEN_8086&DEV_6FAF&SUBSYS_00000000&REV_01\3&103A9D54&0&9F 
Base System Device PCI\VEN_8086&DEV_6FB7&SUBSYS_21EA103C&REV_01\3&103A9D54&0&AB 
Base System Device PCI\VEN_8086&DEV_6FBF&SUBSYS_00000000&REV_01\3&103A9D54&0&A7 
Base System Device PCI\VEN_8086&DEV_6FE5&SUBSYS_21EA103C&REV_01\3&103A9D54&0&65 
Base System Device PCI\VEN_8086&DEV_6F1E&SUBSYS_21EA103C&REV_01\3&103A9D54&0&85 
Base System Device PCI\VEN_8086&DEV_6F26&SUBSYS_21EA103C&REV_01\3&11583659&0&26 
Performance Counters PCI\VEN_8086&DEV_6F36&SUBSYS_21EA103C&REV_01\3&103A9D54&0&59 
Performance Counters PCI\VEN_8086&DEV_6F7D&SUBSYS_21EA103C&REV_01\3&103A9D54&0&86 
Base System Device PCI\VEN_8086&DEV_6FA0&SUBSYS_21EA103C&REV_01\3&103A9D54&0&90 
Base System Device PCI\VEN_8086&DEV_6FB0&SUBSYS_21EA103C&REV_01\3&103A9D54&0&A0 
Base System Device PCI\VEN_8086&DEV_6FB8&SUBSYS_00000000&REV_01\3&103A9D54&0&BC 
Base System Device PCI\VEN_8086&DEV_6FC0&SUBSYS_21EA103C&REV_01\3&103A9D54&0&F3 
Base System Device PCI\VEN_8086&DEV_6FF8&SUBSYS_21EA103C&REV_01\3&103A9D54&0&78 
Base System Device PCI\VEN_8086&DEV_6F1F&SUBSYS_21EA103C&REV_01\3&103A9D54&0&87 
Base System Device PCI\VEN_8086&DEV_6F27&SUBSYS_21EA103C&REV_01\3&11583659&0&27 
Performance Counters PCI\VEN_8086&DEV_6F37&SUBSYS_21EA103C&REV_01\3&103A9D54&0&5A 
Base System Device PCI\VEN_8086&DEV_6F81&SUBSYS_21EA103C&REV_01\3&103A9D54&0&58 
Base System Device PCI\VEN_8086&DEV_6FA8&SUBSYS_21EA103C&REV_01\3&103A9D54&0&98 
Base System Device PCI\VEN_8086&DEV_6FB1&SUBSYS_21EA103C&REV_01\3&103A9D54&0&A1 
Base System Device PCI\VEN_8086&DEV_6FB9&SUBSYS_00000000&REV_01\3&103A9D54&0&BD 
Base System Device PCI\VEN_8086&DEV_6FD0&SUBSYS_00000000&REV_01\3&103A9D54&0&B8 
Base System Device PCI\VEN_8086&DEV_6FF9&SUBSYS_21EA103C&REV_01\3&103A9D54&0&79 
Base System Device PCI\VEN_8086&DEV_6F20&SUBSYS_21EA103C&REV_01\3&11583659&0&20 
Base System Device PCI\VEN_8086&DEV_6F28&SUBSYS_21EA103C&REV_01\3&11583659&0&28 
Base System Device PCI\VEN_8086&DEV_6F68&SUBSYS_00000000&REV_01\3&103A9D54&0&B0 
Base System Device PCI\VEN_8086&DEV_6F88&SUBSYS_00000000&REV_01\3&103A9D54&0&F8 
Base System Device PCI\VEN_8086&DEV_6FAA&SUBSYS_21EA103C&REV_01\3&103A9D54&0&9A 
Base System Device PCI\VEN_8086&DEV_6FB2&SUBSYS_21EA103C&REV_01\3&103A9D54&0&A2 
Base System Device PCI\VEN_8086&DEV_6FBA&SUBSYS_00000000&REV_01\3&103A9D54&0&BE 
Base System Device PCI\VEN_8086&DEV_6FE0&SUBSYS_21EA103C&REV_01\3&103A9D54&0&60 
Base System Device PCI\VEN_8086&DEV_6FFC&SUBSYS_21EA103C&REV_01\3&103A9D54&0&7C
Base System Device PCI\VEN_8086&DEV_6F21&SUBSYS_21EA103C&REV_01\3&11583659&0&21 
Base System Device PCI\VEN_8086&DEV_6F29&SUBSYS_21EA103C&REV_01\3&11583659&0&29 
Base System Device PCI\VEN_8086&DEV_6F6E&SUBSYS_00000000&REV_01\3&103A9D54&0&B6 
Base System Device PCI\VEN_8086&DEV_6F8A&SUBSYS_00000000&REV_01\3&103A9D54&0&FA 
Base System Device PCI\VEN_8086&DEV_6FAB&SUBSYS_21EA103C&REV_01\3&103A9D54&0&9B 
Base System Device PCI\VEN_8086&DEV_6FB3&SUBSYS_21EA103C&REV_01\3&103A9D54&0&A3 
Base System Device PCI\VEN_8086&DEV_6FBB&SUBSYS_00000000&REV_01\3&103A9D54&0&BF 
Base System Device PCI\VEN_8086&DEV_6FE1&SUBSYS_21EA103C&REV_01\3&103A9D54&0&61 
Base System Device PCI\VEN_8086&DEV_6FFD&SUBSYS_21EA103C&REV_01\3&103A9D54&0&7D 
Base System Device PCI\VEN_8086&DEV_6F22&SUBSYS_21EA103C&REV_01\3&11583659&0&22 
Base System Device PCI\VEN_8086&DEV_6F2A&SUBSYS_21EA103C&REV_01\3&11583659&0&2A 
Base System Device PCI\VEN_8086&DEV_6F6F&SUBSYS_00000000&REV_01\3&103A9D54&0&B7 
Base System Device PCI\VEN_8086&DEV_6F98&SUBSYS_21EA103C&REV_01\3&103A9D54&0&F0 
Base System Device PCI\VEN_8086&DEV_6FAC&SUBSYS_21EA103C&REV_01\3&103A9D54&0&9C 
Base System Device PCI\VEN_8086&DEV_6FB4&SUBSYS_21EA103C&REV_01\3&103A9D54&0&A8
Base System Device PCI\VEN_8086&DEV_6FBC&SUBSYS_00000000&REV_01\3&103A9D54&0&A4 
Base System Device PCI\VEN_8086&DEV_6FE2&SUBSYS_21EA103C&REV_01\3&103A9D54&0&62 
Base System Device PCI\VEN_8086&DEV_6FFE&SUBSYS_21EA103C&REV_01\3&103A9D54&0&7E 
Base System Device PCI\VEN_8086&DEV_6F23&SUBSYS_21EA103C&REV_01\3&11583659&0&23 
System Interrupt Controller PCI\VEN_8086&DEV_6F2C&SUBSYS_21EA103C&REV_01\3&11583659&0&2C 
Base System Device PCI\VEN_8086&DEV_6F70&SUBSYS_21EA103C&REV_01\3&103A9D54&0&92 
Base System Device PCI\VEN_8086&DEV_6F99&SUBSYS_21EA103C&REV_01\3&103A9D54&0&F1 
Base System Device PCI\VEN_8086&DEV_6FAD&SUBSYS_21EA103C&REV_01\3&103A9D54&0&9D 
Base System Device PCI\VEN_8086&DEV_6FB5&SUBSYS_21EA103C&REV_01\3&103A9D54&0&A9 
Base System Device PCI\VEN_8086&DEV_6FBD&SUBSYS_00000000&REV_01\3&103A9D54&0&A5 
Base System Device PCI\VEN_8086&DEV_6FE3&SUBSYS_21EA103C&REV_01\3&103A9D54&0&63 
Base System Device PCI\VEN_8086&DEV_6F24&SUBSYS_21EA103C&REV_01\3&11583659&0&24 
Performance Counters PCI\VEN_8086&DEV_6F30&SUBSYS_21EA103C&REV_01\3&103A9D54&0&91
Base System Device PCI\VEN_8086&DEV_6F71&SUBSYS_21EA103C&REV_01\3&103A9D54&0&99 
Base System Device PCI\VEN_8086&DEV_6F9A&SUBSYS_21EA103C&REV_01\3&103A9D54&0&F2 
Base System Device PCI\VEN_8086&DEV_6FAE&SUBSYS_00000000&REV_01\3&103A9D54&0&9E 
Base System Device PCI\VEN_8086&DEV_6FB6&SUBSYS_21EA103C&REV_01\3&103A9D54&0&AA 
Base System Device PCI\VEN_8086&DEV_6FBE&SUBSYS_00000000&REV_01\3&103A9D54&0&A6
Base System Device PCI\VEN_8086&DEV_6FE4&SUBSYS_21EA103C&REV_01\3&103A9D54&0&64 

I've found that it was missing proper drivers for Inter chipset C610:

https://downloadcenter.intel.com/download/25731/Intel-Server-Chipset-Driver-for-Windows-?product=98915

After installation of this driver the errors went away.

Has anyoune had similiar issue? I wonder if it was only missing this driver or maybe it's something else?

I'm looking forward to hearing from you (any comments appreciated).

Best regards,

melelhov88

ProLiant DL380 Gen8 12G controller

$
0
0

Good day all, 

Do you know if a DL380 and DL360 GEN8 server can run 12G drives (12G speed as well) 
I am aware of the need of a 12G PCI controller. (698529-B21)

This is from HPE product Bulletin; NOTE: All 12G SAS Hard drives only operate at 6G speeds in the DL380pGen8.

I am looking forward to your respones on this matter. 

 

ILO show memory degarded

$
0
0

Hi,

 

During status check, found  server has a yellow warning light indication. Login to ILO and found the memory was degraded. 

DL380 G10 can not install WS2016

$
0
0

Hi all,

I got trouble with installation Window server 2016 on DL380 G10 server.

I was try to install ws2016 with iLO5 Remote Console .NET and to deploy it by F10 Intelligent Provisioning with HPE WS2016 ISO file as a virtual DVD ... the ISO file is OK, I tested it with other server.

In Intelligent Provisioning ... I choose Express OS Install. Then I enter installation parameters for os ws2016, then choose Launch Now in Job Configuration Viewer. But the StatusCodeError: 500 - undefined message will appear ...

And that´s all.

 

Thank you ...

ILO show memory degarded

Viewing all 10362 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>