@@@Hi Community,
I am running one time the vms and etc normally, until one time my VM's are starting to act up, like the boot up after loading the Windows loading page, it is just black screen, I performed a safe mode and performed as shutdown but i still took me time before the start-up window appears.
The I starting doubting my computer resource and perform a refresh at my storage, then an error message showed up that the "ESXI host does not have persistent storage" and the datastore is lost. After performing a some refresh, the datastore sometimes comes up but with a not valid storage details like this below:
These are my partion list
~ # partedUtil getptbl /vmfs/devices/disks/naa.690b11c02431950018a2880c287af901
gpt
218673 255 63 3512991744
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
3 10229760 3512991710 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
# esxcfg-scsidevs -m
naa.690b11c02431950018a2880c287af901:3 /vmfs/devices/disks/naa.690b11c02431950018a2880c287af901:3 510ff510-52bcd128-b4d5-90b11c2d9c60 0 datastore1
I also ran this and got this error
# esxcli storage filesystem list
Error getting data for filesystem on '/vmfs/volumes/510ff510-52bcd128-b4d5-90b11c2d9c60': Unable to get FS Attrs for /vmfs/volumes/510ff510-52bcd128-b4d5-90b11c2d9c0, skipping.
Cannot open volume:
I also followed some of the KBA's but I'm having these difficulties Recreating a missing VMFS datastore partition in VMware vSphere 5.0/5.1/5.5 (2046610)
# offset="128 2048"; for dev in `esxcfg-scsidevs -l | grep "Console Device:" | awk {'print $3'}`; do disk=$dev; echo $disk; partedUtil getptbl $disk; { for i in `echo $offset`; do echo "Checking offset found at $i:"; hexdump -n4 -s $((0x100000+(512*$i))) $disk; hexdump -n4 -s $((0x1300000+(512*$i))) $disk; hexdump -C -n 128 -s $((0x130001d + (512*$i))) $disk; done; } | grep -B 1 -A 5 d00d; echo "---------------------"; done "---------------------"; done
/vmfs/devices/cdrom/mpx.vmhba35:C0:T0:L0
Warning: Unable to open /dev/cdrom/mpx.vmhba35:C0:T0:L0 read-write (Device or resource busy). /dev/cdrom/mpx.vmhba35:C0:T0:L0 has been opened read-only.
Error: The device /dev/cdrom/mpx.vmhba35:C0:T0:L0 has zero length, and can't possibly store a file system or partition table. Perhaps you selected the wrong device?
Unable to get device /vmfs/devices/cdrom/mpx.vmhba35:C0:T0:L0
On the logs, im seeing the same message below:
pu34:5590)Vol3: 647: Couldn't read volume header from control: Invalid handle
and performing kill world ID, but there is no VM running.
~ # esxcli storage core device world list -d naa.690b11c02431950018a2880c287af901
Device World ID Open Count World Name
------------------------------------ -------- ---------- ----------
naa.690b11c02431950018a2880c287af901 4120 1 idle0
~ # esxcli vm process list
~ # esxcli vm process kill --type=force --world-id=4120
Unable to find a virtual machine with the world ID 4120
~ # esxcfg-rescan -u vmhba1
Still no avail
The thing is the files are still there, currently I'm creating a backup, but there are two VM files that are missing and it shows at my vm list under the host as inaccessbile.
The storage adapter still shows that the vmhba1 is mapped to this disk.
Please tell me what to do?
