HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: L-Class takes quite long to boot !! is it norm...
HPE 9000 and HPE e3000 Servers
1827210
Members
2553
Online
109716
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-19-2001 12:21 AM
07-19-2001 12:21 AM
L-Class takes quite long to boot !! is it normal ?
I have a common problem on L-class servers. They take loads of time to boot. They take very long time in a state pdc_alloc_mem ...... What would this server be doing at this state and why does it take so long. I noticed that the larger the RAM the more wait time
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2001 12:53 AM
07-19-2001 12:53 AM
Re: L-Class takes quite long to boot !! is it normal ?
Correct, because of the testing the more hardware you have, the longer it takes to boot especially if you have plenty RAM...
There is a way to bypass some tests (RAM for example) to shorten the reboot time, I remembered on K class you would do this at IPL...
Unfortunately Im still on my IBM SP2s migrations at the moment and cannot access my HP doc ( there maybe a fast reboot option on L/N class), but thats the way to look for reducing reboot time
All the best
Victor
There is a way to bypass some tests (RAM for example) to shorten the reboot time, I remembered on K class you would do this at IPL...
Unfortunately Im still on my IBM SP2s migrations at the moment and cannot access my HP doc ( there maybe a fast reboot option on L/N class), but thats the way to look for reducing reboot time
All the best
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2001 11:19 PM
07-19-2001 11:19 PM
Re: L-Class takes quite long to boot !! is it normal ?
Stefan,
When the "alloc_pdc_pages : Relocating PDC from?" message appears is the task of PDC reallocation already done. Usually is the next step that the kernel initializes the IO tree. That may take a while, especially when you have a flaky SCSI or Fibre Channel connections.
Victors explanation about the memory part is just perfect. If you don't want the memory been tested you can switch fast boot on in the Boot Console Handler. That safes time during boot, but bad DIMMs are not identified and deconfigured.
When the "alloc_pdc_pages : Relocating PDC from?" message appears is the task of PDC reallocation already done. Usually is the next step that the kernel initializes the IO tree. That may take a while, especially when you have a flaky SCSI or Fibre Channel connections.
Victors explanation about the memory part is just perfect. If you don't want the memory been tested you can switch fast boot on in the Boot Console Handler. That safes time during boot, but bad DIMMs are not identified and deconfigured.
There is no good troubleshooting with bad data
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP