- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: EVA 3000 Disk Drives failed state
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-01-2008 11:18 PM
тАО10-01-2008 11:18 PM
EVA 3000 Disk Drives failed state
We are setting a new EVA 3000 in a test environment with only one drive enclosure and 8 disk drives of different capacities. The problem is that only 3 of the disks are recognized by the Command View, with their LEDs green. The other 5 have red LEDs, and command View Operational State shows them as failed or not mated. Unable to update their firmware as Code Load are not available.
Updated one controller to VCS 3.110 did not help, so we returned to VCS 3.028.
Specs:
EVA 3000, 2 controllers HSV100 VCS 3.028
Command View EVA v6.0 Build 193
Operational drives: 72GB 15K Firmware HP00 for one, and HP02 for 2 drives.
Failed Drives are all firmware HP03. 2x72GB are 15k, 3x 146GB are 10k.
Moveing the disk drives from one bay to the another has same results.
Does anyone has any suggestions, or recommendation.
Thank you
Nick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2008 11:55 PM
тАО10-01-2008 11:55 PM
Re: EVA 3000 Disk Drives failed state
did you also try the "good disks" in the "wrong bays" and vice versa pls?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2008 12:00 AM
тАО10-02-2008 12:00 AM
Re: EVA 3000 Disk Drives failed state
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2008 12:01 AM
тАО10-02-2008 12:01 AM
Re: EVA 3000 Disk Drives failed state
Where did this "new" EVA3000 come from ?
I'll guess that disks are actually bad.
Even if the firmware on the drives is too new, you should just get a warning in Command View to that effect.
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2008 04:53 AM
тАО10-02-2008 04:53 AM
Re: EVA 3000 Disk Drives failed state
Since you appear to be new to the EVA, but wanting a not-new setup (the EVA 3000 has not been sold as new for a while) I would highly recommend:
- getting at least 8 drives of the same capacity (better space usage for the reserved protection alogorithm)
- Setting "double" protection (reserves space so the EVA can self heal in case drives fail)
- once you get those working drives in , upgrade to the latest controller and drive firmware on all controllers
- running an program that generates lots of I/O to give the drives you have a workout
- Never use RAID 0 (any drive failure will cause data loss)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2008 05:44 AM
тАО10-02-2008 05:44 AM
Re: EVA 3000 Disk Drives failed state
BTW, if you compare firmware versions, you must also compare the drive models.
Are all models the same?
Different models typically have different firmware.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2008 03:30 AM
тАО10-14-2008 03:30 AM
Re: EVA 3000 Disk Drives failed state
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2009 12:44 AM
тАО09-01-2009 12:44 AM
Re: EVA 3000 Disk Drives failed state
All drives powered up. I got 8 drives of the same capacity with "double" protection to reserve space so the EVA can self heal in case drives fail. Upgraded to the latest controller and drive firmware on all controllers.
Thanks
DRJJ