SOLVED
You shouldn't try trust command without checking logs by some MSA specialist. If you have contract with HPE then log a support case with HPE
How vd01 went to offline state?
You can also check system events and find out if any drives having any hardware errors. If all drives health ok then you can run the below command,
#trust enable
#trust vdisk vd01
# show vdisks
You can also share the MSA logs with me in private chat and I can check the same.
Keep in mind that you shouldn't run trust command multiple times on a vdisk otherwise drive metadata will get corrupted and no one can recover data from the vdisk.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
Bundle Version: TS230P008
It looks like this MSA running with very old or expired or inactive firmware so there is no gurantee that Vdisk will come up or not.
Three drives at location 1.2, 1.11 and 1.12 shows big number of recovered errors which looks bad as well.
Anyway you can try the below commands,
#trust enable
#trust vdisk vd01
# show vdisks
Once vdisk came up. Take data backup. Then plan for downtime and stop Host IO or disconnect Host from MSA. Then upgrade MSA controllers to latest version TS252P005
Upgrade Path -> TS230 -> TS250 -> TS252
www.hpe.com/storage/MSAFirmware
Then you may have to plan and replace faulty drives one by one.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
I forgot to mention that you need to physically re-seat drive at location 1.10 then only you can try the commands that I have suggested because 1.10 now missing and that is the last drive for which vdisk went to offline state
If even after re-seat 1.10 not coming up then there is no way to recover this vdisk
Vdisk was made with 11 drives in RAID5. Right now only 9 drives present. As you know RAID5 can't sustain more than one drive failure. Here two drive missing which are 1.6 and 1.10 so vdisk in offline state as this is RAID failed. We don't need 1.6 anymore but If we re-seat 1.10 as that is having latest data so We can try recovering this vdisk as that time we will have 10 drives in vdisk which is meeting RAID5 criteria which will help to recover the vdisk but again it depends upon in what condition 1.10 is. If controllers not able to read data from 1.10 then data recovery not possible.
1.6 failed on 30th Dec 2017 but no one replaced it.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
Is 1.10 now detected by controller?
As told you before there are multiple drive having issue which will not allow to recover the vdisk
You can log support case with HPE if they can recover
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
Please don't run trust command without drive 1.10 back online again otherwise no way you can recover data.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
Hello,
I highly recommend you take an immediate backup of the data. With the multiple drive failure scenario you have described the chances that reconstruction will complete successfully are extremely small. While you have access to the data, please back it all up! You will need to verify the data is valid but at least if you have a backup you can restore valid data if the reconstruction fails.
Be aware - if the reconstruction fails and the vdisk goes offline again, using trust will likely cause data integrity issues.
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.
I work for HPE