Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7.

Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first?Unable to create virtual SCSI device for scsi0:0

I got this error when I imported a Redhat Linux 4 VM instance from VMware Server 2.0 and converted the VM to ESXi and powered on the VM.

/vmfs/volumes/4bb68dd3-8372b78e-eb21-0019b9eddb67/RHEL4 # vmkfstools -i rhel4_vm.vmdk -d 2gbsparse rhel4_esx.vmdk Destination disk format: sparse with 2GB maximum extent size Cloning disk 'rhel4_vm.vmdk'... Clone: 100% done.
After importing, when I power on the Redhat Linux VM, I get the following error:

Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first?Unable to create virtual SCSI device for scsi0:0, ‘/vmfs/volumes/4a8075b3-4e4bf1b8-28e40017a48d6112/syslogappliance/Appliance-OS-.vmdk’ Module DevicePowerOn power on failed.

To fix this problem, I had to reimport the VM using the "zeroedthick" argument for the "vmkfstools" command:

/vmfs/volumes/4bb68dd3-8372b78e-eb21-0019b9eddb67/RHEL4 # vmkfstools -i itvmgr41.vmdk -d zeroedthick itvmgr40sp1.vmdk Destination disk format: VMFS zeroedthick Cloning disk 'itvmgr41.vmdk'... Clone: 100% done.


vmkfstools -i disco_origen.vmdk -d zeroedthick disco_origen_1.vmdk


With the "zeroedthink" option, a flat file is created with complete disk size allocated to the file. For example, my linux distribution was created to use 73GB file, so a ".vmdk" file of 73GB is created.

I don’t want to create a 73GB file because I don’t know if I’ll use all that space in the future, I opted to "thin" option.

Other supported disk formats are explained below:

Supported Disk Formats

When you create or clone a virtual disk, you can use the -d –diskformat suboption to specify the format for the disk. Choose from the following formats:

. zeroedthick (default) – Space required for the virtual disk is allocated during creation. Any data remaining on the physical device is not erased during creation, but is zeroed out on demand at a later time on first write from the virtual machine. The virtual machine does not read stale data from disk.
. eagerzeroedthick – Space required for the virtual disk is allocated at creation time. In contrast to zeroedthick format, the data remaining on the physical device is zeroed out during creation. It might take much longer to create disks in this format than to create other types of disks.
. thick – Space required for the virtual disk is allocated during creation. This type of formatting doesn’t zero out any old data that might be present on this allocated space. A non-root user is not allowed to create this format.
. thin – Thin-provisioned virtual disk. Unlike with the thick format, space required for the virtual disk is not allocated during creation, but is supplied, zeroed out, on demand at a later time.
. rdm - Virtual compatibility mode raw disk mapping.
. rdmp – Physical compatibility mode (pass-through) raw disk mapping.
. raw - Raw device.
. 2gbsparse - A sparse disk with 2GB maximum extent size. You can use disks in this format with other VMware products, however, you cannot power on sparse disk on an ESX Server host unless you first reimport the disk with vmkfstools in a compatible format, such as thick or thin.
. monosparse – A monolithic sparse disk. You can use disks in this format with other VMware products.
. monoflat - A monolithic flat disk. You can use disks in this format with other VMware products.


Fuente: http://pubs.vmware.com/vi35u2/wwhelp/wwhimpl/common/html/wwhelp.htm?context=server_config&file=sc_appb.21.6.html