DL380 Gen10 部分内存无法识别(map out error)。更新BIOS,交叉内存和CPU测试, 始终指向相同槽位 map out error。
有遇到类似现象的盆友,请指教。
Part of the memory of DL380 Gen10 cannot be recognized (map out error). Update BIOS, cross memory and CPU test, always point to the same slot map out error. Any friends who have encountered similar phenomena, please advise.
Part of the memory of DL380 Gen10 cannot be recognized (map out error), cross memory and CPU tests,
Re: DL 360 G6 DUAL X5675 / Booting with one but not with 2 cpus inside
Hello,
As per sharing information, suspecting an issue with the memory configuration.
If you are using two processors then you have to install memory accordingly.
Please follow the below memory configuration guide.
HPE ProLiant DL360 G6 Server - Configuring Memory
https://support.hpe.com/hpesc/public/docDisplay?docId=c01761995&docLocale=en_US
Share the below information, if the issue still persists.
1. Share POST error message, if it is there.
2. Front LED indication.
https://support.hpe.com/hpesc/public/docDisplay?docId=c01716841&docLocale=en_US
HP ProLiant DL360 G6 Server Maintenance and Service Guide ( follow the page no 74-75)
https://content.etilize.com/User-Manual/1013299190.pdf
If you feel this was helpful please click the KUDOS! thumb below!
Regards,
Re: Disable CPU cores from Windows
Hello,
First of all Windows 10 not supported with this server.
Follow the below link for disabling Processor Cores as well as a system reboot is required.
HP ProLiant DL380p Gen8 Server - Disabling Processor Cores
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03503454
If you feel this was helpful please click the KUDOS! thumb below!
Regards,
Hp Microserver gen 8 - System Power Fault Detected
Hello,
yesterday suddenly my HP MicroGen8 server did not start, flashing lights in red and in iLo i saw the error:
System Power Fault Detected (XR: 20 00 MID: FF F5 FE 01 FF FF FF 06 06 00 00 02 00 05 40 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00)
It tries to start, the fans work (PSU and power fan) buy stop.
I've tried to reinstall the BIOS from iLO with no success (I can install diferents versions od iLO but when I try to install a System ROM, the error is "The last firmware update attempt was not successful. Ready for the next update" I think to update BIOS first it has to be booted and this is why I can't update the BIOS. Anyway I don´t know it the error is related to BIOS.
System ROM version appears as "undefined", main and backup also "undefined"
Please, could anyone give me any idea on how to resolve it?
Thanks in advance
Re: Proliant DL580 G7 + nvidia gt710 = device with error code 43
Hello,
Windows 10 don't support this server DL580 G7.
Follow the below link for more information.
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c02279623
- Microsoft Windows 2008 R2.
- Microsoft Windows 2008 (32 bit and 64 bit)
- Microsoft Windows Server 2008 Standard Edition (32 bit and 64 bit)
- Microsoft Windows Server 2008 Enterprise Edition (32 bit and 64 bit)
I would suggest you install supported OS on this server.
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c02279623
If you feel this was helpful please click the KUDOS! thumb below!
Regards,
Re: Using a Tesla K80 in a Dl380 G8
Hello
Tesla K80 is not supported by this server.
Follow the DL380 Gen8 Quickspace for more information.
HP ProLiant DL380p Generation8 (Gen8) Quick space ( Follow page no 42)
https://h20195.www2.hpe.com/V2/Getdocument.aspx?docname=c04123238#
If you feel this was helpful please click the KUDOS! thumb below!
Regards,
Re: Drive missing & Failed after firware upgrade
Hi Sanjeev,
Many thanks for your reply.
Below are some of the logs i could find under Event Viewer
Events under Event Viewer: (Event Viewer)
Error
Smarty Array Events
A drive failure notification has been received for the SAS physical drive located in bay 7. This drive can be found in box 0 which is connected to port 2I of the array controller P408i-a SR Gen10 [Embedded]. The failure reason received from the HPE Smart Array firmware is: HOT_PLUG_START_UNIT_FAILED.
Smart Array Events
A drive failure notification has been received for the SAS physical drive located in bay 7. This drive can be found in box 0 which is connected to port 2I of the array controller P408i-a SR Gen10 [Embedded]. The failure reason received from the HPE Smart Array firmware is: REMOVED_IN_HOT_PLUG.
Smart Array Events
A drive failure notification has been received for the SAS physical drive located in bay 7. This drive can be found in box 0 which is connected to port 2I of the array controller P408i-a SR Gen10 [Embedded]. The failure reason received from the HPE Smart Array firmware is: REMOVED_IN_HOT_PLUG.
Warnings:
FilterManager
File System Filter 'Datascrn' (Version 6.3, 2013-08-22T12:39:35.000000000Z) failed to attach to volume '\Device\HarddiskVolume5'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor
Smart Array Events
The event information received from array controller P408i-a SR Gen10 [Embedded] was of an unknown or unrecognized class.
An excerpt of the controller message is as follows: D005 (current:0/threshold:0/max:0): Could not read temperature.
Smart Array Events
The event information received from array controller P408i-a SR Gen10 [Embedded] was of an unknown or unrecognized class.
An excerpt of the controller message is as follows: GB event, 0x0 GB is initializing.
Is there any indication we can find from this as to why the hard disk would not be recognised?
Looking forward to your reply, many thanks.
Re: Drive missing & Failed after firware upgrade
Hello,
I would suggest you have a proper case be logged with HPE, and share the appropriate logs for further analysis.
Because one of the hard disk required replacement.
If you feel this was helpful please click the KUDOS! thumb below!
Regards,
Re: DL380p Gen8 + HP StorageWorks 82Q 8Gb PCI-e Dual Port FC HBA = ILO Fan speed
Hello Team,
please update the latest SPP. https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Regards,
Naresh Sharma
Re: SFP compatibility with mikrotik
Hello,
As per your query, i cannot confirm whether this 3rd party router is supported/compatible or not, since we dont have any supported docs.
Below is the quick specification fort the 530FLR
https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=c04111479
Regards,
Vijay
Re: Drive missing & Failed after firware upgrade
Hi Sanjeev,
Thank you for your reply, just to clarify, are you suggesting the drive might be failed and needs replacement?
Thanks.
Re: Proliant ML10 gen9 BSOD Stop Code error WHEA UNCORRECTABLE ERROR
Hello,
This is a very old case 5345227882, which was logged in March 2020.
I think you have to follow the HPE tech support engineer suggestion.
What is the current issue or currently server has BSOD, share the complete BSOD error message for further investigation.
Make sure the server should be updated with the latest bios and firmware.
If you feel this was helpful please click the KUDOS! thumb below!
Regards,
Re: iLO firmware update stays at 1% complete and does not finish
Hello,
Good day,
We have latest ILO firmware version 2.77(17 Dec 2020) . Please try below steps.
shut down the server completly and power drain by removing power cord.
then make sure BIOS is latest then try latest ILO version.
Re: Microserver Gen10 Plus - E208i-p controller not detected in SSA
Hello
Kindly refer the following customer advisory and use the USB Boot: Smart Storage Administrator option to execute the correct SSA utility
https://support.hpe.com/hpesc/public/docDisplay?docId=a00097770en_us&docLocale=en_US
If the issue persists , kindly go ahead and log a support case with HPE so that the respective team will troubleshoot the issue further .
Re: DL380 G7 UID Light turns on by itself
Hello,
The main idea behind this UID indicator is to help you to physically identify a server in your data center (in a rack or in your datacentre even).
When you logon to the iLO remote management port of the ProLiant server, this UID will blink on/off i.e.
The Unit Identification Light (UID): The UID helps you identify and locate a system, especially in high-density rack environments. Additionally, the UID is used to indicate that a critical operation is underway on the host
The following circumstances cause the UID to blink:
Remote Console is currently active.
Upgrade of iLO Firmware is in progress.
The UID continues to blink until the circumstances causing it to blink subside. The UID reverts to the current state when the cause of the blinking is gone.
Turn Unit ID On
Clicking this button sets the current state of the UID On. However, blinking the UID overrides this state until the cause has subsided.
The UID current state can also be toggled by pressing the physical button on the front of your system (or on the back, if supported). The UID is blue when lit.
Turn Unit ID Off
Clicking this button sets the current state of the UID Off. However, blinking the UID overrides this state until the cause has subsided.
The UID current state can also be toggled by pressing the physical button on the front of your system (or on the back, if supported). The UID has no color when it is off.
If you feel this was helpful please click the KUDOS! thumb below!
Regards,
Re: DL 360 G6 DUAL X5675 / Booting with one but not with 2 cpus inside
Ok, so i checked the said things again.
I tried starting the server with 2 CPUs installed and 1x4GB RDIM DR for each CPU. Still doesnt start. The Server doesnt show anything on the front LED indicator exept Power Supply error, but thats because i have just one plugged in at the moment.
The server also doesnt show any errors on the screen, the screen doesnt even get any output.
The only thing that the server does is spin the fans, they get faster and faster and faster, then they slow down, then they get faster again. Thats the only thing the server does. Nothing blinks or indicates any error.
Do i need to enable Advanced ECC anywhere? I havent found anything. Also, if i am right, i need to install my RAM A-I in the slots. Dont know if i am right though.
Re: SAS HDD для ProLiant DL160 Gen9
Hello EvrazTekhnika ,
Please find the below supported features for H240 Controller
Standard Features
- Storage interface (SAS/SATA)
o 8 physical links across 2 x4 internal ports
o 12Gb/s SAS, 6Gb/s SATA technology
o Mix-and-match SAS and SATA drives to the same controller
o Support for SAS tape drives, SAS tape autoloaders and SAS tape libraries
- PCI Express Gen3 x8 link
- RAID 0, 1, 5, 10
- Simple RAID or HBA mode
- Legacy and UEFI boot operation
- Up to 200 physical drives
- Up to 64 logical drives
- HPE Secure Encryption (optional license)
- Seamless upgrades to other HPE Smart Array P-series controllers
- PCI Express standard plug-in card o Dimensions: 6.6 x 2.7 x 0.6 in (16.8 x 6.86 x 1.6 cm)
Reference: https://h20195.www2.hpe.com/v2/GetDocument.aspx?docname=c04346303
Also the part no. 861590-B21 corresponds to the spare part no. 861607-001 which shows for use with Gen8/Gen9 or newer:
861607-001
8TB SAS hard drive - 12Gb/s interface, 7,200 RPM, 3.5-inch large form factor (LFF), smart carrier (SC) - For use with Gen8/Gen9 or newer
Also please find the below quick specs for DL160 Gen9 server representing the list of compatible parts to be used with the server:
https://h20195.www2.hpe.com/V2/Getdocument.aspx?docname=c04375607
Disclaimer : Data integrity is customer responsibility. HPE recommends to have data backup frequently and before performing any activity so that it can be restored during disaster recovery. Also it’s customer’s responsibility to keep a backup of any licenses on the system board.
Thanks
Re: Connection with iLO cannot be established
Thanks,
for me it's work. After reset need to wait 2-5 minutes.
Re: ML310 G8 V2 - Unable to update Intelligent Provisioning. iLO and IP displays different versions.
Hello,
Please clear NVRAM on system using maintenance switch and check status
if same issue then capture a screenshot of version information from IP and ILO as well.
Regards
Re: HP Proliant DL380 G7 ILO 3 Firmware Version Upgrade from 1.16 to 1.88
Get the *.exe file, rename to *.zip and extract the *.bin file.
Use the *.bin file to update from the web interface.