- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: L2000 boot failure
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
тАО10-25-2005 10:17 PM
тАО10-25-2005 10:17 PM
L2000 boot failure
I have L2000 machine with 2 CPU's. I tried to install Debian GNU/Linux on it(etch). Installation failed after disk repartitioning. I rebooted server and saw that boot stuff corectly, but system did not booted as disk has no OS on it. After another RS to get boot from CD, I cannot get past early system test:
PDH test 3158
***** EARLY BOOT VFP : SYSTEM ALERT *****
SYSTEM NAME: uninitialized
DATE: 01/01/1970 TIME: 23:02:11
ALERT LEVEL: 15 = Fatal hardware or configuration problem prevents operation
REASON FOR ALERT
SOURCE: 3 = PDH
SOURCE DETAIL: 2 = ROM SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF ON ON
LED State: Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.
0x000030F032001560 00000000 00000002 - type 0 = Data Field Unused
0x580038F032001560 00004600 0117020B - type 11 = Timestamp 01/01/1970 23:02:11
How to get in to boot admin console?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 01:12 AM
тАО10-26-2005 01:12 AM
Re: L2000 boot failure
The early boot vfp can be acknowledged and may be possible to continue generally. did you try to acknowledge? check GSP logs (sl), for more details. Is the Debian Linux supported on PA-RISC? If your system cannot reach boot admin (PDC) There may be hardware fault(coincedence), call HP support.
Regds
TT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 02:04 AM
тАО10-26-2005 02:04 AM
Re: L2000 boot failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 02:50 AM
тАО10-26-2005 02:50 AM
Re: L2000 boot failure
For more info. This machine was ok before installing linux. It failed after I did rebooted with not finished installation. It does not boot to anything. I think it does not finish so called PDC (Processor Dependent Code) thing. One interesting detail: one cpu was showed ok, second one as not configured(not used). After couple of reboots, CPU0 showed as installed but NOT CONFIGURED in SL logs. After another reboot everything went back. Somehow I feel that I need to reset something or stuff like that. But not sure where to look at. Does L2000 needs something on disk to get to BOOT ADMIN?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 05:30 PM
тАО10-26-2005 05:30 PM
Re: L2000 boot failure
The PDC (so called boot admin) is purely from firmware codes. Without any disk you should reach there. If not then there could be a hardware problem. As per your last post, could be CPU problem too. You may install a known good processor at cpu-0 slot and remove all other processors. (remember to disconnect the power & use autistatic mat/wrap). I don't think Linux installation caused anything, may be a coincedence.
Regds
TT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2005 03:37 AM
тАО11-01-2005 03:37 AM
Re: L2000 boot failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2005 05:21 AM
тАО11-01-2005 05:21 AM
Re: L2000 boot failure
As far as the compatibility is concerned , this server is seems to be supported by Debian GNU/Linux
for respective kernel versions.
Take a look at this and ensure it matches with your version of Debian GNU/Linux kernel.
http://www.pateam.org/list.html
http://www.debian.org/releases/sarge/
The error show that there is a problem with PDH ROM which may have been caused on account of the previous configuration problem.
As per the system firmware , there would be test sequences running on the system critical components during POST.
The system is stopping at the PDH test 3158 , but it is not succeeding because of the PDH ROM problem.
I am wondering about the CPU stuff. Did you see any other events/alerts from SL logs other than the one you posted here? There has to be more entries in the SL for events/alerts happening before and after this alert.
What is current status of the CPUs?
I would suggest to shutdown the server i,e complete power-off ( remove all power cable ) and start it.
Check if you get to BCH.
If not , shut it down again completly and remove the disk on which you tried to install linux.
Check again if you could get further.