Vmware Vsphere 5 Error : Unsupported or invalid disk type 7. Ensure that the disk has been imported. "

Maen Abu-TabanjehNetwork Administrator, Network Consultant
CERTIFIED EXPERT
Published:
Updated:
Problem : Unsupported or invalid disk type 7. Ensure that the disk has been imported.

You can run into this problem when you try to power on virtual machine on Esxi that converted from physical to virtual machine. An error message prompt and running of vm will stop. The message looks something like :

Module DevicePowerOn power on failed. Unable to create virtual SCSI device  for scsi0:0,  
'/vmfs/volumes/4e981593-1bbfd9e3-cbe6-00237de1f462/xxxx/xxxx/xxxx.vmdk'
Failed to open disk scsi0:0:
Unsupported or invalid disk type 7. Ensure that the disk has been imported.

This problem occurs when you are converting physical machine to virtual one , actually the The VMs were converted and set to preserve the controller, which was IDE. The disks were also in sparse format. The VM would not boot because the controller was set to lsi sas which will not work with sparse disks. If this is changed then the VM will power up successfully.

Resolution :

Method 1 :

First up, open putty SSH session then type the following :
cd vmfs
cd volumes
cd datastore1

Open in new window

note that datastore1 is sample name , just type your datastore name , if you don't know what is it , just type "ls" after volumes you will see a folder in greeny color , it's the datastore name.

Then type :
mkfstools -i xxxxxx.vmdk xxxx-New.vmdk

Open in new window

note that xxxxx is disk name of the related virtual machine , the process will convert  disk type to zerothick , if the process success try to run your machine , if its not successful the following message may appear :

Destination disk format: VMFS zeroedthick
Cloning disk 'DemoServer.E-Data.local-s001.vmdk'...
Failed to clone disk: There is not enough space on the file system for
the selected operation (13).
If it does appear, then move to method2 :

Method 2 :

You might need to create new virtual machine with IDE hard disk and SCSI controller , you need to edit vmx file and remove line of LSI logic SAS controller and add instead ide controller  configuration :
ide0:0.present = "TRUE"
ide0:0.fileName = "xxxxx.vmdk"
ide0:1.present = "TRUE"
ide0:1.autodetect = "TRUE"
ide0:1.filename = "auto detect"

Open in new window

and under swap sections :
replay.filename = ""
ide0:0.redo = ""

Open in new window

then try to power on your machine.
 
In the future purposes when you are converting SAS Machine to virtual to avoid such case try to modify the machine configuration before you convert it never convert SAS disk to IDE on machine that have LSI Logic Card and SAS Disks ,  see the picture :
 untitled.jpg

Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.

Maen Abu-TabanjehNetwork Administrator, Network Consultant
CERTIFIED EXPERT
3
32,852 Views

Comments (4)

Commented:
Good article, method 1 worked for me to convert a vmware workstation created disk to thick provisioned so I could boot it up with esxi.

One typo, 'mkfstools -i xxxxxx.vmdk xxxx-New.vmdk' should be 'vmkfstools -i xxxxxx.vmdk xxxx-New.vmdk'

Commented:
thanks Martin81 -
Maen Abu-TabanjehNetwork Administrator, Network Consultant
CERTIFIED EXPERT
Top Expert 2011

Author

Commented:
thank you martin81 for correction :)
amanzoorNetwork infrastructure Admin

Commented:
Thanks a lot Jordannet, very easy to understand article.  Method 1 worked for me, flawless.

Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.

Get access with a 7-day free trial.
Continue Growing Your Skills and Your Career
  • Interact with leading experts on your specific technology problems.
  • Receive the guidance of experienced professionals.
  • Learn from troubleshooting others have experienced.
  • Gain knowledge from a library of courses, all included.