- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: recurring issues with varius dl380 g4 or g3
ProLiant Servers (ML,DL,SL)
1753342
Members
4940
Online
108792
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
тАО02-25-2011 12:04 PM
тАО02-25-2011 12:04 PM
recurring issues with varius dl380 g4 or g3
In the past two weeks, we have had three servers have issues.
1. dl380 G3 5i controller, Novell 5.1, disk 0 and 1 raid 1 (OS mirror) disk 2, 3 and 4 RAID 5 (apps). Q1529A tape drive. Drive 0 showed bad (red icon on drive), we replaced drive with good drive, tries to rebuild and fails (red icon on drive). Try another drive, same result. Replace controller, now drive four and zero has red error icon. system tries to boot but can't. Rebuilt server from scratch.
2. dl380 g4 5i controller, Windows 2003 server, disk 0 and 1 raid 1 (OS mirror) disk 2, 3 and 4 RAID 5(apps). Q1529A tape drive. Drive 0 showed bad, we replaced drive with good drive, tries to rebuild and fails (red icon on drive). Try another drive, same result. Replace controller and put back original drive 0, fail. Try a new drive zero, system is running.
3. dl380 G4 5i controller, Windows 2003 server, disk 0 and 1 raid 1 (OS mirror) disk 2, 3 and 4 RAID 5(apps). Q1529A tape drive. Drive 0 and 4 showed bad (red icon on drive), we replaced drive 4 with good drive, immediate BSOD. Reboot server, system can't find ntoskrnl.exe and hangs. Take out drive 0, replace with good drive, same issue.
So, we have multiple machines with similar if not identical configurations all dying on us in what seems to be the same way.
Our intentions with the 0 and 1 drive mirror was so that in case 0 or 1 goes bad, the machines could still boot. Well, in our case, if 0 dies, we are SOL. Are we mis-configuring our servers so that there is no disk redundancy? What is the best way to ensure if a drive goes bad (especially a boot drive) that we can still work? Am I experiencing bad drives or bad controllers?
Tests on all the bad drives and controllers, above, from the problem servers show that the equipment is ok (running on a test box w/SmartStart.)
Any ideas??
1. dl380 G3 5i controller, Novell 5.1, disk 0 and 1 raid 1 (OS mirror) disk 2, 3 and 4 RAID 5 (apps). Q1529A tape drive. Drive 0 showed bad (red icon on drive), we replaced drive with good drive, tries to rebuild and fails (red icon on drive). Try another drive, same result. Replace controller, now drive four and zero has red error icon. system tries to boot but can't. Rebuilt server from scratch.
2. dl380 g4 5i controller, Windows 2003 server, disk 0 and 1 raid 1 (OS mirror) disk 2, 3 and 4 RAID 5(apps). Q1529A tape drive. Drive 0 showed bad, we replaced drive with good drive, tries to rebuild and fails (red icon on drive). Try another drive, same result. Replace controller and put back original drive 0, fail. Try a new drive zero, system is running.
3. dl380 G4 5i controller, Windows 2003 server, disk 0 and 1 raid 1 (OS mirror) disk 2, 3 and 4 RAID 5(apps). Q1529A tape drive. Drive 0 and 4 showed bad (red icon on drive), we replaced drive 4 with good drive, immediate BSOD. Reboot server, system can't find ntoskrnl.exe and hangs. Take out drive 0, replace with good drive, same issue.
So, we have multiple machines with similar if not identical configurations all dying on us in what seems to be the same way.
Our intentions with the 0 and 1 drive mirror was so that in case 0 or 1 goes bad, the machines could still boot. Well, in our case, if 0 dies, we are SOL. Are we mis-configuring our servers so that there is no disk redundancy? What is the best way to ensure if a drive goes bad (especially a boot drive) that we can still work? Am I experiencing bad drives or bad controllers?
Tests on all the bad drives and controllers, above, from the problem servers show that the equipment is ok (running on a test box w/SmartStart.)
Any ideas??
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2011 12:45 AM
тАО03-05-2011 12:45 AM
Re: recurring issues with varius dl380 g4 or g3
Please state which RAID controller you are using. IIRC DL380 G3 and G4 use SCSI, please make sure all cables are attached properly by reseating them. Make sure your SCSI ID's are set correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2011 02:15 AM
тАО03-05-2011 02:15 AM
Re: recurring issues with varius dl380 g4 or g3
There was some issues with bad connectors the G3's.
However improber seating is the most common reason, also check the FW level, get it to latest.
When you have these multible disk failures.
Reseat the drives.
Re-enable the failed logical drives.
Note on improper seating:
It's a common mistake, to close the lever only. After closing the lever, you must push on the drive, to ensure its fully seatet.
Also in your case.
These are old machines, and running Novell.
Are you using the HW monitoring tools(Insight agents/HP SIM)?
If not you might have had disk failures for a long time.
BR
/jag
However improber seating is the most common reason, also check the FW level, get it to latest.
When you have these multible disk failures.
Reseat the drives.
Re-enable the failed logical drives.
Note on improper seating:
It's a common mistake, to close the lever only. After closing the lever, you must push on the drive, to ensure its fully seatet.
Also in your case.
These are old machines, and running Novell.
Are you using the HW monitoring tools(Insight agents/HP SIM)?
If not you might have had disk failures for a long time.
BR
/jag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2011 02:46 AM
тАО04-05-2011 02:46 AM
Re: recurring issues with varius dl380 g4 or g3
I would not rely solely on the lights on the drive for status. See what the array configuration software says (software running on an operating machine, not the firmware array setup utility.)
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