Ok testinegrity/rebuild integrity gives me MSG_ERR_NOPARITY
I guess it points out that partitions where not created correctly, however it was done as a step of the pre installation task...
But I got another question then - during OVF deployment I set up 3 additional disks as user guide described, I set them into Think disks - could that be a problem?
angrydok
20 Posts
0
August 1st, 2013 05:00
endup rebulding avamar from scratch - hope would not see this error again
rpervan
266 Posts
0
August 1st, 2013 03:00
hello angrydok
for such issues there is procedure to perform test integrity on particular stripe or rebuild it as well .
From my part of view it will be better to contact EMC support and open case with them.
thanks, regards,
Rej
angrydok
20 Posts
0
August 1st, 2013 03:00
Since I am not a customer yet - I guess I do not have direct access to support.
Sound useless to rebuild as I just configured fresh install
What is to perform test integrity on particular stripe?
Thank you for you help!
angrydok
20 Posts
0
August 1st, 2013 04:00
cplist --full output:
cp.20130726051137 Fri Jul 26 09:11:37 2013 valid --- --- nodes 1/1 stripes 25
Date is different as VMware time was changed.
Where/how could I get STRIPE_ID? - got it from the error log stripes 6-E reported check of failed errors
angrydok
20 Posts
0
August 1st, 2013 04:00
Ok testinegrity/rebuild integrity gives me MSG_ERR_NOPARITY
I guess it points out that partitions where not created correctly, however it was done as a step of the pre installation task...
But I got another question then - during OVF deployment I set up 3 additional disks as user guide described, I set them into Think disks - could that be a problem?
rpervan
266 Posts
1
August 1st, 2013 04:00
Hello angrydok,
I understand.
well give a try with this one first .
# avmaint testintegrity --ava
then you could involve
# avmaint rebuildstripe --ava
Do you have validated CP ? Can you give us output from the cplist
# cplist --full
thanks, regards,
Rej
Nayak2010
50 Posts
1
August 1st, 2013 04:00
If you want to troubleshoot on your own, then I'd suggest looking for clues in the following files
/data01/cur/err.log
/data01/cur/gsan.log