Disk Read Error Occurred Vmware Converter
Contents |
you don't know the cause of the problem. I was converting a plain physical MS WinXP machine to a virtual one and when it was all finished, I have started the machine and got this
A Disk Read Error Occurred Press Ctrl+alt+del To Restart
message at VM bootup: "A disk read error occured, press ctl+alt+delete to a disk read error occurred windows 10 restart". I was using a VMware Converter Standalone 4 on a vCenter 4 platform. Google gave me a lot of a disk read error occurred laptop possible solutions..from booting a WinXP recovery console to selecting a SCSI disk over IDE hard disk during conversion configuration, but the solution that worked for me was converting an IDE to SCSI https://kb.vmware.com/kb/1033243 disk type after conversion. You have to write something in the VM configuration file so follow this steps to do so: 1. Connect to the ESX via SSH where your converted machine is located and go to your datastore path. example: cd /vmfs/volumes/"datastore name"/"virtual machine name"/ 2. Now edit the .vmdk file of the VM which is the primary disk file with your favorite http://www.itino.net/a-disk-read-error-occured-press-ctlaltdelete-to-restart-at-vm-bootup/ editor - vi or nano (I prefer vi). 3. Look for the line: ddb.adapterType = "ide" and change that adapter type to "buslogic". example: ddb.adapterType = "buslogic" 4. Save changes and exit. 5. Now from your VMware Infrastructure/vSphere Client edit your virtual machine in a way that you remove the disk from it (do not delete it while removing!). Then add it as an existing disk - navigate to the location of the disk and select to add it into the virtual machine. While configuring the SCSI ID should read SCSI 0:0. 6. If a CDROM device exists in the virtual machine it may need to have the IDE channel changed because it could raise a problem while booting. Just remove it and add it again like an IDE 0:0. tino Vmware disk error, p2v, vmware convert Sync Firefox on multiple computersHow to activate GodMode in Microsoft Windows 7? Leave a Reply Cancel reply Name * Email * Website Post Comment Categories Cisco Linux Microsoft MikroTik Misc Security Vmware Google Copyright © 2016 ITino. Proudly powered by WordPress & Corporate Business WordPress Theme by Dinozoom. This site uses cookiesOkay, thanksFind out more
Join the Community! Creating your account only takes a few minutes. Join Now I was running ESXi 4.1 host on an old HP DL360 G5 with RAID 5 (3 disks). One of the disks has failed and when I got a replacement, I've found out that another is failing as well. https://community.spiceworks.com/topic/330153-disk-read-error-has-occurred-press-ctl-alt-del-to-restart-esxi-4-1 So instead of rebuilding RAID5 I have build RAID0 of two healthy disks (gives me same capacity as RAID5) and installed ESXi 4.1 on the new RAID0 Before I build the new RAID I've copied my VM files from the datastore so that I have my http://www.zimarev.com/2010/12/fighting-disk-read-error-after-vmdk.html nvram, vmdk (both, descriptor and virtual disk), vmsd, vmx and vmxf files, even the log files. Then I copied them all back to a new datastore, imported vmx files to the inventory but when I try to start the VM is hangs on "Disk Read disk read Error has Occurred. Press Ctl+Alt+Del to restart". I can start the same VM on my VMWare Player with no issues. I've tried changing Disk Controller from BusLogic to SCSI, tried creating new virtual disk of the same size (vmkfstools -c 100G new.vmdk) and then changing new.vmdk to point to my original virtual disk, but it didn't help Reply Subscribe View Best Answer   11 Replies Serrano OP ErikFest Apr 28, 2013 at 4:29 UTC Maybe your other physical disks on this VM Host are shot too? Bad sectors and disk read error whatnot? Can you try other disks? Do you have / Can you get spares? By the fact they boot in Player I think (I could be wrong) it's safe to assume your VM's are okay. 0 Mace OP Texkonc Apr 28, 2013 at 4:35 UTC You never want to run your Hypervisor on Raid0. It is just as reliable as Raid5 during a rebuild. You can not stand a single drive loss in Raid0 like you can in Raid5. Still a 3 drive Raid5 is the devil. What happened to you with the Raid5 rebuild is about par for Raid5. The load increases and one of the other drives says F U I am done. Then you lost all, just like if you were running all 3 in Raid0 for production and drive failed. Since you only have 3 drives, your Hypervisor doesn't change much, so it would be better to mirror that and Raid10 your SAN array. 0 Serrano OP LarryCK Apr 29, 2013 at 4:27 UTC ErikFest wrote: Maybe your other physical disks on this VM Host are shot too? Bad sectors and whatnot? Can you try other disks? Do you have / Can you get spares? HP diagnostics did not find anything wrong with the two disks I build RAID0 on. No, I'm afraid this is al I have to work with. 0 Serrano OP LarryCK Apr 29, 2013 at 4:34 UTC Thanks Texkonor, I'm afraid I lost you towards the end of your post. I do understand RAID5 benefits over RAID0 but I only have two phy
Windows Server 2008 to 2008 R2 was planned anyway. The questions raises what to do with exsiting virtual machines? One of the reason to use virtual environment was to decrease the need of reinstalling OS every time we need to move it to another hardware. The solution was found in form of the vmdk2vhd utility supported by numerous success stories of such migration.This page contains quite extensive explanation how such migration should be done. One of the most important steps is to check whether the existing machine uses IDE or SCSI controller on the boot drive. Hyper-V doesn't boot virtual machines from virtual SCSI controller. I followed the steps described in the article and expected everything to work fine. Even better, some of my VMWare machines already had IDE controllers on a boot drive.So far so good but when all disks have been migrated and I created quite a few new Hyper-V virtual machines, none of those started up. There were two types of errors:For bigger virtual disks I got a message "Disk read error. Press Ctrl+Alt+Del to restart" on a black screen.For the other machines I got Windows booting but crashing in a couple of seconds with the BSOD.After spending hours of reading excessive number of posts in different forums and blogs I managed to resolve both issues. So first I understood the reasons of these issues:"Disk read error" occures after vmdk to vhd migration because MBR or partition table is not valid for the disk size. This might be a bug in vmdk2vhd, I have no idea but this issue is definitely related to the hard drive geometry.The second issue is known as famous "inaccessible boot device" BSOD error. It only occured on those machines that used to have SCSI drives as boot devices, although I followed the instructions to avoid this problem (may be not very carefully).Now we get quickly to the solutions of both problems:Hard drive geometry can be fixed using the teskdisk utility, which also runs on Windows. What needs to be done is simple - use Disk Manager to mount the corrupted virtual disk and run testdisk. Further steps are very well described in the following atricles:Testdisk Step By StepRebuilding NTFS boot sector using TestdiskWhen you are done with testdisk, don't forget to save the new partition table and quit the utility, after that unmount your virtual disk in Disk Manager. Try starting the machine in Hyper-V and it should not give you "Disk read error" anymore.The IDE driver must be injected to the offline Windows machine, in the system registry. Although it sound