Hyper-v Vhd A Disk Read Error Occurred
Contents |
Join Now I have Spiceworks installed on a win7 and want to create a vhd so that it can run on hyper v, on the server. I created a
Disk2vhd Alternative
vhd using Disk2vhd and created a new virtual machine in hyper v. As disk2vhd error snapshotting volumes it starts up it gives the error "A disk read error occurred press ctrl alt delete to restart." The pc is
Virtualbox Bios Disk Read Error At Sector
only running Spiceworks and the vhd is only 12.8gb Any reason why its giving me this, am I missing something? Reply Subscribe RELATED TOPICS: Best software for P2V Conversion P2V Conversion how to http://www.chicagotech.net/netforums/viewtopic.php?f=3&t=17265 successfully perform a p2v conversion as well as the requirements for suc   10 Replies Thai Pepper OP Bournestar Sep 13, 2012 at 10:59 UTC First thing I would check would be whether you set up the disk as SCSI or IDE on the VM settings. if that is ok I would look at taking the image again to rule out corruption. 2 https://community.spiceworks.com/topic/258079-p2v-conversion-using-disk2vhd Cayenne OP Keith - Randox Sep 13, 2012 at 11:13 UTC Sounds very much like you havent configured the VM with the right disk controller to match the source physical system. Google your error message and you will find hundreds of posts with similar issues. 1 Thai Pepper OP Brian Thorp Sep 13, 2012 at 11:49 UTC Chestnut Consulting is an IT service provider. I agree with Keith. I do this all the time and generally it will work fine if you put the VHD as IDE. Before you P2V, it is recommended to build a machine on hardware that is as generic as possible (read: no additional drivers) 0 Pimiento OP IT8141 Sep 13, 2012 at 11:59 UTC Its configured in IDE. Did make a 2nd VHD and still the same issue. Ill check on Google if I can find any solutions. 0 Chipotle OP _Tyler Sep 13, 2012 at 12:56 UTC Make sure you are NOT checking the "Prepare for use in a virtual machine" box in the P2V utility before you click create. I found that box a bit mis-leading, it's not for Hyper-V VHDs. 0 Tabasc
ThijsB Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 October 2009 Location: netherlands Status: Offline Points: 19 Post Options Post Reply QuoteThijsB Report Post Thanks(0) QuoteReply Posted: 04 November 2009 at 10:42am Damm... http://forum.sysinternals.com/a-disk-read-error-occurred_topic20815_page4.html Did download the new 1.31.... But .... nothing... only black screen..... Damm..... ( BTW Lenovo T60 ) ThijsB Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 October 2009 Location: netherlands https://neosmart.net/forums/threads/windows-7-disk2vhd-and-hyper-v.9067/ Status: Offline Points: 19 Post Options Post Reply QuoteThijsB Report Post Thanks(0) QuoteReply Posted: 04 November 2009 at 2:00pm STOP the presses.. Eureka..... - Created a VHD with the new Disk2VHD 1.3 - Try to boot.... disk read Black screen only... ( So no error "A Disk Read Error Occurd" ) - Booted with a CDto repair XP with the recovery console - Replaced the HAL --At the command prompt, type “CD System32″ , hit enter. Then type “expand D:\i386\HALACPI.DL_” , hit enter. Finally, type “copy HALACPI.DLL HAL.DLL”, and hit enter. Type Y for yes on the overwrite file confirmation message. (*cd drive letter may vary) Now it hangs on the Windows XP screen. ... but.... a little disk read error bit closer.... I am sure... this can be solved also ThijsB Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 October 2009 Location: netherlands Status: Offline Points: 19 Post Options Post Reply QuoteThijsB Report Post Thanks(0) QuoteReply Posted: 04 November 2009 at 3:15pm Update... Looks like the VHD is running in Save mode.... Damm.... Don't have time to look futher... ( maybe tomorow, keep U posted ) ThijsB Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 October 2009 Location: netherlands Status: Offline Points: 19 Post Options Post Reply QuoteThijsB Report Post Thanks(0) QuoteReply Posted: 05 November 2009 at 11:48am After replacing the HAL.DLL, I am only able to boot in Safe mode.... ThijsB Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 October 2009 Location: netherlands Status: Offline Points: 19 Post Options Post Reply QuoteThijsB Report Post Thanks(0) QuoteReply Posted: 10 November 2009 at 7:10am Still no progress.... Only able to boot in Safe mode after doing the HAL.... Note: With VMWARE I don't have any issues.... ( But somehow i preferred this tool.. don't ask me why ) ThijsB Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 October 2009 Location: netherlands Status: Offline Points: 19 Post Options Post Reply QuoteThijsB Report Pos
Likes Received: 0 Trophy Points: 0 I was running Windows 7 x64 on my system, and needed to install Windows Server 2008 R2. I want to run my Windows 7 in a VM on the Windows Server 2008 R2 Hyper-V. In order to take an image of the my system, I used the SysInternals Disk2vhd utility to create a virtual disk (*.vhd) of my system. I know that Disk2vhd does not support creating an image of a system, and then running that VM on the exact same system/partition, but I thought EasyBCD would be able to fix that. Here's the warning about Disk2vhd; Note: do not attach to VHDs on the same system on which you created them if you plan on booting from them. If you do so, Windows will assign the VHD a new disk signature to avoid a collision with the signature of the VHD’s source disk. Windows references disks in the boot configuration database (BCD) by disk signature, so when that happens Windows booted in a VM will fail to locate the boot disk. My error in Hyper-V is "A disk read error occurred. Press Ctrl-Alt-Del to restart." Is this something that EasyBCD can help me with? I tried running it and pointing to the VHD file, but it didn't seem to make any changes and/or difference. Thanks for any insight into this. AainR, Dec 23, 2011 #1 sambul12 Member Joined: Oct 2, 2010 Messages: 47 Likes Received: 0 Trophy Points: 6 If you attach your VHD on the same system, Windows will change the virtual disk signature, thus preventing boot from it. Read more on how to fix. To verify, this is your problem, try to boot the VHD on your real PC instead of the VM. Understand that Windows is designed to prevent by default running the same install on various PCs and VMs due to licensing policy. However there is more to it. If your real PC boots only from SATA drives, and Hyper-V is setup to boot from IDE, you would have to add IDE support on startup, and vice versa. Also add DetectHAL to BCD Entry of the OS on VHD. The simplest way for you to fix Hyper-V issue would probably be Generalizing the install with Sysprep, or follow this Tutorial. Last edited: Dec 25, 2011 sambul12, Dec 25, 2011 #2 (You must log in or sign up to reply here.) Show Ignored Content