- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Logged Drive Errors in ADU-Log on ML350G4 with Sma...
ProLiant Servers (ML,DL,SL)
1752793
Members
6016
Online
108789
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
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
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
11-04-2010 04:53 AM
11-04-2010 04:53 AM
Logged Drive Errors in ADU-Log on ML350G4 with SmartArray 641
Hi,
I had a strange Issue on one Customer-System. Basically the System suddeltly slowed down to a crawl without any bigger Load on it and evantually it stopped responding at all (incl. Network-Access).
After a Hard Reboot I had a look at the System Logs and did not find many information about a possible reason except warnings from Exchange, that a write Operation to Disk took like 61 seconds.
I then generated an Array Diagnostics Report and tried to find whether there are faulty drives.
The Problem is, that I indeed see Entries in the Drive Error Logs from some Drives but can't interpret the Errors as they are given in Hex-Codes. Can someone help me out here ?
Strange is, that on the System Management Homepages no Read or Write Errors are reported on the physical Drives, so I'm wondering what is true here.
The Firmware / Drivers on the System are really old, but the System has been stable for a longer time (planning to Upgrade soon). I want to make sure, that there is no imminent Hard Drive Failure as this is a Windows SBS Server 2003.
I had a strange Issue on one Customer-System. Basically the System suddeltly slowed down to a crawl without any bigger Load on it and evantually it stopped responding at all (incl. Network-Access).
After a Hard Reboot I had a look at the System Logs and did not find many information about a possible reason except warnings from Exchange, that a write Operation to Disk took like 61 seconds.
I then generated an Array Diagnostics Report and tried to find whether there are faulty drives.
The Problem is, that I indeed see Entries in the Drive Error Logs from some Drives but can't interpret the Errors as they are given in Hex-Codes. Can someone help me out here ?
Strange is, that on the System Management Homepages no Read or Write Errors are reported on the physical Drives, so I'm wondering what is true here.
The Firmware / Drivers on the System are really old, but the System has been stable for a longer time (planning to Upgrade soon). I want to make sure, that there is no imminent Hard Drive Failure as this is a Windows SBS Server 2003.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2010 07:47 AM
11-04-2010 07:47 AM
Re: Logged Drive Errors in ADU-Log on ML350G4 with SmartArray 641
Others will take a look in the report as well. The only thing I found and could explain such a crash would be:
PHYSICAL DRIVE IDENTIFICATION:
SCSI Port 1, Drive ID 0
Vendor Id: COMPAQ
Product Id: BF0368B269
Product Rev: HPB9
Vendor Specific: 3LQ2N3T1
Serial Number: 3LQ2N3T10000983019NB
......
Last Failure Reason: 0x07 (Drive timeout)
Consider upgrading the firmware. Sometimes hardly reproducible issues occur with older FW.
PHYSICAL DRIVE IDENTIFICATION:
SCSI Port 1, Drive ID 0
Vendor Id: COMPAQ
Product Id: BF0368B269
Product Rev: HPB9
Vendor Specific: 3LQ2N3T1
Serial Number: 3LQ2N3T10000983019NB
......
Last Failure Reason: 0x07 (Drive timeout)
Consider upgrading the firmware. Sometimes hardly reproducible issues occur with older FW.
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