- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Proliant DL 380 G3 On start up: processor 1: 0...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2011 05:58 PM
02-09-2011 05:58 PM
Proliant DL 380 G3 On start up: processor 1: 000 MHz...
Processor 1 Initialized at 000 MHz/533 MHz (512 Kbyte L2)
Processor 2 initialized at 3.06 GHz/533 MHz (512 Kbyte L2)
4096 MB Detected.
Now after it slowly initiates all 4096 MB Detected, the following message appears:
Advanced Memory protection Mode: Advanced ECC Support THEN IT JUST HANGS THERE!
This started after following the instructions on using the System Maintenance switch to clear the admin password. Please, I need help to get this server started, many cahritable organizations are relying on me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2011 06:24 PM
02-09-2011 06:24 PM
Re: Proliant DL 380 G3 On start up: processor 1: 000 MHz...
1 it does not detect a cpu CPU 1
2 most problematic, it seems that the server detects the 4096 MB memory in the system (top left hand of the screen), but then it wants to check the memory 1 Byte at the time. The top right screens starts with a counter that that increase every 1-2 with 1. I can only guess thats for the memory. From there, it just hangs. Need help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2011 10:06 PM
02-09-2011 10:06 PM
Re: Proliant DL 380 G3 On start up: processor 1: 000 MHz...
Did you move the switch back? Did you maybe accidentally move any of the other switches?
Maybe you can switch places on the CPUs? Does the problem follow the CPU?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2011 07:03 AM
02-10-2011 07:03 AM
Re: Proliant DL 380 G3 On start up: processor 1: 000 MHz...
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2011 07:40 AM
02-10-2011 07:40 AM
Re: Proliant DL 380 G3 On start up: processor 1: 000 MHz...
Maybe if you try to clear CMOS via the system maintenance switch too?
Firmware upgrade/reflash?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2011 08:33 AM
02-10-2011 08:33 AM
Re: Proliant DL 380 G3 On start up: processor 1: 000 MHz...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2013 09:05 PM
05-28-2013 09:05 PM
Re: Proliant DL 380 G3 On start up: processor 1: 000 MHz...
We had a similar issue. In our case a USB license dongle was causing the problem. Disconnect all peripherals before doing anything else.
- Tags:
- usb