bridalpasob.blogg.se - Hdd can be read but get disk read error at boot

HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT HOW TO
HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT INSTALL
HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT DRIVERS
HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT PC
HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT WINDOWS

HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT DRIVERS

Haven't yet even booted to the new installation, didn't need to instal drivers or validate and will delete it and reclaim the space. A few minor glitches, easily resolved on one of the os's but nothing deleted, all working. Let it do it's stuff and hey presto, on reboot there's my boot menu including the previously unreadable installations.

HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT WINDOWS

Turn off pc, reconnect dodgy drive and boot to windows installation disc.

HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT PC

Connected the crashed hdd and no prob seeing it in explorer so reduced one of the partitions and created a new one in the space (obviously can be done by connecting hdd to another pc but didn't have a spare laying around).

HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT INSTALL

So, bunged a spare hdd in the tower and did quick windows install + basic drivers and downloaded Easus Partition Master. Eventually pressed the reset button and lo and behol, the dreaded disk read error. 1 of the os's crashed on shutdown and wouldn't close. I've got dual boot to 2 Win 7 installations on seperate partitions on a single harddrive.

I've just got round this problem on my PC. Maybe a bit late with this but perhaps of help to someone in the future. Perhaps it got tired of running the show. I don't know why the original disk has no problems being a slave.

To put it one way, your motherboard and drive are no longer on speaking terms. Here's what I've learned: this error message likely has more to do with a hardware interaction between the drive and your system than any actual issues with the drive. The problem typically evades all forms of detection. If it doesn't, or it there are errors, run the Repair Installation option from your Windows boot CD.īut why does this happen? Nobody seems to know why. And all of your data will still be accessible. Ghost your data to a new drive, and use the original one as a slave. If all that fails, here's what will usually work: Pulling the CMOS battery to let the BIOS lose it settings may work.Īt this point, you may be feeling some frustration. Changing the BIOS drive settings from auto to user-specified, ensuring that LBA is selected may fix it. Setting the BIOS to use defaults may fix it, but usually not. Replacing the data cable may fix it, but usually not. Changing the drives from cable select to Master/Slave may fix it. Run the manufacturer's diagnostic utility, downloaded from their website (it will typically find no error) run FIXMBR from recovery console (typically has no result) run FIXBOOT from recovery console (typically has no result) Run CHKDSK /R /P from the recovery console (it will typically find no error) In my experience, you won't start seeing results until step 5 or so. Try each step below, in order, and see if your drive becomes accessible after each step. If you put your drive into another computer, or connecting it as a slave on your own computer, it will typically work fine, and no data is missing.īecause this error is not usually associated with data loss, DO NOT RE-PARTITION THE DRIVE. Multiple restarts result in the same error message. So you receive the dreaded "a disk read error occurred. Having recently dealt with this again, I thought I'd post my thoughts in the hopes that it helps someone else out there. Sometimes the fix is simple, sometimes it's a complete pain. Unfortunately, this is often an indication of a hard drive failure, follow the hard disk fail recommendations for additional steps in troubleshooting this issue.This is one of the most frustrating error messages you can ever deal with. If you have no diskette or CD in the computer and get Disk I/O errors on computer startup, it refers to your hard drive.

HDD CAN BE READ BUT GET DISK READ ERROR AT BOOT HOW TO

How to troubleshoot floppy disk drive issues.

If that computer can boot without the error, it is likely you have a problem with your drive.

Try booting the diskette or disc in a different computer.

Make sure there are no smudges or fingerprints on the bottom of the disc. If using a blank CD or DVD (not burned), try cleaning the disc.

Recreate the bootable diskette or CD you are attempting to boot since the disc may be bad.

Remove the floppy diskette or CD from the computer and put it back in and press any key to continue.

Make sure no floppy diskette or CD is in the computer since the computer may be trying to boot from a non-bootable disk, which may cause this error. If you are attempting to boot the computer from a floppy diskette, CD, or other disc follow the recommendations below. Floppy diskette, CD, or DVD in the computer Below are different recommendations to try before assuming the diskette, disc, or other disk is bad. A disk I/O error occurs any time the computer cannot read a diskette, disc, or other disk in the computer.