ASR = Automatic Server Recovery
An ASR event is indicative of the host OS being in a hung state. When the hardware detects the host OS is hung, it will reboot the server. Please check the OS logs and server health logs to see if there were any errors logged
I recently picked up one of these also to learn on since I am studying to become a network admin. My school gives me access to windows server 2016 and 2019. I already know 2019 isn't gonna work, but I figured I might be able to get 2016 to work. I can install it fine but it is missing 2 drivers. How did you go about with your situation, I can find that disc they were talking about, but I don't see anything about installing drivers.
HPE doesn't test 3rd party component compatibility. The Samsung M.2 drive should be recognised. As far as warranty goes, the addition of 3rd party components should not void the warranty, but you may be asked to remove them while working with support to troubleshoot an issue.
Debian, like most community Linux distributions is enabled, but not tested. The MCP is available with several components in .deb format. https://downloads.linux.hpe.com/SDR/project/mcp/
Hi,
It appears to be a configuration issue.
Please ensure that you have correct controller and cabling in place.
Considering 25SFF backplace - i assume you have p420/p421/p430/p431/p830 which can handle 25SFF drives and expander-backplane is directly connected to controller.
We do not see any reason for connecting to onboard ?
Please refer cabling instruction in the
HP ProLiant DL380e Gen8 Server Maintenance and Service Guide(page 110)
http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03413095-10.pdf
also refer server quickspecs to know about the supported opions/controller
https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=c04128166
Regards,
Sudhir
Hello
Old thread but...
Do you succeed to boot on ES processor in your DL360gen 9 ?
Any advice would be appreciated !
Regards
Bertrand
I just bought a used ML150 G9 for learning more about servers. It booted fine with WS 2012. I tried to install WS 2016 from a USB stick but something went wrong. It ajust stops at this point and doesnt continue. Nothing happens when I push F9, F11 or F12. I have tried with and without both USB-stick and disks. No error messages, nothing.
Any ideas what I can do?
I have tried Clear NVRAM without success. Stops at exactly the same. I
I installed a new 2x X5675 processor in the DL160 G6 server. Updated BIOS and iLO to the latest version. The temperature of the processor shows 30 degrees and does not change. How to fix it?.
I installed a new 2x X5675 processor in the DL160 G6 server. Updated BIOS and iLO to the latest version. The temperature of the processor shows 30 degrees and does not change. How to fix it?.
I see that your BIOS is still on version v1.20. I reccomend to update everything possible.
If you still can enter the iLO. Update the iLO first and you also can upload the ROM through the iLO page. You can get the ROM file by downloaing the Windows update file, extract it on your workstation and point at that file from within your browser, in the iLO.
Maybe get it that far to install the older version of Windows Server and put of ver the latest HPE SPP. That will contain all the firmwares in your server.
Maybe you also want to update the IP, the Intelligent Provisioning. You can do that by booting from a DVD, when burning the Intelligent Provisioning ISO on that. If you get Remote Control at work throug iLO, you can attatch the ISO through there and let it boot from that ISO. After updating IP, it will support newer OS'es, like Windows Server 2016. For Gen9 servers, you need a v2.x IP, like v2.71.
All the latest software for your ML150 Gen9 can be found here.
Hi Jimmy,
Noted. Thank you for the advice.
I have error: FIRMWARE BUG – THE BIOS HAS CORRUPTED HW-PMU RESOURCES
(MSR 186 is 43003c).
Help me plzzz
Hi Floran,
Good Day. Check if BIOS is updated to the latest. If it is then perform a hardware diagnostic on the server through the Intelligent Provisioning. The errors you are seeing are possibly because of hardware errors or the firmware.
Redhat article:-
https://access.redhat.com/solutions/67599
Take the diagnostics report and the AHS log and log a case with HPE using the below portal:-
https://support.hpe.com/hpesc/home
Regards,
Bunsol
Please refer page 86-87 of the iLO 5 user guide for removal of running task in installation queue.
https://support.hpe.com/hpsc/doc/public/display?docId=a00039434en_us
Please use the "Intelligent Provisioning Recovery Media for Gen10" version 3.22 to bring Intelligent provisioning up to date.
https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_49c1286bcd954376a00d0484e8#tab3
Greetings.
Yes, as per the troubleshooting action performed looks like DIMM slot issue.
With reference to bootstrap processor (PROC 1), the Multiprocessor initialization protocol defines two classes of processors: the bootstrap processor (BSP) and the application processors (APs).
Following a power-up or RESET of an Multiprocessor system, system hardware dynamically selects first processors on the system bus as the bootstrap processor. Hence you have seen PROC1 error. However there is no option available to change the bootstrap processor from PROC 1 to PROC 2.
Hi ,
Please let know if this issue has been resolved
This will be helpful for everyone following this thread
Ronny
Thanks for you answer. Effectively, I 'can not boot with only # 2PROC. That was validated in the service guide. Pleasy help me with another question.
In the ILO overview or diagnosys, the values have not been updated after the many previous test.
That means, the size of the memory and the processor still shows the previous values (A: 2Gb, B: 2Gb, PROC # 1), even if they have more, or less than no memory or the processor has been changed to slot # 2.
Greetings.
We are still working with the product team, will write back to you once we have a clear update from the product team.
Appreciate you patience.
Thank you
Hi,
Good day,
I would suggest you to contact any local HPE vendor/Parnter to get the part.
and regarding using higher capacity drive:
Yes, you can. however its suggested not to use different capacity drive in the same array instead
create an additional array with the higher capacity drives.
Regards,
Sudhir
wrote: I have error: FIRMWARE BUG – THE BIOS HAS CORRUPTED HW-PMU RESOURCES
(MSR 186 is 43003c).Help me plzzz
This is a well documented error ProLiant server have with the Linux kernel. it really isn't a firmware bug. The server hardware is reserving a few of the performance counters. It is just an informative message and has no impact on server performance. In your case it just happens to be the last message you see on the screen.
You might try booting with 'nomodeset' to disbale KMS which can cause blank screens during boot