what is Verify vdisk-groups command?

[ariapostmail]

hi all

hi all

command
Verify vdisk-groups (Vdiskname)
What does it do on my vdisk if I hit it?
if I run this command, it is possible that my vdisk volume is shown correctly again?

The problem started here when my msa 2040 gave a Fault error on poolA and all vdisks gave an FTOL error. I turned it off and on several times, but it didn't work.
My friend unfortunately switched controller A with b. And vdisks go to quarantine mode. I said put the controllers back. Then it was quarantine again. I checked all hard drives and they are healthy. One or two people wrote in the HP forum to type the Dequrantine command to make the vdisk online. I typed this command. Then they said that if it was still in FTOL mode, press the Trust vdisk command to fix it. I also ran this command, but the capacity of 6 of my 7 vdisks became 0. But the volume capacity is still correct.
I started reading cli msa commands, I saw the verify vdisk-group command, if I run this command, it is possible that my vdisk volume is shown correctly again? And will the FTOL error be fixed or will it make the situation worse?

[Mr_Techie]

Hi @ariapostmail 

Good day. 

Running the verify vdisk-group command on your MSA 2040 will not directly change the state of the vDisk, but it is useful to validate the integrity of the vDisk group and check for any errors or inconsistencies. It typically verifies the consistency of the vDisks within the group and can help identify any issues that might have been caused by the earlier controller swap or the FTOL state.

Fyi, verify vdisk-group command is useful for diagnostics, but it may not directly resolve the FTOL error or fix the capacity issue. It's safe to run, but proceed with caution and consider your backup and recovery options if necessary.

[ariapostmail]

hi Mr_Techie
thank you for your respond

How do I fix the problem of FTOL and 0 capacity showing Vdisk groups?
I need guidance and help. Hp doesn't support me yet because the device is old.
can you help me

I did everything I could think of, but still the vdisks are not accessible
I started to recover about 14 days ago, but the recovery is still ongoing and will take another 3 months. That is terrible.
I am doing volume recovery with the software. I don't know why my storage is messed up like this, apparently the virtual pool structure is damaged. I wish someone would guide me here. All my information is on storage. And I got into trouble badly

[Mr_Techie]

@ariapostmail 

Data loss and storage issues are challenging, and given that this involves FTOL errors, quarantined vDisks, and 0 capacity showing for some vDisk groups, the virtual pool structure is likely in a severely damaged state. I would say please contact the Support team for further assistance.