ProLiant Servers (ML,DL,SL)
1820641 Members
1750 Online
109626 Solutions
New Discussion

PROLIANT ML350 LENTO A PARTIRE PRIMA DEL S.O.

 
GiancarloBerni
Visitor

PROLIANT ML350 LENTO A PARTIRE PRIMA DEL S.O.

Buongirono a tutti, qualcheduno può darmi un cosiglio  per la lentessa all'avvio del SERVER Proliant ML350 Gen 10.

Prima che si avvii il S.O. WIndows Server 2019 dal momento dell'accensione passano circa  55 minuti, da un momento all'altro ha incominciato a dare questa anomalia, prima di questa situazione la macchina partiva nell'arco di 3/4 min. Sembra che faccia dei controlli il BIOS perchè i dischi non stanno ancora lavorando, non gira la rotellina dei dischi RAID 5 gestiti dall'Array  P408i-a SR Gen10.

Per cortesia qualche consiglio.

Google Translated:

PROLIANT ML350 SLOW TO START BEFORE O.S.
Good morning everyone, can anyone give me some advice on the slowdown when starting the Proliant ML350 Gen 10 SERVER.

Before the OS starts. WIndows Server 2019 took about 55 minutes from the moment it was turned on, from one moment to the next it started to give this anomaly, before this situation the machine started within 3/4 minutes. It seems that the BIOS is doing some checks because the disks are not yet working, it does not turn the wheel of the RAID 5 disks managed by the P408i-a SR Gen10 Array.

Some advice please.

6 REPLIES 6
support_s
System Recommended

Query: PROLIANT ML350 LENTO A PARTIRE PRIMA DEL S.O. - Prolaint server - ML350 Gen 10

System recommended content:

1. ProLiant ML350 Gen10 Server - Server automatically reboots on POST screen with all the front panel LEDs flashing simultaneously

2. Gen10/Gen10 Plus SPP 2023.09.00.00 Server Support Guide

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

GiancarloBerni
Visitor

Rif.: Query: PROLIANT ML350 LENTO A PARTIRE PRIMA DEL S.O. - Prolaint server - ML350 Gen 1

Non è la nostra situazione. La macchina funziona perfettamente, impiega 55 minuti prima di avviarsi, non si evidenziano degli errori e non avviene nessun reboot automatico.

Grazie

Google Translated: 

That's not our situation. The machine works perfectly, it takes 55 minutes to start, no errors are highlighted and no automatic reboot occurs.

Thank you

TVVJ
HPE Pro

Rif.: Query: PROLIANT ML350 LENTO A PARTIRE PRIMA DEL S.O. - Prolaint server - ML350 Gen 1

Hello,

You may restore default manufacturing settings on the server and see if it helps. To do so, you may perform the following:

  • Power off the server and remove the power cable from the power supplies.
  • Remove the server's access panel and locate the system maintenance switch on the system board. You may refer to item number 22 on page 15, diagram titled "System board components" on the HPE ProLiant ML350 Gen10 Server's User Guide.
  • Once located, set system maintenance switch position 6 (S6) to on. Replace the server's panel, connect the power cable to the power supplies and power on the server.
  • Once a message indicating that once of the system maintenance switch is in 'On' position and needs to be turned off is displayed, then power of the server, remove the power cable and then server's access, reverse that switch's position to the default 'Off' position and replace the access panel.
  • Once completed power on the server after connecting the power cable.

If the issue is not resolved, then reduce the server to base configuration.

  • To do so, remove all expansion cards and any installed thrid party components.
  • Remove the cables connecting the hard drives to the system boar.
  • Install only one memory module for each installed processor and the power on the server.
  • If the issue is resolved, then add one component at a time to isolate the issue.

Regards,



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[All opinions expressed here are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Sunitha_Mod
Moderator

Re: PROLIANT ML350 LENTO A PARTIRE PRIMA DEL S.O.

Hello @GiancarloBerni,

Let us know if you were able to resolve the issue.

If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.



Thanks,
Sunitha G
I'm an HPE employee.
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
GiancarloBerni
Visitor

Re: PROLIANT ML350 LENTO A PARTIRE PRIMA DEL S.O.

Grazie 1000 dei consigli, agire sull'hardware per scoprire quale eventuale componente piò dare problemi era un idea che mi era venuta

L'intervento consigliato non è un intervento semplice da effettuare,, sono obbligato a pianificare e il cliente non è disposto a far star fermo il personale, non avendo poi neanche la certezza che possa essere un problema su qualche componente, sono ancora più frenato.

Esiste qualche software tipo SMART Update Manager che verifichi l'hardware installato e dia delle indicazioni sul corretto funzionamento ?

Grazie

Google translated: 

Thank you very much for the advice, acting on the hardware to find out which component could cause problems was an idea that came to me

The recommended intervention is not an easy intervention to carry out, I am forced to plan and the customer is not willing to let the staff stand still, not even having the certainty that there could be a problem with some component, I am even more held back.

Is there any software like SMART Update Manager that checks the installed hardware and gives indications on correct functioning?

Thank you

Vinky_99
Esteemed Contributor

Re: PROLIANT ML350 LENTO A PARTIRE PRIMA DEL S.O.

@GiancarloBerni 

Good day!

A significant increase in the startup time of your ProLiant ML350 Gen10 server could be attributed to several factors, and troubleshooting the issue requires a systematic approach. Here are some steps you can take to identify and resolve the slowdown:

>> Ensure that all hardware components, including hard drives, memory modules, and expansion cards, are securely connected. Reseat the RAID controller and associated cables.

>> Access the BIOS/UEFI settings during the boot process and review the configuration. Check for any changes made to the BIOS settings recently that might have caused the slowdown.Reset the BIOS settings to default and see if the issue persists.

>> Ensure that the server's firmware, including BIOS, RAID controller, and other components, is up-to-date. Manufacturers often release firmware updates to address performance and compatibility issues.

>> Visit the official HPE website to download and apply the latest firmware updates for your server model.

>> Access the RAID controller configuration utility during the boot process and check for any issues or warnings related to the RAID array. Verify that the RAID array is in optimal condition and there are no failed or degraded disks.

>> Check the RAID controller settings for any misconfigurations.

>> Use diagnostic tools provided by HPE to perform hardware tests and identify any potential issues with the server components.HPE Insight Diagnostics is a tool that can help in diagnosing hardware problems.

>> Review the system event logs in Windows Server 2019 for any error messages or warnings that occurred during the startup process. Look for any patterns or specific error codes that can provide clues about the root cause.

>> Boot the server from a different bootable media (such as a live CD or USB) to see if the issue persists. This can help determine if the problem is related to the operating system.

>> If the issue persists after performing the above steps, it's advisable to contact HPE support for assistance. Remember to back up important data before making any significant changes to the system configuration.

Hope this helps! Let me know 

These are my opinions so use it at your own risk.