- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Proliant ML350 G3 failure
ProLiant Servers - Netservers
1753757
Members
4929
Online
108799
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
Discussions
Discussions
Forums
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
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
тАО06-07-2005 06:26 PM
тАО06-07-2005 06:26 PM
Proliant ML350 G3 failure
Hello everybody,
I have an Proliant ML350 G3 (Xeon 3Ghz, 641 Raid, 4x72 GB disks (3 in RAID 5 + 1 spare).
After th einstalation of OS (Netware 4.11) the server worked OK for a couple of days. On emorning the server was found hanged with the "internal health status" LED off (not green - OK, yellow -warning or red- failure ) but completely OFF. The server could not be restarted using the power button , only plugging off the power sources (both of them) helped. Everything was OK for another couple of days, then th esimilar situation happened (found in the morning hanged, internal health status completely off). This time the server won't boot up at all, pressing the power button results in power sources fans starting but main fan remain still, the LED's on the front are showing Power - green, External Health - green, Internal Health - off ?! and on the motherboard we have as follows:
- a red led (NB ALERT)
- a amber led (OVERTEMP)
- three out of for DIMM led's amber and one off ? (despite we have only 2 DIMMS)
Work around:
- changed processor with a known good one - same no boot
- changed Dimms - same
- completely removed DIMM's - same situation
- removing 641 RAID card - same
- removing power connector for the cage backplane , CD, Floppy - same
- exchanging power supplies - same
We are now running out of solutions, it remains only the mainboard to be suspected. Before claiming an exchange one at HP I/m wondering if there are other solution to try ?
thanks
I have an Proliant ML350 G3 (Xeon 3Ghz, 641 Raid, 4x72 GB disks (3 in RAID 5 + 1 spare).
After th einstalation of OS (Netware 4.11) the server worked OK for a couple of days. On emorning the server was found hanged with the "internal health status" LED off (not green - OK, yellow -warning or red- failure ) but completely OFF. The server could not be restarted using the power button , only plugging off the power sources (both of them) helped. Everything was OK for another couple of days, then th esimilar situation happened (found in the morning hanged, internal health status completely off). This time the server won't boot up at all, pressing the power button results in power sources fans starting but main fan remain still, the LED's on the front are showing Power - green, External Health - green, Internal Health - off ?! and on the motherboard we have as follows:
- a red led (NB ALERT)
- a amber led (OVERTEMP)
- three out of for DIMM led's amber and one off ? (despite we have only 2 DIMMS)
Work around:
- changed processor with a known good one - same no boot
- changed Dimms - same
- completely removed DIMM's - same situation
- removing 641 RAID card - same
- removing power connector for the cage backplane , CD, Floppy - same
- exchanging power supplies - same
We are now running out of solutions, it remains only the mainboard to be suspected. Before claiming an exchange one at HP I/m wondering if there are other solution to try ?
thanks
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 06:25 AM
тАО06-09-2005 06:25 AM
Re: Proliant ML350 G3 failure
Disconnect every IDE or SCSI cables from System Board, no FDD no CD Drives, minimum Memory one stick original, no additional Cards, single CPU, all Jumpers if exist should be verified for clock and system Settings, enable Switch #6 at System Maintenance box and power up, reset all power connectors to System board, power up if problem exist make attempt with different CPU, PPM or memory, if problem still exist say good by to System board.
http://h20000.www2.hp.com/bc/docs/support/UCR/SupportManual/TPM_316336-002/TPM_316336-002.pdf
http://h20000.www2.hp.com/bc/docs/support/UCR/SupportManual/TPM_316336-002/TPM_316336-002.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 06:27 AM
тАО06-09-2005 06:27 AM
Re: Proliant ML350 G3 failure
and just in case if it works run
http://h18023.www1.hp.com/support/files/server/us/romtabl.html
http://h18023.www1.hp.com/support/files/server/us/romtabl.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 08:04 PM
тАО06-09-2005 08:04 PM
Re: Proliant ML350 G3 failure
Hi,
Case closed finally, the problem was the faulty PSU backplane board (292235-001) that behaves erratically and messed up totally the mainboard.
Thanks anyway for the answer :)
Case closed finally, the problem was the faulty PSU backplane board (292235-001) that behaves erratically and messed up totally the mainboard.
Thanks anyway for the answer :)
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP