![]() ![]() Read the link Wil gave you - easpecially make sure you read about vmkfstools -t 0 If this also fails you have a real problem and probably should call me or Ontrack for help. If this works you can regard the fixed-disk-flat.vmdk as healthy - or better - as the best you can get in this circumstances. Use a Linux VM and connect to an ESXi host that has access to the VMFS-volume.Ĭonnect to a second ESXi with a healthy datastoreĭdrescue /esxi-in/vmfs/volumes/datastore-damaged/vm-name/disk-with-i-o-errors-flat.vmdk /esxi-out/vmfs/volumes/healthy-datastore/recovery/fixed-disk-flat.vmdk /esxi-out/vmfs/volumes/healthy-datastore/recovery/ If that also fails it is time to switch to Linux for the following steps. If that works without errors you can regard fixed-disk-flat.vmdk as healthy. If that again fails with I/O errors you probably have VMFS heartbeat corruption on that volume.ĭd if=disk-with-i-o-errors-flat.vmdk of=fixed-disk-flat.vmdk bs=1M ![]() Vmkfstools -i disk-with-i-o-errors-000001.vmdk fixed-disk.vmdk If that fails with I/O errors again make sure that disk-with-i-o-errors.vmdk is used readonly by adding an empty snapshot-delta to it. If that works without vmkfstools-errors you can regard fixed-disk.vmdk as healthy. Vmkfstools -i disk-with-i-o-errors.vmdk fixed-disk.vmdk If I see this I usually first try to clone the vmdk with vmkfstools: There are 2 types of I/O errors that you may see in log files while attempting standard operations: physical i/o errors and logical i/o errors. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |