Disk Read Error After Ghosting
List Welcome Guide More BleepingComputer.com → Microsoft Windows Support → Windows XP Home and Professional Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Register a free account to unlock additional features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site. Click here to Register a free account now! or read our Welcome Guide to learn how to use this site. After restoring a ghost image, Computer boots to "A Disk Read Error Occured" Press CTRL-AlT-Del to restart. Started by EDGAR214 , Mar 23 2010 05:27 PM Please log in to reply 2 replies to this topic #1 EDGAR214 EDGAR214 Members 2 posts OFFLINE Gender:Male Local time:02:17 AM Posted 23 March 2010 - 05:27 PM After restoring a ghost image, Computer boots to "A Disk Read Error Occured" Press CTRL-AlT-Del to restart. It runs Windows XP, its a Lenovo Thinkpad with a SATA drive (also in AHCI): This is what happened. I took out the 160GB SATA from the laptop, and put it in an USB enclosure and created an image in Ghost 11 that is saved to a desktop computer, then. I restored the image to a 80GB SATA drive with a USB enclosure. I pop in that 80GB drive to the laptop and that message of "A Disk Read Error Occured" shows up. There is only one partition. I tried the following already: fixboot fixmbr Chkdsk /r (all clean) By the way, if I put it in an enclosure, it is accessible and does read data as normal. What can I do to fix it? Please don't ask me to reformat, I want the laptop to use that image. Back to top BC AdBot (Login to Remove) BleepingComputer.com Register to remove ads #2 rigel rigel FD-BC BC Advisor 12,944 posts OFFLINE Gender:Male Location:South Carolina - USA Local time:03:17 AM Posted 23 March 2010 - 06:20 PM The difference in drive sizes (Larger to smaller) may be the problem. I haven't used Ghost in a while, but I had a similar thing happen to me. Let me dust off my memory and dig.Edit : Look at nigels reply here: http://www.symantec.com/connect/forums/len...l-wil
Registration E-mail: * Password: * Useful Links How to get Support? All Product Documentation Frequently asked questions by product Acronis Backup 12 https://forum.acronis.com/forum/16205 FAQ Acronis Backup 11.7 FAQ Acronis Backup & Recovery FAQ Acronis True Image 2017 FAQ Acronis True Image 2017 Mac: FAQ Upgrading to Acronis True Image 2017 Grover's True Image http://www.hardwareanalysis.com/content/topic/19004/?o=200 Guides Acronis Disk Director 12 FAQ Acronis Disk Director 11 FAQ Product pages Acronis Home Products Acronis Business Products Acronis Forum Archive Home › Forums › Solutions for Disk Management › disk read Acronis Disk Director Forum 16205: A disk read error occurred - Press ctrl alt del to restart Login to post comments 7 replies [Last post] Wed, 2010-11-17 14:28 Daniel Pedrosa Offline Beginner Joined: 2010-11-17 Posts: 4 I created a bootable ISO of Acronis Disk Director 12077 (WinPE based). I booted the computer (Windows XP SP3) with the bootable disc and cloned disk read error the first disk onto the second disk: first disk: Western Digital WD1600AAJS (160 GB, contains WinXP SP3 and all my data) second disk: Seagate ST3500418AS (500 GB, empty, sealed from the factory) I used all the default options proposed by Acronis Disk Director (automatically resize the partition in the destination disk to fill the entire disk, "NT signature" was left unchecked). I turned off the computer, disconnected the first disk, and connected the second disk in its place (I used the same SATA port on the mainboard, the SATA0 port). I turned on the computer and I was greeted with this message: A disk read error occurred Press CTRL-ALT-DEL to restart Is this normal behaviour? Please note that I used all the default options, I didn't change any option. Top Login to post comments Wed, 2010-11-17 14:46 #1 Daniel Pedrosa Offline Beginner Joined: 2010-11-17 Posts: 4 More details: Mainboard: ECS ALIVE6100 VSTA (bios version dated 2008-06-19) The bootable ISO disc was automatically created by Acronis bootable media builder (the computer had the latest WAIK 2.0 installed). I've noticed something interesting.
Home Theater Forums Price Search Community HWA Store Latest Topics How to de-activate forum account HGST drive acting very odd Laptop-related ethernet connection issue Dual monitor setup - 2nd monitor flickering greetings... (website=carder007.me):ICQ:669364660,Skype:carder007sale,dumps,CC Fullz Fresh,track 1&2 Optical mouse wont turn off after shutdown Surface 3 running windows 7 used to set up 30 other Surface 3s How to Recover Deleted Files from Pen Drive Files? More >> You Are Here: / Forums / Hard Drives / Getting rid of "A Disk Read Error Occured. Press CTRL+ALT+DEL to restart" error. Author Date Written Tools Continue Reading on Page: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, Next >> David Wickersham Feb 04, 2006, 09:56am EST Reply - Quote - Report Abuse Private Message - Add to Buddy List >>Re: A Disk Read Error Occured. Press CTRL ALT DEL to restartOne day I attempted to boot up and from out of nowhere I began consistently getting this message every time I tried to boot. I had made no recent hardware or software updates except that I do use automatic update for Norton Internet Security and Windows XP. I first checked for cable issues but found none. I have two identical Maxtor 200G drives. I swapped the drives and installed Windows on the one that is normally my secondary drive. I had no problem booting from that drive and no problem reading the original primary drive from the new Windows installation. I read most of the posts in this thread and began trying the suggested solutions working my way up from the least drastic to the most. The thing that cured it for me was flashing the BIOS and refreshing the settings in the CMOS console. There was a slightly newer version of my BIOS available but I have a hunch that if I h