- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Identifying faulty disk on EVA4000
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-16-2009 01:57 PM
тАО07-16-2009 01:57 PM
The log points out almost every disk between 1 and 14 in the cabinet at random times when there is probably only one messing the communications up on that loop.
Right now the only solution I see is to ungroup and remove one disk at a time but it takes forever with leveling and all.
Another thing I have been wondering about; is the array protected during leveling or will a disk failure during leveling destroy the whole group?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2009 09:21 PM
тАО07-16-2009 09:21 PM
Re: Identifying faulty disk on EVA4000
there could be
a) media errors (block reallocation within the disk)
b) mechanical errors (servo, positioning)
c) port interface errors (loop failures)
d) SMART (prediction - spindles, arms, headers, platters)
When a controller puts FC loop in a failed state due to excessive port errors, the other controller also puts the same loop in a failed state to prevent the access to occur over the properly functioning loop.
Disk errors related to loop failures can impact other disks and controller operation. Failures affecting one port also affect other disks and can be detected and reported by any device ├в downstream├в from
the problem.
There is a special functionality in Webes/IRS/RSP - call-out/notification rules to the HP HW teams for the proactive disk replacement. This should be kept strict not to wait until the controller log shows the disk in a failed state and thus risk the double disk failure in the same Disk group/same RSS. Usualy during the failure the controller does the ungroup of the disk (migrate all its data to other disks in the disk group). Once the disk is ungrouped/data migrated, another disk failure will be only a 1 disk failure in the Disk group.
Yes there is the Disk group function of the disk protection to reserve the free virtual space for the automaticaly/manual addition to the disk group when needed in the emmergency situations.
Single disk protection means the capacity of 2 virtual spare drives, Double disk protection means the capacity of 4 virtual spare drives, so avoid to use NONE here in your production.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2009 09:49 PM
тАО07-16-2009 09:49 PM
Re: Identifying faulty disk on EVA4000
Is there an easy way to determine which disk it is or do I have to ungroup and remove one disk at a time until problems clear? This is the way I have had to do it before since almost every disk in the box generates errors right now because of garbage in the loop.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2009 11:26 PM
тАО07-16-2009 11:26 PM
Re: Identifying faulty disk on EVA4000
if there is an excessive number of port problems on the loop, HP support could be called to run the special loop test (FCLX).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2009 12:43 AM
тАО07-17-2009 12:43 AM
Solution1) The "missing data" events are always on the same loop?
2) Are there any disk giving "SCSI parity error?
If all disks give "missing data", on the same loop, and there are no "SCSI parity error" it's the I/O module.
Get the log checked by some with experience on HP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2009 04:43 AM
тАО07-17-2009 04:43 AM
Re: Identifying faulty disk on EVA4000
So I├В┬┤ll try to replace to cable tonight and we├В┬┤ll see.
/Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2009 11:09 AM
тАО07-17-2009 11:09 AM
Re: Identifying faulty disk on EVA4000
I changed the cable for the loop and no errors since.
Thanks a bunch for the help. Weekend saved!
/Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2009 11:10 AM
тАО07-17-2009 11:10 AM