MSA Storage

HPE P2000 G3 MSA SAS - Unable to De-Quarantine vDisk

 
SOLVED
Go to solution
Marco-85
Occasional Visitor

HPE P2000 G3 MSA SAS - Unable to De-Quarantine vDisk

Hi guys, I hope you can help me out

I have a problem with one vdisk, it has the status quarantined offline QTOF, I try the CLI command: rescan

When I run the command show vdisks it say this:

---------------------------------------------

vd02 8093.4GB 4444.4GB B B RAID6 11 0 64k QTOF 00c0ff152db8000089876e5e00000000
Disabled 0 Fault
The vdisk is quarantined.
- Look for events in the event log related to quarantine (172, 485 or 590) and follow the recommended actions for those events.

--------------------------------------------------

This are the logs:

Download logs 

Thank you in advance

 

5 REPLIES 5
Solution

Re: HPE P2000 G3 MSA SAS - Unable to De-Quarantine vDisk

@Marco-85 

First of all delete the log file from public forum for your data security purpose.

In case of vd02, below my observation,

14th May 2021 1.15 failed
4th June 2021 1.13 failed
8th June 2021 1.11 used as spare drive and reconstruction started
8th June 2021 approx 12:07 rescan done and that created major issue.
As per log I see 1.11 which was getting used as spare drive to reconstruct data for vd02, the same drive got used for vd01 as well. So no idea if the running reconstruction gets complete for vd02. You have no choice but to wait for this to complete and don't do anything else.
Please remember vd02 configured as RAID6 and we have two failed drives 1.13 and 1.15. So once this 1.11 reconstruction gets completed, this vdisk will expect another drive as spare drive to reconstruct data as well.

In case of vd01,

27th May 2021 1.6 failed
1st June 2021 1.14 failed
3rd June 2021 1.14 replaced with new drive and configured as spare drive. It participated in vdisk reconstruction as well.
Then due to too much error with 1.11 reconstruction was not getting completed. That time 1.11 was part of vd01.
4th June 2021 we can see vd01 reconstruction was failing again and again. It was going in quarantine mode.
8th June 2021 It looks like 1.11 failed and got replaced by new drive. But this time it was used to reconstruct data for vd02.
As vd01 configured with RAID6 and 3 drives missing so it went to offline state.

I would suggest to log a HPE support case to try and get back your data as this is complex in nature. However I feel data recovery not possible for vd01 because 1.11 was last drive failed which had latest data and that drive no more present in the system to recover back data.

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

**********************************************************************


I work for HPE
Accept or Kudo
ArunKKR
HPE Pro

Re: HPE P2000 G3 MSA SAS - Unable to De-Quarantine vDisk

Hi Marco,

 

As suggested by Subhajit, please log an HPE support case to check for options to bring pool online

While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company

Accept or Kudo

Marco-85
Occasional Visitor

Re: HPE P2000 G3 MSA SAS - Unable to De-Quarantine vDisk

Thank you  Subhajit for your help, I did what you said, for the vd02 I add a new disk as spare and I have to use the command trust, after that I only loss 1virtual machine, I restore it from my backup, so now it's working propperly, for vd01 I also used the command trust and I did not loss any data. 

I have other 2 warnings on my P2000 MSA, one is about the network card on the controller A and other is about PSU 1, I can post the details here or you recommend to open a new case?

 

Marco-85
Occasional Visitor

Re: HPE P2000 G3 MSA SAS - Unable to De-Quarantine vDisk

Hi ArunKKR.

Thank you for your answer, one question I never submit and HPE support case, what is the procedure to do so?, please help me out to know this for future problems..

once again thank you for your help.

 

Re: HPE P2000 G3 MSA SAS - Unable to De-Quarantine vDisk

@Marco-85 

First of all never use "trust" command without HPE Second level support assistance. It may lead to data corruption if this command used wrongly. This is because when we run this command controller updating metadata structure in the LEFTOVER drives and all other drives part of same vdisk or VDG.

Please find the link to log HPE support case,

https://support.hpe.com/help/en/Content/productSupport/supportCaseManager.html

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

***********************************************************************


I work for HPE
Accept or Kudo