EVA 3000 Disk Drives failed state

[Nicolas Saade2]

Hello;

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

[IBaltay]

Hi
did you also try the "good disks" in the "wrong bays" and vice versa pls?

[Nicolas Saade2]

Yes "good disks" were placed in the "wrong bays" and vice versa

[Rob Leadbeater]

Hi Nick,

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

[McCready]

All drives should power up to show their Green LED's - firmware is unlikely to be an issue.

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)

[Torsten.]

If this EVA is "new" and currently not used for data, you may consider to uninitialize it.

BTW, if you compare firmware versions, you must also compare the drive models.

Are all models the same?

Different models typically have different firmware.

[Nicolas Saade2]

Thank you all. It has not been resolved yet. But we arewaiting for disk replacements.

[DR M.JAVED K JADOON(PHD]

Just today I got same issue as was discussed in this forum. I have resolved successfully.
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