Hello all,
I use esxi 6.5.0 Update 1 (Build 7967591). I had 2 datastore, one of them RAID0 the other one is RAID1. This evening, I add new couple disk and create new array. I have make sure that my new disk array configuration does not touch existing array, I still able to see my previous array, the RAID1 and RAID0 is there.
But, after I reboot the server, my esxi told me that I only had one datastore, the RAID1. When I check the storage --> devices, I can see my disk array is there, the RAID0 disk array.
Is there any home I can recover and re mount my previous datastore on RAID0 ?
Thank for help
Triyono
Jakarta
Does
esxcli storage vmfs snapshot list
show the missing datastore/LUN?
André
Please run ls -lisa
in /vmfs/devices/disks
to see whether the expected devices/partitions show up, and point out which one's the RAID0 device.
André
It looks like that partition table got lost for whatever reason.
Please take a look at https://kb.vmware.com/s/article/2046610, run the command in "Step 1", and post the output (no screenshot please, copy&paste the text output).
In addition to that, also post the result for partedUtil getUsableSectors /vmfs/devices/disks/... the from Step 2.
These two commands do not change anything, but only provide required information.
André
here is the output of #1 step:
/vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0
Unable to get device /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0
---------------------
/vmfs/devices/genscsi/naa.5005076028cf03e7
Warning: Could not determine sector size for /dev/genscsi/naa.5005076028cf03e7: Function not implemented.
Using the default sector size (512).
A bug has been detected in GNU Parted. Refer to the web site of parted http://www.gnu.org/software/parted/parted.html for more information of what could be useful for bug submitting! Please email a bug report to bug-parted@gnu.org containing at least the version (2.4.41-bb42-dirty) and the following message: Unable to determine the size of /dev/genscsi/naa.5005076028cf03e7 (Function not implemented).
Unable to get device /vmfs/devices/genscsi/naa.5005076028cf03e7
---------------------
/vmfs/devices/disks/naa.600605b0040035e019cf2a524062ad99
gpt
72702 255 63 1167966208
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
2 1843200 10229759 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 10229760 1167962112 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
---------------------
/vmfs/devices/disks/naa.600605b0040035e02530a3731d46858c
unknown
72702 255 63 1167966208
---------------------
and you right, I am afraid the partition table is in trouble, here is the output from step 2:
[root@manos-vm:~] partedUtil getUsableSectors /vmfs/devices/disks/naa.600605b004
0035e02530a3731d46858c
Unknown partition table on disk /vmfs/devices/disks/naa.600605b0040035e02530a3731d46858c
after I run this command:
partedUtil mklabel /vmfs/devices/disks/naa.uuid gpt
it seems that my RAID0 partition table has been identified as gpt.
/vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0
Unable to get device /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0
---------------------
/vmfs/devices/genscsi/naa.5005076028cf03e7
Warning: Could not determine sector size for /dev/genscsi/naa.5005076028cf03e7: Function not implemented.
Using the default sector size (512).
A bug has been detected in GNU Parted. Refer to the web site of parted http://www.gnu.org/software/parted/parted.html for more information of what could be useful for bug submitting! Please email a bug report to bug-parted@gnu.org containing at least the version (2.4.41-bb42-dirty) and the following message: Unable to determine the size of /dev/genscsi/naa.5005076028cf03e7 (Function not implemented).
Unable to get device /vmfs/devices/genscsi/naa.5005076028cf03e7
---------------------
/vmfs/devices/disks/naa.600605b0040035e019cf2a524062ad99
gpt
72702 255 63 1167966208
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
2 1843200 10229759 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 10229760 1167962112 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
---------------------
/vmfs/devices/disks/naa.600605b0040035e02530a3731d46858c <-- my missing RAID0 disk
gpt
72702 255 63 1167966208
---------------------
and here it is output of step 2 command:
[root@manos-vm:~] partedUtil getUsableSectors /vmfs/devices/disks/naa.600605b004
0035e02530a3731d46858c
34 1167966174
I'm afraid that the RAID0 LUN is missing some header information.
Simply trying different could make things even worse.
Please try to get in touch with continuum (via Skype, see his profile). He's a data recovery expert, and may be able to help.
André
what's the situation of your arrays on the server RAID configuration now?! and check the hardware and volume information on the OOB solution of your server (iLO, DRAC or etc based on your server vendor) ?!