I have a problem with Msa 2040 storage. Access to vdisks is disabled

[ariapostmail]

hi
I have a storage msa 2040 but a few days ago I bought a new storage 2062. I haven't started the 2062 yet and the 2040 storage has crashed and I've lost access to my data.

In short, I have 7 vdisks and 12 volumes.
Except for one vdisk which is of linear type and the volume inside it, the other vdisks which are of virtual type are out of reach.
Full description:
On the MSA 2040 dual fc storage, I had created a PooLA, the owner of which was controller A, inside which there were 6 virtual vdisks. And 10 volumes were made inside it.

I also have a linear disk group that has a volume of 2 TB. And he is healthy after the accident.
But before my access was cut off, I had connected the enclosure number 4, first two linear vdisks, the volume of which was 10TB and 5TB.

, but because I didn't need them, I deleted them and added these hard drives to PoolA and created two virtual vdisks, one with 16 1.2 TB hard drives and the other with 9 1.2 TB hard drives. After this vdisks started initializing. I didn't have anything to do with the system anymore. On the other hand, the empty volume of the other virtual disks was small, so I added these hard drives. After about 24 hours, the storage had a problem of not accessing the volumes.

I connected to the graphic storage console and saw that PoolA has a fault status and my vdisks are also in the same status. The amount of their volume was shown correctly. 3 to 9TB-one 12TB and 3.5TB and 7TB and 3TB and 3.5TB and 2TB and 10TB. In the volumes section, the volume was correct and the status was OK and green.
What he did was turn off the storage and turn it on again. It didn't work. Once I moved controller a with b. This time the vdisks were placed in QTOL or quarantine mode. But I turned off the storage again from the console. I installed the controllers as before.

Again, the status of vdisks was in QTOL mode. This time I searched on the internet and the Hp forum. One of the HP employees said that you can run the dequarantine disk-group command. I ran this command and the vdisks changed from QTOL to FTOL, but I still had no access. In the HP forum, they said that if this does not work, press the trust enable command and then trust vdisk diskgroup name
hit After I typed this command, the volume of 6 of my 7 virtual vdisks changed to 0 and the volume of the reserved value was added!! But the volumes were still correct.

In the HP DL380 g9 servers that I have esxi 7, the data stores are in unknown mode with unknown addresses. I connected a server with optical fiber and Windows Server 2022 to Storge. In the device manager section, it shows the number of volumes in the storage, in the hard disk section, there are a number of hard disks with the names of MSA 2040 disks, but they are not usable, and in some recovery software, they show up to the capacities. . Even some data can be recovered from it, but very little.

Now I don't have any backup and I need my vdisks to be online again so that my virtual machines can come back.

Is there a command that can make vdisks online and available again?
thank you

Pic Errors:
https://ibb.co/kxqx3dG
https://ibb.co/D5Zq3XL
https://ibb.co/YZFzrCr
https://ibb.co/Wsb01NT
https://ibb.co/Z6Tv42k
https://ibb.co/GkjG5kS
https://ibb.co/8697rT4

[ariapostmail]

Hello, I don't know the reason for the power cut or the vdisk space on the Storage 2040 being full
pool A has an error and the capacity of vdisks, except for one, is 0. But all the volumes show the correct capacity, but in Windows Server, I can only see the names of the volumes, Msa 2040 device, which must be formatted to be used.
Is there a way to repair vdisks or make them online again? Is there no command for this?
Or I can number the hard drives in the existing order and set them to 2062 and test.

[ArunKKR]

Hi,

MSA 2060 doesnt support the hard drives caddys of MSA 2040.

More over moving disks from one array to another model array is not recommended.

I see that you have performed a lot of troubleshooting steps the majority of which should not have been performed without engaging HPE support.

Please log an HPE support case to check for any options to bring disk groups / Pool online.

This issue will require log/debug log analysis to suggest the next steps.

I do understand that MSA 2040 is an end of support life product.

Please contact HPE support team and log a support case to check for one time support options.

[ariapostmail]

hi mr arun, how are you sir?

I made a ticket for HP, but they told me that they no longer support MSA 2040. What should I do now?
You can help me. Tell me the log and any necessary information.

All my information is on the storage and I really don't know what to do. It remains only to use the recovery software, the speed of recovery from msa 2040 is very slow, because the storage controllers do not allow fast reading of the hard drives. 2000 hours to 4000 hours means it takes 3 months to recover at least 10 terabytes of information.
thank you sir

[ArunKKR]

Hi @ariapostmail ,

HPE chat support team would have reached out to you through email.

Please respond to the email and we will see how best we could assist you.

[ariapostmail]

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

[ariapostmail]

An HP MSA 2040 device has failed due to a hard drive being full or a firmware bug
It was giving FTOL error on POOL A
Controller A was moved to B, it didn't make a difference
The Vdisk hard drives went into quarantine and the controllers were returned to their original state
Dequarnti-trust commands were executed and the capacity of 6 out of 7 vdisks became zero
But the volume capacity did not change
The hard drives are healthy
And the volumes show the capacity correctly, but it is not possible to access their real information. Do we have a command to repair vdisks so that they become operational?

Currently, I am recovering information with a series of recovery software, but it is extremely time-consuming, it takes about 3 months.

[ArunKKR]

Hi @ariapostmail ,

HPE chat support team would have reached out to you through email.

Please respond to the email and we will see how best we could assist you.

We will need an HPE support case and logs to be reviewed to assist you.

Please note that if the Pools are already reporting healthy state , there wont be nothing much we could do from our end. Using trust command without reviewing logs could have created corruption at block level or file system level.