Fusion

 View Only
  • 1.  'Virtual Disk.vmdk' has one or more internal errors that cannot be fixed

    Posted Dec 30, 2024 07:43 AM
      |   view attached

    Hi,

    This morning my VM for Win 11 appears with this error... I read on the community that there are ways to solve this. Can anyone help me to found the right commands to apply?

    I've already attached the filelist

    The specified virtual disk needs repair

    Cannot open the disk '/Volumes/VM Disk/Maquinas Virtuales/Windows 11 64-bit Arm.vmwarevm/Virtual Disk.vmdk' or one of the snapshot disks it depends on.

    Module 'Disk' power on failed.

    Failed to start the virtual machine

    Many thanks in advanced

    Attachment(s)

    txt
    filelist.txt   4 KB 1 version


  • 2.  RE: 'Virtual Disk.vmdk' has one or more internal errors that cannot be fixed

    Posted Dec 30, 2024 07:46 AM

    Please attach the VM's latest vmware.log file, to see whether it contains useful details.
    Make sure that this logfile does not contain any personal/sensitive information.

    André




  • 3.  RE: 'Virtual Disk.vmdk' has one or more internal errors that cannot be fixed

    Posted Dec 30, 2024 07:50 AM
      |   view attached

    Hi, many thanks for your support, see attached log file


    Attachment(s)

    log
    vmware.log   1.06 MB 1 version


  • 4.  RE: 'Virtual Disk.vmdk' has one or more internal errors that cannot be fixed

    Posted Dec 30, 2024 08:43 AM

    I can't promise anything, but if you provide the required metadata, I will take a look at it.
    For how to collect the required metadata, see Get-VmdkMetadata.sh - Script to collect virtual disk metadata

    André




  • 5.  RE: 'Virtual Disk.vmdk' has one or more internal errors that cannot be fixed

    Posted Dec 30, 2024 08:51 AM
      |   view attached

    Any help will be Wellcome.

    See attached metadata.

    Thanks


    Attachment(s)



  • 6.  RE: 'Virtual Disk.vmdk' has one or more internal errors that cannot be fixed
    Best Answer

    Posted Dec 31, 2024 08:09 AM
      |   view attached

    It took some time, and I needed to make some decisions due to duplicate pointers, so do expect some file system issues within the guest OS. Anyway, the fixed metadata should allow you to access the VM again.
    Make sure that you backup the VM's current files prior to applying the modifications!

    What needs to be done is to inject the fixed metadata into the corrupted files, and to expand one of them to its expected file size.
    Please extract the .fixed files from the attached .zip archive, and run the following commands from within the VM's folder:

    dd if="Virtual Disk-s001-4171366400.fixed" of="Virtual Disk-s001.vmdk" bs=512 count=1024 conv=notrunc
    dd if="Virtual Disk-s002-4250337280.fixed" of="Virtual Disk-s002.vmdk" bs=512 count=1024 conv=notrunc
    dd if="Virtual Disk-s005-4257284096.fixed" of="Virtual Disk-s005.vmdk" bs=512 count=1024 conv=notrunc
    dd if="Virtual Disk-s006-2460610560.fixed" of="Virtual Disk-s006.vmdk" bs=512 count=1024 conv=notrunc
    dd if="Virtual Disk-s036-532283392.fixed"  of="Virtual Disk-s036.vmdk" bs=256 count=1024 conv=notrunc

    dd if=/dev/zero bs=1 count=4096 >> "Virtual Disk-s006.vmdk"

    André


    Attachment(s)

    zip
    Vmdk-Metadata-fixed.zip   578 KB 1 version


  • 7.  RE: 'Virtual Disk.vmdk' has one or more internal errors that cannot be fixed

    Posted Dec 31, 2024 09:30 AM

    Amazing André.

    It worked!!!

    I have access to the VM now.

    Many thanks and have an amazing new year!!!