Failed .srdata

[Mr.turbo750]

Does anyone have any ideas on how to fix the vv .srdata thats in a failed state?

[MammaGutt]

Generally a VV shouldn't be in a failed state unless you've lost more drives/capacity then what the RAID level and sparring is capable of handling.

Do you have any failed drives in the system?

[JohnMH]

Assuming that you have identified and fixed the underlying issue you could try:
Note it highly likely you have lost the data in the existing database so it would need to be recreated.

Stop the system reporter database with
cli% stopsr
Recreate the system reporter database with
cli% admithw srdata
Check the .srdata volume status with
cli% showvv
Start system reporter with
cli% startsr
Check the system reporter status with
cli% showsr

Failing that you may have to delete the volume and recreate as above, but before doing do that I'd speak to support.

[Mr.turbo750]

I had someone that decided to swap my several disk in my 3par for bad ones in theirs and currently being dealt with!

I tried what you said and did not work... Got any other ideas? I don't care if I loose the data on this vv, just trying to preserve the other VV's I have that are in normal condition.

IPTVDASHSAN2 cli% stopsr
Are you sure you want to unmount srdata volume?
select q=quit y=yes n=no: y
IPTVDASHSAN2 cli% admithw srdata
System Reporter data volume exists.
IPTVDASHSAN2 cli% showvv
----Rsvd(MB)---- - --(MB)--
Id Name Prov Type CopyOf BsId Rd ---Detailed_State---- Adm Snp Us r VSize
1 .srdata full base --- 1 RW needs_check,preserved 0 0 6144 0 61440
0 admin full base --- 0 RW normal 0 0 1024

IPTVDASHSAN2 cli% startsr
Are you sure you want to mount srdata volume?
select q=quit y=yes n=no: y
Cannot startsr, already started
IPTVDASHSAN2 cli% showsr
System Reporter volume not mounted

[JohnMH]

It looks like the volume is in a preserved state (needs_check,preserved) which means the backing LD's failed. Probably due to multiple disk failure with subsequent data written to the logging LD's. The rebuild process that should then kick off and relocate those chunklets back or to spares may also have been compromised if multiple drives we're failed or being actively swapped.

You could delete the volume and repeat the above (cli% admithw srdata) but it sounds like the system is in a bit of an indeterminate state which could effect sparing and other volumes going forward. So I would advise contacting support and getting it checked out properly before making more changes, they may also be able to recover the volume and any stray chunklets.

BTW someone with better breakfix / maintenance knowledge on here might be able to help, but support are much better placed to resolve and provide a thorough health check of the system.