A disk read error occurred
Cause:
The partition boot record was reading data from the drive and received a disk error.
This could be due to damage to the file system, bad boot record information or a problem with the hard disk.
Workaround:
1. Fix File System and Boot Record
You can use Windows Recovery Console to fix a number of problems. First boot from your Windows boot CD/DVD. We recommend you use a version that matches the OS service pack installed on your system (i.e. if you have Vista SP1, use a Vista SP1 DVD). Go into the Vista Recovery Console or XP Recovery Console . For Vista, a the option "Startup Repair" should take care of it.
For XP, you'll need to go through the command prompt and type: chkdsk c: /r to validate and fix errors in the file system.
Next you'll repair the boot record by typing at the command prompt: fixboot
Vista/ Windows 7
Typically this is used if Windows doesn't start and you can't get to the safe mode menu. You might also replace the Master Boot Record (MBR) and boot sector if you suspect a virus infection. There are four options:
New MBR - Insert a new generic MBR without changing the partition table.
At the prompt, type: bootrec /FixMbr
New Boot Sector - Insert a new Windows 7/Vista compatible boot sector. It will automatically insert the right type of sector for the file system type (NTFS, FAT32, etc.)
At the prompt, type: bootrec /FixBoot
Rebuild BCD - Rebuild the Boot Configuration Data (BCD). The BCD controls which partition boots. This option will let you select which installations to include in the BCD.
At the prompt, type: bootrec /RebuildBcd
Find OSes - Scan the system for all OS installations that are compatible with Vista/2008 and will also show those that are currently included in the BCD.
At the prompt, type: bootrec /ScanOs
2. Check Hard Disk and Cables
If you had changed, added or removed hard drives, or changed or removed drive cabling, likely something is wrong. Recheck that the drives are properly installed and the cabling has not changed. Switching cables to different motherboard connectors or changing the master/slave drive jumpers (on old ATA drives) can cause this problem. In some systems, the cables were not plugged into the drive or motherboard securely and may have worked loose. Reseat all drive connectors.
It's also possible a hard drive is failing. Use a system diagnostic to validate the drive or swap to another hard disk.
See also:
Description of the Windows XP Recovery Console.
How to use the Command Prompt from Windows Vista Recovery Environment?
Related Topics :
