Disk Group Failure

[Johan Guldmyr]

I've read on several other occasions in this forum that 'trying' a later CV version is not a wise idea.

Also there are lots of 'licensing problems' seen when upgrading the CV from 6 to over 7, for people who have the license.

How long can you play with the EVA with the trial license? 60 days?

[SUBHAJIT KHANBARMAN_1]

Please find the procedure and attached are the scripts in order to collect logs,

1. Logon to the SAN Appliance and open "Command View EVA" .
2. Click on the Storage sub system (The Storage Cell).
3. The Storage sub system properties is now displayed on the right side. Click on "View Events" button.
4. Click on the "Controller Event Log"
5. Click on the "Get log file" to download the logs.
Repeat step 4 for â Controller Termination logsâ .

And procedure to Collect the Configuration Log or SSSU log

SSSU Logs: [From EVA LUN PERSPECTIVE]

SSSU (it is a utility) log uses to capture the configuration of the EVA.

The SSSU utility is attached to this post.

Please extract the content of the file to a folder and run this utility for the Eva's.

Use SCANV6 for command view 6 - read readme1st.txt for how to do, which is available when you unzip the content of the file.

[Jacky Wing]

As I said before, Not the whole EVA is test environment, the test environment was on 4 TB on the disk group which I deleted to enable faster leveling.

Upgrading CV or firmware is not an option right now. Also we are not sure that it will solve the issue.
In the logs I see many events of "A Volume has transitioned to the MISSING state." with a UUID that I cannot find.

The logs are very big to attach. I am attaching the one failure I always see.

I searched all the vdisks, the disks, the .... and I was not able to see anything failed.

I tried to log in to SSSU to check the available Vdisks, or the UUID but I was stuck at "SELECT SYSTEM". If I check the LS SYSTEM command it says: EVASYSTEMNAME available, so I do a "SELECT SYSTEM EVASYSTEMNAME" it says the system EVASYS... is not available.

[Johan Guldmyr]

You need to put in the name of your EVA.

You can see the name of it in CV.

[Uwe Zessin]

> the trial version of CV EVA9.3

Be careful with these "trial" versions. From what I have read, they make irrecoverable meta-data changes deep in the controller's NVRAM so that it is no longer managable by CV V6!

And XCS 6.000 has space management bugs. If the disk group runs out of free space, data corruption might result.

[D.Glass]

I had a similar error recently on an EVA5000. The CV EVA options to ungroup or remove the failed disk had not been available so I just pulled it from the array. I put a new disk in the same bay and grouped it, but the reconstruction kept failing because it could not find the disk for that bay even though CV EVA and Controller Configuration dump showed it was good. Eventually I ungrouped the new disk and removed it in the normal way, then put another new disk in the bay and grouped it. This time the reconstruction succeeded.

I suspect the reconstruction would have worked first time if I had put the first new disk through a normal Remove process in CV EVA after installing it, followed by re-insertion and grouping.

[WilliamSmith11]

Hi 

I have a similar problem, but in my case, I have two disk groups with the error mentioned before.

The IT personal take too much time to request for new disks to be replaced in the failed disk groups.

Both disk groups are at 100% of occupancy, 

Seven physical disks failed in total (divided into the two disk groups).

Failed disk drives have been replaced and are available to be grouped, but when trying to group the Pop-up messages (A hardware failure has occurred ...)  appear.
 
Also, both controllers had Soft Diagnostic Failure, which was corrected by entering to the fieldservice option and resetting the Master controller.

I reboot the two controllers, one at a time.
Going back to both disk groups can see the error persist.

I make a shutdown EVA4400 and disconnected power for all the enclosure and controller enclosure, 

I have waited for 10 minutes and reconnected everything and power on.

The error for the disk group persists and can not add the available new disks.

Some idea or clue to resolve this case

Regards 

[WilliamSmith11]