New
#1
A disk read error has occurred but disk can be read
TLDR: I get the "A disk read error occurred" error but the system disk is readable and checks OK in the recovery USB.
So, I have two hard drives--a terabyte drive with some data on it and a smaller drive with the win7 installation on it--and a USB drive. I made the USB drive into a recovery USB using the instructions here Installing Windows 7 System Recovery into USB Flash Drive | Raymond.CC Blog with the addendum found in the comments. I made a system image of the smaller drive via the control panel and then put the image in the terabyte drive. I then replaced my smaller hard drive with a new drive of a comparable size.
In order to restore the drive, I booted into the recovery USB, formatted the new hard drive with ntfs, made it active, and ran
wbadmin start recovery -version:xxx -items:C: -itemtype:Volume -backupTarget:C: -recoveryTarget:
where C was the terabyte drive and D is the new drive. I may have the drives mixed up here, but I assure you I had them correct when I actually ran the command
After a reset, I got some generic error so I went back into the bios, and set the new drive to be at the top of all boot lists, and then rebooted. It was at this time I got the above error. I feared that my drive was actually DOA, so I booted back into the recovery. I did a D:;dir and saw that all of my old files did indeed exist, so I figure it was a boot issue. I ran the boot repair utility in the recovery menu and it said there were no errors and I should restart. I didn't restart, and instead ran a chkdsk D: /f and found no errors. I did a bootsect /nt60 /all /mbr and restarted and still nothing changed. I even tried a "bcdedit /timeout 10" and I do not see the boot loader before getting this error. Not sure if that is expected or not but I'll throw that in here.
Sorry about the font change here. Happened when I copied from the other site :)
Any ideas? I can still view all of the files on the drive in question so I know it's not malfunctioning. I have a feeling it's a boot issue, but I can't find anything wrong. Looking forward to your assistance.