- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: PIM logs boot error
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
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
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
тАО07-11-2005 02:33 AM
тАО07-11-2005 02:33 AM
I have an N-Class server which fails to boot. It starts to load the kernel and then fails. I've tired to boot the machine from both primary and alt boot disk, also tired the HP-UX install CD and still get the same error.
The machine gets to
alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x7f9ab000.
and then crashes.
In the SL logs I get errors
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 1A
PROBLEM DETAIL: 3 = function failure
CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 34 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 03
0x70003023821A6343 00000000 00070200 type 14 = Problem Detail
0x58003823821A6343 00006804 0F002413 type 11 = Timestamp 05/15/2004 00:36:19
Type CR for next entry, - CR for previous entry, Q CR to quit.
I've attached the PIM logs and the SL logs to this postings. Could anybody help figure out what part of the server has the problem.
Many Thanks
Michael
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 03:11 AM
тАО07-11-2005 03:11 AM
Re: PIM logs boot error
To my remotely familiar to the context eye, this looks like a cpu board problem but again take my word with a lot of salt, not just a grain. :)
Good luck
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 03:13 AM
тАО07-11-2005 03:13 AM
Re: PIM logs boot error
http://www2.itrc.hp.com/service/cki/search.do?category=c0&mode=text&searchString=0x7f9ab000&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty&search.x=22&search.y=11
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 03:16 AM
тАО07-11-2005 03:16 AM
Re: PIM logs boot error
This seems to be a hardware failure case. You need to call HP for rectification if you have a support contract.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 04:28 AM
тАО07-11-2005 04:28 AM
Re: PIM logs boot error
Log a hardware call with your local HP Response Centre
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 02:28 PM
тАО07-11-2005 02:28 PM
SolutionThanks for including the PIM dump.
Analysis of the HPMC points to the most likely cause of the problem to be in slot 6, path 0/2. Try removing this card and booting.
If you want the analysis information, I can provide it for you.
Good Luck - Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 05:04 PM
тАО07-11-2005 05:04 PM
Re: PIM logs boot error
what card is there in slot 3 path 0/12 .u can try removing the card in slot 3 and try to boot the server .
Regards,
Aliasgar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 05:57 PM
тАО07-11-2005 05:57 PM
Re: PIM logs boot error
You can remove all I/O cards then try the install CD boot to check which I/O card causes your HPMC. HPMC PIM itself should indicate which I/O is most culprit. You can log a HP support call for help.
Or you can run ODE mapper or IOTEST from the ISL prompt. ODE -> run mapper or run iotest.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 08:08 PM
тАО07-11-2005 08:08 PM
Re: PIM logs boot error
Cheers
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 08:09 PM
тАО07-11-2005 08:09 PM
Re: PIM logs boot error
This may not be related to your current problem but I have seen a very similar fault where the system craches after the 'alloc_pdc_pages' message. Mine was due to the console path not being correct. It looked very much like an I/O error and the fault is re-creatable - just change the console path in BCH and power cycle the system.
Perhaps on this occasion I'm barking up the wrong tree.
Lester