I have an ESXi 3.5 server with a simple local RAID5 array. One of the drives in the array failed causing the whole system to hang, so it was replaced, and the array rebuilt. However, the unclean shutdown during the failure seems to have caused one of my vmdk files to become inaccessible. As you can see, when I attempt to list the files within the vm directory, it displays "No such file or directory" for the flat backing of the vmdk indicating that the file might still actually be there. The free disk space on volume is still showing the space being consumed by the phantom disk file.
/vmfs/volumes/4ad3ba84-4e750958-3b28-0007e9065658/drool # ls -l
ls: ./drool-flat.vmdk: No such file or directory
-rw------- 1 root root 8684 Oct 19 17:27 drool.nvram
-rw------- 1 root root 408 Oct 19 18:02 drool.vmdk
-rw------- 1 root root 0 Oct 16 21:08 drool.vmsd
-rwxr-xr-x 1 root root 2292 Oct 19 18:04 drool.vmx
-rw------- 1 root root 269 Oct 19 18:04 drool.vmxf
-rw-r--r-- 1 root root 70507 Oct 16 22:56 vmware-1.log
-rw-r--r-- 1 root root 40996 Oct 19 18:05 vmware-2.log
-rw-r--r-- 1 root root 14944 Nov 4 23:50 vmware-3.log
-rw-r--r-- 1 root root 14944 Nov 4 23:51 vmware-4.log
-rw-r--r-- 1 root root 14944 Nov 6 23:54 vmware.log
/vmfs/volumes/4ad3ba84-4e750958-3b28-0007e9065658/drool #
Output from fdisk:
Disk /dev/disks/vmhba1:0:0:0: 367.0 GB, 367033057280 bytes
64 heads, 32 sectors/track, 350030 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/disks/vmhba1:0:0:1 5 750 763904 5 Extended
/dev/disks/vmhba1:0:0:2 751 4845 4193280 6 FAT16
/dev/disks/vmhba1:0:0:3 4846 350030 353469440 fb VMFS
/dev/disks/vmhba1:0:0:4 * 1 4 4080 4 FAT16 <32M
/dev/disks/vmhba1:0:0:5 5 52 49136 6 FAT16
/dev/disks/vmhba1:0:0:6 53 100 49136 6 FAT16
/dev/disks/vmhba1:0:0:7 101 210 112624 fc VMKcore
/dev/disks/vmhba1:0:0:8 211 750 552944 6 FAT16
When attempting to do "vmkfstools -R" it always fails--maybe this isn't supported on ESXi?
- vmkfstools -R /dev/disks/vmhba1:0:0:3
Check that the file system on /dev/disks/vmhba1:0:0:3 is not being accessed by another server. Do you want to continue?
0) Yes
1) No
Please choose a number 0-1: 0
Error: vmkfstools failed: vmkernel is not loaded or call not implemented.
Any other suggestions?
Tags:
esxi_3.5
